Earlier quoted context omitted.
Devops is an attitude more than a particular practice. So far as AWS, I'm an AWS maniac and I would say it is a bit complicated. You have a huge number of choices and if you pick the wrong ones you will pay in more ways then one. I've gotten to the top of the learning curve fortunately because I read AWS docs over and over when I work out at the gym, but I've got little interest in working with other cloud platforms…
>because I read AWS docs over and over when I work out at the gym Now that's... dedication. How does the "working out" part go though? There is no way I could see myself reading AWS docs repeatedly while lifting, it actually sounds kindof dangerous. Edit: you and I have the same alma mater and have probably worked out in the same gym! Go Big Red.
The Developer's Dystopian Future
91–100 of 209 posts
Re: The Developer's Dystopian Future
#92But listen, it's crucial to ignore this fear, because it's wrong. We don't really lose our ability to learn way until retirement (and for the lucky ones, even past it).
When you decide to stop looking back, and decide to bravely dive into the big unknown, you realize "you still got it".
Been there, done that. I still got it ;)
Re: The Developer's Dystopian Future
#93The lack of coherence in the software career is troubling. See, what we're not told is that (at least under closed allocation) 4/5 of us are going to be bench-warmers, given low-importance evaluative projects, and what determines whether a person gets promoted to something real, or gets enough clout to direct his career and protect his specialties, is mostly politics, not merit. (This can be afforded because, put to genuine work, good programmers are worth $500k-2M/year to the business, and great programmers are worth $2-10M. So low utilization is quite affordable with programmer salaries at their current level.) The result of this is that we have to job-hop until we find jobs where we "click" (find like-minded people, or win the political lottery, or just come in at the right time) every 1-3 years. It's not fun to change jobs constantly, but there's often no other way to have a legit career in this industry.
The other thing that's really shitty is that employers demand specialization and high-quality work in job candidates, but refuse to recognize specialties once the person is on board. In terms of work experience, most companies don't eat their own dogfood. This is also why software firms have a terrible record on internal promotion. Even they would rather hire, for a high-impact position, a mercenary who only did cool stuff over the loser "team player" who let them load him up with grunt work.
I think it's time to consider some form of collective action. I don't want an old-style union (with wages set by seniority alone) because that tends toward mediocrity. I think our model needs to be more like the Hollywood model (Screen Actors Guild, worker-side talent agents). We're generating a lot of value, but ultimately the people who decide what to do with our work aren't using it to improve the world or the state of technology, but to cut jobs. We're in the business of helping executive assholes unemploy people, and that just fucking sucks. We need to take charge of this industry and make it work on our terms, not theirs.
Re: The Developer's Dystopian Future
#94I'm not even legally an adult, and I feel like things are moving too fast for me. At 17 years. I guess I shouldn't feel like that, but I can't help it. I started with VB6 as a kid, 6 years ago. I moved onto C++, then learned about 3D graphics and game engines, then learned HTML, CSS, JavaScript, gotten into web development, learned Photoshop, some basic design, working with Linux, PHP, a little of C#. Recently tinker…
My advice is keep the fundamental books close to you and practice a lot. Programming is mastered by practicing, not by reading blog posts, never forget that. Filter the noise. And most importantly : have fun. Mastery will come as a byproduct, don't even worry about that. You can trust your crave for knowledge, it will always lead you on the right path.
I'm probably not the most knowledgeable out there but you can reach to me if you want to talk.
Re: The Developer's Dystopian Future
#95Honest, legitimate post that I very much enjoyed. However I do think posts like this feed in ageism. I say this because it posits that the change is that the author is older and has more things to do, therefore they've fallen out with technology. The take-away invariably being that people who are older and have more things to do have fallen out with technology, whereas the young are still with it, whatever it is. Let…
I'm reminded by a writing blog, like writers of popular fiction, programmers aren't creating technology anymore but we are simply selling a idea (e.g., Martha Stewart for home furnishings flash sales sites, fear of missing out for Facebook/Instagram, diversion or outlet for teenage aggression/frustration for iPhone games) that validates a user's idea that is wrapped around technology. Hence, tech trends surrounds consumer tech instead of system programming now and new web frameworks sprouts by the day that emphasize shaving the man-hours of a routine set of mundane tasks down by a fraction of an hour for the benefit of the agile burn-down chart.
This is not meant to be depressing nor cynical comment but a liberating one for me. Too often, I or I have witnessed a lot of my mostly younger peers try to reconcile the art and commerce, or to put in blunt way, have our cake and eat it too. I see that as a cowardice or indecisive but perhaps necessary stage in one's journey of growth, not to commit yourself and not to express your personal values through the imperfect tradeoff's and limited circumstances of a finite professional life - but be swayed by the arbitrary trinkets that one's professional guild assigns and equating its idea of worth to your self worth.
VB/Pythonistas/Rails/Node.js I've seen them come and go like names on the Billboards charts moving to VH1's "Behind the Music/Where are They Now?". I'm convinced now that you have two routes in this business, 1) make your programming craft secondary to the development of your domain expertise, so learn finance, SEO or sales whatever is the main objective of your business, 2) make your programming craft your domain business and work at companies where their business is the software.
Re: The Developer's Dystopian Future
#96Open source has made it so businesses don't really need to hire engineers anymore, only developers good enough to make changes to a system engineered for free. As the older generation dies out and the younger generation starts businesses, it will only get worse.
This is why I started my own business and totally quit development (aside from my own business).
Re: The Developer's Dystopian Future
#97I'm not even legally an adult, and I feel like things are moving too fast for me. At 17 years. I guess I shouldn't feel like that, but I can't help it. I started with VB6 as a kid, 6 years ago. I moved onto C++, then learned about 3D graphics and game engines, then learned HTML, CSS, JavaScript, gotten into web development, learned Photoshop, some basic design, working with Linux, PHP, a little of C#. Recently tinker…
Relax. One of the lovely things about being older is having the confidence to be able to be able to point out that the latest fad is just a warmed-over rehash of something old. It's important to keep up with the new things, but the fact of the matter is that there is very little in the world of software development that's actually new. Swift? Please. If you know ML (1970's), Smalltalk (1980), and Objective-C (1983),…
Sane advice. I'm 39, and I'm rather stunned to see 27yr olds calling themselves "old" and disillusioned with tech and what not ... let alone 17!
If you like to build things, hone your system level thinking .. which lasts longer than Angular/Backbone/whatever. (Heck I'm working with the intention of obsoleting them, based on old Smalltalk ideas!) If you like to build things the possibility of which average society has no idea of, hone your algorithmic thinking. I'm certainly more productive today than I was, say, a decade ago because I chose to focus on the ideas rather than specific tools during that time. I'm confident I can work with any tool at hand due to exactly what rayiner says. Good debugging skills, for example, don't die because you need to approach it scientifically.
rayiner - while you're right about the "if you know .." part, many companies today ask for specific skills and hirers don't know enough to say "we need guys to work on a Java code base, you know Smalltalk, you can handle it, hop onboard". So it is up to us tech folks who give these job specifications to hint at the broader kind of people we can accept.
Re: The Developer's Dystopian Future
#98Like the OP I started doing with design-y tasks as an intern in a web shop. Then followed a lot of t.gif style table layouts. Then followed some flash development, and my fist scripting with ActionScript and copy-paste JS stuff. Then ASP classic and PHP.
Then followed the push towards semantic html and progressive enhancement, and the first JS libs like mootools started popping up to be eventually boiled down into jQuery.
Couple years later and it was all about MVC frameworks, databases and so on. Like the OP I did php based stuff, and it meant learning 4+ different frameworks, i.e Cake, Zend, Symfony and so on.
At the same time there was Agile and TDD coming into the mix and you had to learn a whole lot on how to do your work.
Following that I started looking into node pretty early on and that shifted my understanding of JS as a language and pushed me into the niche where I am working today, namely JS stuff be it server or client.
Looking at the current tech choices and popular stacks, or even just the browser APIs available and coming, I cannot believe how far things have gotten. On one hand things have become a lot easier for menial dev tasks, you have things like bower and grunt/gulp whatever really helping you, boilerplate generators and the likes. Deployment is often just a git push so some PaaS or some docker file and shell script. On the other hand is just SO MUCH OF IT, that it's impossible to keep on top of even one aspect of the stack properly if you need to get on with making stuff and have a life. If you just take the browser these days (audio API, Web GL and so on). In 15 years of dev work I have learnt and forgotten so much that my brain feels like a sieve. My approach to deal with that is to not desperately try and REALLY remember many things. Instead I just focus on the current stack I'm working with and remember the general concepts of that, plus some good knowledge of where to look for things. Come the next project in a different stack I basically anticipate a learning curve.
Re: The Developer's Dystopian Future
#99Luckily you don't need any of these fad/new libraries to make good products and websites.
Unfortunately, when you're job hunting ... you do. As I'm finding out. Two years as a system admin and not keeping up with trending tech and I can't land anything here.
Re: The Developer's Dystopian Future
#100Recently I marvelled at how far we have come since 1999, and how many changes in focus that meant. Not just tech itself, but also paradigms and methodologies. Like the OP I started doing with design-y tasks as an intern in a web shop. Then followed a lot of t.gif style table layouts. Then followed some flash development, and my fist scripting with ActionScript and copy-paste JS stuff. Then ASP classic and PHP. Then f…