12 ms·
>My own experience is that I need to devote about 20% of my time to keep up, if I'm doing it on an ongoing basis, or about 1-3 months every 2-5 years And that
by ChuckNorris89 6y ago
>My own experience is that I need to devote about 20% of my time to keep up, if I'm doing it on an ongoing basis, or about 1-3 months every 2-5 years
And that's the problem with software engineering vs other white collar careers. For example, my accountant friend is expected to be trained by their employer in the latest accounting practices and law frameworks and does't devote 1-3 months per year of their personal time on open source accounting projects to learn the latest legal framework for fun, that would be crazy for him. Same for my friends in architecture, dentistry and law. Their employers pay them to learn and gather the expertise needed for their future in the firm.
Whereas, as a software engineer, very few companies(at least in Germany from my experience) will invest into their existing workforce to train them on the job for the future language/framework they will plan to use and instead seek to let them go once their expertise is no longer valuable and hire someone already experienced in the needed stack then repeat the cycle several years/decades down the road.
That's why here you're expected to transition to management as a career progression, as IC roles are not really valued at old age unless you've dedicated your free time to coding and I don't know about you guys, but I'd prefer to spend my free time with my kids and exercising outdoors instead of coding to make myself employable in the latest stack.
- Nursie 6y ago> Whereas, as a software engineer, very few companies(at least in Germany from my experience) will invest into their existing workforce to train them on the job Maybe I've been fortunate, but in the UK and for a couple of years in Australia, I have had employers (and later clients for my contracting business) who have been happy to throw me at projects far enough outside my comfort zone that I keep learning and stretching my muscles. I feel at the top of my game (much of the time).
- caymanjim 6y agoMy anecdotal evidence does not match your anecdotal evidence. I'm approaching 50, and I've had about a dozen jobs in tech starting in my teens. I've never worked anywhere that didn't allow on-the-job time for learning, and the majority of my employers have both actively-encouraged it and financed it. I also learn on my own, for fun, as my career started as a hobby and still interests me, but the vast majority of my education has been paid for during normal work hours. I also actively seek out new and interesting technology when switching jobs, and I switch jobs when things stagnate. It's what you have to do in tech, regardless of your age. If you stay too long at a company that isn't advancing your career, you're going to go stale. This isn't specific to tech either. How many mechanics, lab technicians, chefs, marketing people, stock brokers, architects, lawyers, etc. could find a job today if they hadn't learned anything in 20 years?
- sukilot 6y agoNo field reinvents itself as frequently as software.
- dpc_pw 6y agoThat's only true if if you consider SWE as "learning a JS framework". The core methods and principles of SWE are almost timeless, other things are well documented and can be learned on the go.
- deleted 6y ago[deleted]
- nitrogen 6y agoIt's extremely difficult to communicate this to a team exclusively populated by those who do not have cross-language experience. As an anecdote, and not to boast: I have occasionally had to write data visualization and function plotting software at least a half a dozen times in as many languages and frameworks, from QuickBasic as a teenage hobby, to C in DOS, Java (Swing and JavaFX), OpenGL, WebGL, JS with charting libraries, Linux raw framebuffer... Also tweaked MRTG charts back in the day, wrote a super basic 3D editor in highschool for games I never ended up making, etc. A team I was on once had to add a simple chart to a webapp. When the task came up in meetings and was causing the dev assigned the task some grief, I mentioned that I've had to do some charting work before, and offered to help with any details if they got stuck. Instead of saying something like, "Ok, I'll let you know if I have any questions," they said, "Yeah, but was it D3?"
- pmiller2 6y agoIf by "anything" in the phrase "hadn't learned anything in 20 years," you mean things like legal principles, rather than specific new precedents and laws, I suspect a lawyer probably doesn't have to learn much after they clear the bar exam. If any lawyers read this, I'd love to be proven wrong. :)
- 6y ago
- FerretFred 6y agoAh, training - I remember that. Sadly I was only ever "treated" to a couple of "real" (paid-for) courses at the start of my career and the rest was on-the-job.
- Kinrany 6y agoHow often do legal frameworks change? As a non-expert, I think there's a 50% chance it costs 10x more to teach each new hire for a month.
- wittyreference 6y agoAs a physician, I attend conferences, subscribe to online references, question banks, various journals, take ongoing CME, repeat licensing exams, and spend the equivalent of one workday a week reading those new materials, and try to spend a couple hours refreshing myself on materials outside of my specialty. This amounts to an extra un-reimbursed workday a week, and several thousand dollars a year. When I worked in a place that offered CME/conference reimbursement, it covered about 1-2K a year, depending on budgeting issues. In my current place, and for all independent or small practice physicians, that comes out of your own pocket. This does not have any career benefit whatsoever; it’s done so as to be worthy of our patients’ trust. I wouldn’t mind if it was at least partially reimbursed though. It’s an enormous chunk of change, and not for my benefit.
- wolco 6y agoDoctors around here don't do anything close and pay out of pocket. Most will take sponsored vacations paided for by drug companies for being the top subscription giver. Same for dentists usually paided for by some whiting product they will push over the next year.
- chefandy 6y agoHow would you compare your earning potential to a software developer's?
- enraged_camel 6y agoDoctors on average make more, but they also start their careers burdened with overwhelming debt (a few hundred thousand dollars) and work much longer hours than software developers. Both my parents are doctors, and I'm a software developer. And you know what? I have it really, really good in comparison. edit: I noticed that you phrased the question as "earnings potential" -- well, in that case, it's comparable. High-level engineers at FAANG make boatloads of money.
- jimmydddd 6y agoGood points. Doctors do appear to have good career longevity though (in the US). The practice my children go to has several doctors in their late sixties. The doctor who delivered my kids was close to seventy years old. So if you look at career earnings, doctors seem to be in a better spot, as they aren't worried about finding a job from ages 50-65. Is that your parents' experience with their colleagues?
- mantap 6y agoNobody can argue what the next accounting rules are. Accounting practices are handed down from above and all accountants have to follow it. Programming is not like that. If you ask 100 programmers what the new big thing is, you will get 100 different answers. I would much rather take responsibility for my own professional education than outsource it to a company that may not have my career best interests at heart.
- heymijo 6y ago>Nobody can argue what the next accounting rules are This is just not accurate. Accounting rules not only can be argued, they are all the time. FASB and GAAP are rife with subjectivity. I have an accounting degree.
- davinic 6y agoTrue but the framework is standard, which is why there is no software engineering equivalent to GAAP. GASP?
- jaeming 6y agoI've also heard of a lot of employers that are pushing the 20% policy for their software engineers or providing some other time allocated towards upskilling. My employer requires us to do one hour of training per day. We are allowed to study whatever we want or work on personal projects. I personally don't think it's weird for an engineer to keep up with emerging tech and trends. I'm sure a lot of engineers outside of software do this.
- mrich 6y agoYou definitely have to push for it, only in the best of companies will everyone from top to bottom management take case of this proactively. Speak to your manager regularly that you need to expand your skills, tell him why, and show him what you want to do and how he can help. Some managers are not very good at this and you need to do the majority of the work. Accept it and do your part, but don't think training isn't needed just because your manager doesn't bring it up.
- dcolkitt 6y agoI think a lot of this is because employee turnover in the software industry is much higher than for most professions. An accountant, lawyer or architect can reasonably be expected to stay with the same firm for a decade or longer, often their entire career. It makes sense under that context for employers to invest more in long-term skills. Whereas, once you get to the heart of Silicon Valley, it's not unusual for people to jump employers every 6 months. That's maybe not the rule. But even Google and Microsoft has turnover rates that imply a half-life of no more than a few years for the average employee. The economics of long-term re-training just doesn't make sense. Is this the worse thing in the world though? It allows savvy workers to continuously jump around companies and continuously re-negotiating higher compensation packages. That helps to make sure that workers are paid at or near their market value. In a way that doesn't work in the accounting industry, because future employers would look down at your resume history.
- sgustard 6y agoThat logic doesn't hold up. The overhead in learning your way around a Google or Microsoft-sized codebase is much larger than learning a new language or framework.
- pmiller2 6y agoThat's no surprise. Both of those companies have many individual codebases that are larger than any web framework. For instance, last I checked, Django clocked in at around 60-70k [0] Python LOC. The Windows kernel source, IIRC, is over 1M LOC, and, obviously, much lower level than Django. --- [0]: Also, IIRC, 20-30k of that is taken up by the ORM.
- pmiller2 6y agoThis is a good comment with a lot to unpack, but I want to raise a couple points here. First, I wonder if firms investing in training could possibly improve turnover, thereby creating a bit of a positive feedback cycle. It doesn't even have to be formal training, either. It could be something as simple as having a weekly journal club, or the equivalent, and encouraging engineers to read at least one research paper a month. [0] The second aspect, engineers moving jobs just to get raises, seems weird to me from a market efficiency point of view. Interviewing costs companies money -- so much so that it's something they should want to do as little as possible. Many companies don't keep pace with the open market in terms of raises, which is a primary force driving people to job hop. Are there any studies comparing companies that do at least attempt to keep comp for current employees in line with the open market against those who don't? --- [0]: In my experience, reading research papers thoroughly can be a pretty thought intensive process. In grad school, where I studied math, what I would do is read the abstract, decide if it was interesting, then skim the section headings and statements of theorems to see if I wanted to go further. If I did, and I was searching for a particular widget I needed for a proof, then I would read as much as I needed to read to digest the proofs of the useful theorems. If it was for general interest, then I would read the whole thing. I found that once I got an interesting paper in my hands, fully comprehending what it said could take up to 1 day per page for particularly dense papers.
- tensor 6y agoNote that these other professions have tests and certifications you need to pass. I can see developers howling in anger if they were required to do this.
- pmiller2 6y agoI don't think it makes sense to have this in the form of required licensure to practice, but I certainly wouldn't mind if there were tests and certifications I could take that would allow me to show prospective employers what I could do. Extra bonus points if having those things on my resume allowed me to avoid the types of interviews where the candidate is essentially put on the spot for an entire day in front of a whiteboard or laptop. To their credit, I believe that's a direction TripleByte might be attempting to go in, but I don't pretend to be able to speak for them.
- maze-le 6y ago> Their employers pay them to learn and gather the expertise needed for their future in the firm. I think it very much depends on the company and culture. I always had jobs where learning and self improvement was encouraged and expected (also in Germany). With a budget for conferences and books and a fixed time frame (~20%) for that. These were all companies that primarily did software development -- either direct product development or project work for customers. On the other hand you have firms where software treated as an appendage. They might have other great products but an entirely different managerial background. A mindset like: "We need a software department, everyone else has one too" can easily lead to mismanagement -- and I think a lack of time and budget for self improvement is an aspect of mismanagement in the business of creating software.
- deleted 6y ago[deleted]
- ranit 6y ago> ... (in Germany) ... instead seek to let them go once their expertise is no longer valuable and hire someone already experienced in the needed stack then repeat Interesting. I thought Germany's labor law highly discourages this. Isn't "It is easier to divorce than to fire someone." a German saying for your tough labor law?
- thewebcount 6y agoI have a slightly different problem. My employer will pay to help us keep our skills up. We can take training classes and go to 1 related conference per year. We have some time during regular development to work on innovative projects that we'd like to implement or experiment with. That's all great, but much of it ends up not being applicable. For example, we were trained in a new language about 3 years ago, but we haven't been allowed to use it in our product yet! I've been doing my home projects in it, so I'm ready to go when we do start using it. But most of my coworkers took the class and haven't touched it since. They've likely forgotten everything about it. Likewise, the conferences are nice, but I've never implemented anything useful after having read a paper about it, or seen a presentation on it. (The few times I've tried, it turned out the paper didn't give enough information to do your own implementation!) It does keep me aware of what's going on in the field, but I'm not sure how useful it actually is to my job.