bradgnar

This article sounds much more clever than it actually is. Admittedly it does take time to actually know how to write clean code, but if you can, I'd argue it takes less time to write clean code than anything else. Especially if you have a great senior engineer who can architect all of the inheritance and fan out the implementation of the adapters to more junior people.

TURKISH GETUPS!!

levels.fyi is still legit

same with code

i agree with the title, but not with the article. All the things listed in the article can be learned outside of a CS degree. What a CS degree does is force you to learn the academic which gives you the foundation to work at FAANG or some other company that has high [principal] engineering levels, or even just the awareness of knowing what you don't know to round out your skillset post school.

Having said that, a CS degree isn't necessary, just better under the premise that knowing more is better than not knowing more.

This article is kind of buzzy, doesn't really make sense, and never actually states what amazon is defending their tool from.

time please, sounds lolworthy

you could make 17 million networks with it, entry point into aws vpcs has to be somewhere

This is a coinhive [based] website that runs a monero miner. Proceeds go to the national parks.

cool, even better ads.

precisely

this is a good response, if he were a brilliant engineer he probably wouldn't be on here with this post. Or he's a troll and then is possibly brilliant somehow??

This story does not make sense

artificially generate views for your blog to get more people aware of your company?

thats legit max one person a month. bfd, nice clickbait.

This is nothing new right? I learned the first day I went snowboarding with my iphone that it was useless to bring with me... at least without some thick rubber case.

want to work there

Everything I can't stand about management revolves around agile methodologies for profit. Agile itself is a good thing, but once you throw in companies trying to profit off of its processes you end up with this weird dogmatic dumpster fire that inhibits people from really doing anything besides keeping track of the current sprint or planning for the next sprint.

Applications dont really need to be well architected until they are hitting scale. Then the parts of their system that need to relieve pressure will need to be re-architected. This is almost like a case study and there are a lot of good talks on youtube from places like dropbox and facebook that explain the problem and solution. Example: https://www.youtube.com/watch?v=PE4gwstWhmc

If you dont want to do youtube case studies there are also books to read about distributed systems. Also reading about cloud architecture can help.

github?

If you've got that range of skills you'd probably be a really good product owner/manager at a big company. There's always that avenue.

Just go do it. I've worked all of those "jobby jobs" on the way to becoming a software engineer. Maybe just get a less aggressive front end developer job? The difference between whats expected of you at different places or different roles is amazing.