Jira is bad, but the worst part about it is that it makes it non-trivially more likely you'll also be using Confluence, which is an absolute blight upon the software landscape.
The high-achieving SF market may be more likely to select against it.
IME it's much more common in 3rd-tier/mid-market tech companies, or even higher-profile companies where tech isn't the primary operating vertical, and locale != Bay Area.
Companies that can't compete on engineering culture or compensation are naturally going to attract less talented engineers, and there will be a wider variance of skill across the engineering org as a whole.
> But, if you look at some of the latest dev surveys, you'll see there's a ton of fresh talent entering the work force and it's only a matter of time before they become mid-level and senior (5-10 years). At that point, the supply of engineers will far exceed the demand and the same thing will happen to engineers as any other white collar profession.
While I don't disagree we could see a demand contraction, I think your assertion is based on a tenuous premise at best: tenure == competency.
I've had the misfortune of working with many "senior" engineers who struggled with basic technical concepts and even more basic reading comprehension.
The demand for great engineers will always be there. What the market will be flooded with is mediocre ones who have improved nothing but their title in the 5-10 years of their career
> "He then went back to school to pursue a master’s degree in comparative literature at the University of Colorado Boulder."
So:
* Get degree
* Struggle to find steady/career employment in a job market still rippling from a massive recession
* Decide the best ROI is to go back to school for a Master's in Comparative Literature
While I'm totally cognizant of the systematic and pervasive failures of the modern college lending system... I don't think the system is totally to blame for this one.
Four years of college AND working experience and you still can't make a basic CBA for how you spend your time?
> One of the big features Macs have for me is that I can call customer service any time of day and they can work through any serious issue I have with my Mac
This is something else that often gets left out in these discussions. For better or worse, Apple offers an ecosystem/platform, and the support to go along with it.
Suppose you do make a Linux laptop work for your daily driver. You're still left out in the cold if you have an iPhone/iWatch/iPad.
The tight integration that's offered, along with the ubiquitous(and very useful) iCloud is something that Linux just doesn't have.
And yes, I am aware of the various flavors of self-hosted solutions, the dangers of lock-in etc...
If I've already been fighting to make my laptop functional for work, I don't want to start the same battle again for my hobbies too.
The practical implications of what it means to the end user is that companies/entities that write any GUI-enabled software for Linux are forced to make decisions about what(if any) OS they'll support.
And just like that, we've waded into "cracking open the window manager" just to figure out what's going on.
End-user Linux has definitely improved in the last few years.
It offers a lot of attractive features for what I imagine to be the typical HN demographic.
That being said, it's still got rough spots that OSX doesn't. It works great when it works, but when it doesn't....
Font rendering, display/compositor fragmentation etc...
Inb4 the anecdotal "well it works for me I just had to download the xf86 font library and compile with a legacy glibc version..." crew comes in with a thousand and one rebuttals. Problems like that are still a suboptimal user experience, no matter how you slice it.
I'd definitely consider a Linux daily driver for some of my work, but there are things that are just going to be less painful on Apple.