4 ms·
Not targeting you, but the industry in general. In every other industry I've been in outside of software dev, 10 years is not considered elder. You're just now
by dylan604 2y ago
Not targeting you, but the industry in general. In every other industry I've been in outside of software dev, 10 years is not considered elder. You're just now becoming not a greenhorn. You're just now getting your sea legs. It's amazing what additional experience happens after year 10.
To that effect, Rust (2015) is 9 years old, Go and Node are 15 years old. While Python (1991) is 33 years old. Just putting things in a different perspective
- Cthulhu_ 2y agoIt just feels different in software development because things have moved very fast, I'd say especially when github rose to prominence. The amount of software developers on the market has also increased exponentially since then, so the amount of (relatively) junior developers is much higher than those of 15, 20+ years of experience.
- jltsiren 2y agoThe number of software developers has maybe doubled in the last 20 years. The number of senior developers has "always" been low, because the field suffers from unusually high attrition. Many people find that software is not for them, many switch fields after losing their jobs in an economic downturn, some move to management, and some make too much money to bother continuing until retirement age.
- mrkeen 2y agoHas there actually been attrition? Exponential growth is enough to explain "many more juniors than seniors" at any time in the past, present or future. Also for attrition to be the cause, you'd need a lot more seniors dropping off than juniors.
- jltsiren 2y agoThe exponential growth has been something like 3-4%/year, or 2x in 20 years. Though it's hard to find useful statistics that take different job titles and changing nature of the industry properly into account. If you had asked me in 2010, I would have said that the median software developer lasts 5-10 years in the industry. A lot of people left the field after the dot-com bubble burst. The same happened again in a smaller scale in the late 2000s, at least in countries where the financial crisis was a real-world event (and not just something you heard about in the news). But now there has been ~15 years of sustained growth, and the ratio of mid-career developers to juniors may even be higher than usual.
- Retric 2y agoNone of my friends who graduated with me are still software developers and I’m several years from retirement age. There’s a bunch of filters. Many people quickly realize they don’t enjoy development, next is openings in management. One of the big ones is at ~40 you’re debt free, have a sizable nest egg, and start thinking of you really want to do this for the next 20 years? A part of this is the job just keeps getting easier over time. Good developers like a challenge, but realize that the best code is boring. Tooling is just more robust when you’re doing exactly the same things as everyone else using it, and people can more easily debug and maintain straightforward code. So a project that might seem crazy difficult at 30 starts to just feel like a slog through well worn ground. Having significant experience in something also becomes a trap as you get rewarded for staying in that bubble until eventually the industry moves on to something else.
- lifeisstillgood 2y agoI recently hit thirty years of professional software development, in companies large small, profit and non profit, proprietary and FOSS, I have led teams of forty, sat in a corner as the only developer and one thing I know in my bones - I love making software and money just means I get to code what I want instead of what The Man wants. In fact I already have my retirement planned - a small near flat in Argostolli, a walk down to the coffee bars on the harbour and a few hours adding code and documentation to a foss project of my choice before heading to the beach with grandkids. Now affording retirement might be interesting but not having coding in it will be like not having reading and writing
- oblio 2y agoYou're probably from a privileged environment such as working in the US (probably in a top location) and probably from a top university or you were there at the right time to join a top company as it grew rapidly. The first paragraph probably applies to 1-10% of developers worldwide...
- deleted 2y ago[deleted]
- 2y ago
- samatman 2y agoI'm reasonably sure that this estimate is far off the mark. The numbers I've seen suggest that the number of new software developers entering the industry has doubled every five years since at least the mid 90s. That's not the same metric as total number of developers, but it may as well be, and it definitely doesn't add up to a mere doubling of the total in twenty years.
- jrk 2y agoRust was started in 2006 and launched publicly, I believe, in 2009, the same year as Go. The point stands that these are still fairly new, but it’s not nearly that new.
- cmrdporcupine 2y agoEarly Rust was a very different beast. But could say the same about Python pre-1995 or so. My biggest problems with Rust, though, are Cargo and Crates.io, not the language.
- anacrolix 2y agocrates and cargo are better than Rust actual
- cmrdporcupine 2y ago... for you
- gary_0 2y agoCargo and crates.io are something C/C++ developers would kill for (which is why cargo is what it is, I think).
- cmrdporcupine 2y agoJust because there is an absolute shitshow for C/C++ build systems doesn't automatically make Cargo & Crates.io good. There is a fundamental philosophical disagreement I have with the NPM style of package management and this method of handling dependencies. Like NPM, Crates.io is a chaotic wasteland, destined for a world of security & license problems and transitive dependency bloat. But honestly I'm sick of having this out on this forum. You're welcome to your opinion. After 25 years of working, with various styles of build and dependency management: I have mine.
- gary_0 2y ago
- shermantanktop 2y agoI’ve been in this game for 30 and I agree with GP. “I won’t build that simple thing from scratch, I’ll just import this thing that does approximately what I want.” We should banish the word “import” in favor of “take a dependency on someone else’s code, including the stability of the API, the support model, willingness to take patches, testing philosophy…” Reputation is a rough proxy; inspecting the code can help. But when the thing you built your house of cards on falls over, you often can’t fix your house, and have to build a new house. Obviously this applies more to utility code than it does to entire languages. But even there, Apple has broken their Swift syntax enough to release tools that upgrade your code for you…and that’s the best case scenario.
- hnlmorg 2y agoI’ve been in the industry for > 20 years and if anything, I think most people are too scared or lazy to reinvent code. I’m not suggesting the earlier argument about NIH (not invented here) syndrome doesn’t exist. But I’ve certainly never seen in the scale that the earlier posted claimed. If anything, I see people getting less inclined to reinvent things because there’s so much code already out there. But maybe this is a domain specific problem? There does seem to be a new JavaScript frontend framework released every week.
- YZF 2y agoI've been in the industry for >30 years ;) I'm not sure what's the proposal? - Don't use an OS. Write your own. Linux? Boring. - Design your own CPU. - ext3 or xfs? Nah write your own. - Write your own database. - Ethernet. Too boring. Create a new physical layer for networking. - Naturally create your own programming language. That'll make it much easier to find people when you have to expand the team. Seriously, build vs. buy and NIH has always been with us. There's a time to build and there's a time to buy/reuse. Where are you adding value? What's good enough for your project? What's strategic vs. tactical? How easy is it to change your mind down the road? What are the technical capabilities of the team? How do different options impact your schedule/costs? How do they impact quality? In the short term? In the medium term? In the long term.
- ATMLOTTOBEER 2y agoI’ve been in software for over 40 years (yes I’m that old ), and in my humble opinion it’s always correct to build. It keeps things fresh.
- YZF 2y agoThe reality is there is no way to build everything. You want to do scientific computing do you use libraries that have been optimized for 50 years or do you write your own? You want to do cryptography do you build your own? Pretty much everyone working on LLMs today is leveraging things like nccl, cuda, pyTorch, job scheduling frameworks. Let's face it. Nobody builds everything from scratch. The closest is companies like Google who due to sheer scale benefit from building everything from hardware to languages and even for them it's not always clear whether that was the right thing for the business or something they could afford to do because they had lots of money. Build the things that add value. Don't build something that just works. That's why we have the old saying don't reinvent the wheel. If you have a working wheel, while re-inventing it might be fun, it's usually not the best use of time. In the time you've saved build cool things that add value.
- WalterBright 2y agoIt often takes 10 years or more of use before you discover that your technique is execrable. For example, most use of macros, especially when you invent your own language implemented as macros.
- WalterBright 2y agoA lot of people disagree with me on that. Wait till they try to get other people to understand their code :-/ Me, I've eliminated nearly all the use of macros from my old C code that is still around. The code is better. I suspect that heavy use of macros is why Lisp has never become mainstream.
- kazinator 2y agoHeavy use of macros could be why C went mainstream. Macros gave C efficient inline functions without anything having to be done in the compiler. Doing things like "#define velocity(p) (p)->velocity" would instantly give a rudimentary C compiler with no inline functions a performance advantage over a crappy Pascal or Modula compiler with no inline functions, while keeping the code abstract. And of course #if and #ifdef greatly help with situations where C does not live up to its poorly deserved portability reputation. In languages without #ifdef, you would have to clone an entire source file and write it differently for another platform, which would cause a proliferation due to minor differences (e.g. among Unixes). Ah, speaking of which; C's #ifdef allowed everyone to have their own incompatible flavor of Unix with its own different API's and header files, yet get the same programs working. An operating system based on a language without preprocessing would have hopelessly fragmented if treated the same way, or else stagnated due to discouraging local development. Thanks in part to macros, Lisp people were similarly able to use each other code (or at least ideas) in spite of working on different dialects at different sites.
- WalterBright 2y agoYou're quite right in that early C was a primitive compiler, and adding a macro processor was a cheap and easy way to add power. Using the macro preprocessor to work around some fundamental issues with the language is not what I meant. I meant devising one's own language using macros. The canonical example: #define BEGIN { #define END } We laugh about that today, but the 80's people actually did that. Today's macros are often just more complicated attempts at the same thing. The tales I hear about Lisp is that a team's code is not portable to another team, because they each invent their own macro language in order to be able to use Lisp at all.
- roenxi 2y agoWell "elders" are the people who have been there for the most amount of time, so if the industry has >30 year veterans wandering around then the elders will have around that much experience. But the learning in an industry is generally logarithmic where most of the lessons get picked up in the first 1-3 years and then after that there are only occasional new things to pick up. If anything software seems to be unusually favourable to experience because the first 5 years of learning how to think like a computer is so punishing.