re: Is software developer fatigue a thing? VIEW POST

VIEW FULL DISCUSSION
 

Great questions!

As far as languages, I believe that new languages will keep coming around and I think a huge part of that is figuring out the best way to write software and learning from past efforts. I look at languages like Elm, Rust, Go, Scala, and Elixir. They're all evolutions of past efforts where the language was written and designed nearly from scratch, pulling in all the best ideas currently out there.

And as they evolve, they will produce more ideas. While older languages will hang on and evolve as well. They can't start from scratch but I'd look at JavaScript, C++, and C# where they're growing and getting better with time: from performance, to library support, and much more than that.

The fatigue is real but you just need to zoom in on what really interests. I wanted to learn a good replacement for Node (for fun) and sampled Elixir and Golang. I'm using Elixir at work and Golang in my spare time because I like the way it looks and feels.

When it comes to cloud offerings, Amazon's dashboard pretty much gives me a panic attack until you realize that only a handful of services are relevant to YOU. But all of them are offerings that people use.

Looking at the list, I doubt we use more than 5 of these services at my job: S3 and IAM are the ones that come to mind immediately. However, we're planning to migrate our DB to Amazon as well, and it's possible our search will be another one.

The AWS dashboard is a tool store that you can pick your tools from, rather than a toolbox you should fully utilize.

 

I think many languages have become better because of other languages.

It would be entirely possible that some mainstream languages would have been worse or evolving at a slower pace if the ones on the fringe or at least less mainstream wouldn't have been there.

But that's the beauty of it. I don't have an answer but I just wonder sometimes how many times we'll rewrite "now.to_iso_8601()" and in how many languages :D

I picked up Golang recently and I loved it but I don't think it will ever become my "swiss army knife".

I'm circling, from afar, around Dart 2 because Flutter finally made me interested in mobile development but I don't have time right now so I'll wait for Flutter 1.0 :-D

I agree with what you said about the breadth of the Amazon's offer but I think that too much choice (if you sum AWS + Google Cloud + Azure) can make decisions hard sometimes.

At least it's creating a ton of articles in the style "this technology vs that technology" :-D

 

As far as the reimplementation goes, I'm just glad that a lot of these hardcore necessary features (eg. the iso conversion) is based on a spec which should, theoretically, make it much easier to convert. You're not reinventing the wheel, you're just building it from another material...if that makes sense.

The AWS dashboard is absolutely overwhelming and I do feel like unless you spend time researching and learning the tech, it can be nearly impossible to make a right decision and decipher what all of it means. Like Cognito. I had no idea what it was until our company started getting into authentication providers. Or what's the difference between RDS and Aurora? Etc. It's A LOT.

And yeah, on top of that, all these cloud providers call these features by completely different names.

code of conduct - report abuse