10 ms·
I'm an application developer, and I'm also an infra guy, because you can't get away from the fact that your code will run on a machine, and you need to know wha
by stavros 3y ago
I'm an application developer, and I'm also an infra guy, because you can't get away from the fact that your code will run on a machine, and you need to know what happens. I don't have much respect for application developers who "don't want to know anything about infra", sadly.
- silverquiet 3y agoI found it refreshing when a developer said to me point blank, "I don't care where this runs". She didn't say that she didn't care that it runs, but she was being upfront that she had other concerns more relevant to her, so she left the operations work for my team, but crucially, she followed our advice/requests on how to build things to work with our infra. Not everyone can do everything; it's why there are specialties, but it means that collaboration is vital.
- stavros 3y agoI don't care where my stuff runs either, but, when it breaks, I care that I have a good enough mental model of what's going on that I can debug it. Whenever I see web developers not knowing how an HTTP server works, a part of me dies a little.
- silverquiet 3y agoI remember learning about keyboard matrix encoders because I got into building MAME arcade projects when it was still a fairly young idea and consumer products that integrate arcade controls with computers were not commonly available. When you learn about them, you'll understand why older and/or cheaper keyboards have artifacts known as blocking and ghosting. It's something that I at least found interesting, but I doubt most people can be bothered to care. And as far as how that keyboard encoder is creating the ones and zeroes and then sending them over the USB bus - that might as well be magic to me. I suppose we all live at the abstraction level that suits us. I'm of the opinion that a lot of the modern infrastructure we work with is over-abstracted. I'm not sure that most developers even know that an HTTP server exists thanks to the work of modern devops where you push a commit and it gets automatically deployed to some sort of container orchestration system. At some level it has to be this way; we stand on the work that was done before us; "the shoulders of giants" it's often said with more poetic flair. So I wonder if it's just me getting older and not understanding the new, or if we have genuinely gone astray in some ways. And those need to be mutually exclusive either.
- stavros 3y agoI don't know, I'm 41 and I understand the application, the WSGI layer, HTTP, TLS, TCP, containers, OSes, CI, etc. Less so lately, as I've transitioned to leadership, but how would I deploy and debug my applications if I didn't know all this stuff? I guess I've traditionally built and deployed all my apps myself, without the luxury of an infra person, so I had to learn all this, including Linux administration.
- silverquiet 3y agoSimilar age and skillset here though much more comfortable on the operations end of things rather than the development side though I have built small apps that did see some production use which was cool to do. It's a wide-ranging skillset no doubt, but still built on the work that precedes it. Did you build the servers that ran your code? Rack them and set up the networking? Build redundant power systems for them? HVAC? I'm sure you've done some of that, but no one person can really do it all. I think the saying is something like, "fish don't know they're wet"; meaning that they're so adapted to the ocean that they don't really have any idea that there are other ways to live. I get that feeling when I hear older folks talk about working on mainframes - it just sounds like an alien world. I came of age in the era of distributed systems - Microsoft vs Open Source, but it was always on commodity x86 hardware and TCP networks. There's no law of the universe that said it had to evolve that way. It seems like the new way is "cloud-native" which I'm not sure I understand or like (as I've said, it may just be me getting old); my biggest problem is that it seems to give ever more power to Amazon and other members of the tech oligolopoly rather than any technical shortcoming.
- stavros 3y agoI agree with you on the cloud-native stuff, I'm sure it's great after a certain scale, but I think people switch to it way too early, and now we're running our three apps on a huge stack not many people can know unless they spend a lot of time understanding the configs. Maybe it's the same as before, maybe I'm just less familiar and it seems huge to me.
- throwaway894345 3y agoI generally agree with you. In my experience, the infrastructure engineers are very often the best software engineers. Like there have been half a dozen times in the last year that an infra team at my company has essentially done the architecture design work and high level implementation for a complex system that the dev teams technically owned, but they kept stalling out on. I think there are at least two reasons for this: the first is that infrastructure engineers (e.g., SREs) just think about reliability and architecture a lot more than SWEs and the second is that the infra eng position generally selects for people who have a penchant for learning new things (virtually every SRE was an SWE who raised their hand to dive into a complex and rapidly evolving infrastructure space). Also, the best SWEs have been the ones who accepted the reality of infrastructure and learned about it so they could leverage its capabilities in their own systems. And because our org allows infra to leak to SWEs, the corollary is that SWEs are empowered to a high degree to leverage infrastructure features to improve their systems.
- elktown 3y agoThe problem is that our field has a deep seated problem with differentiating good engineering with over-engineering. The latter is taken as the former. In my experience SREs/devops will just as often over-engineer and leak their abstractions to everyone else due to paranoia and the current fad in the "cloud native computing" field. Suddenly people need to know about a dozen concepts to debug the travel of a http request. This was not needed before and mostly just a consequence of holes we've dug ourselves (like micro-services) and are now using to justify our over-engineering - all within the part that was previously seen the absolutely simplest one to manage: stateless app servers.
- throwaway894345 3y agoI mean, maybe? I won’t doubt that some people are prone to overkill or hype-driven engineering, but also most of the simplest solutions still look like Kubernetes (e.g., a cloud provider or a platform-as-a-service). The most severe, prevalent danger is people thinking these things are too complex and then trying to roll their own alternative on bare VMs by cobbling together disparate technologies which only the very best sysadmins can do passably (of course every other sysadmin thinks they are in this elite group) and even then the thing they build still leaks implementation details except now there is no market of engineers who are experienced with this bespoke alternative to Kubernetes nor is there a wealth of documentation available online.
- n3storm 3y agoI do infra apart from dev, ssh, rsync, remote volume, tunnels, load balancer, proxy, these are not trademarked words that belongs a knowledge domain. I am afraid people is focused on company products that the will forget what infrastructure is.