As someone who makes a great salary on doing what I love to do, I don't think it's all bullshit. Following your passion doesn't have to mean that you want to be a rock star. It's ridiculous to think that you can't find something you're passionate about in your work.
The author clearly doesn't have the experience in agile development necessary to be commenting on this. As a software engineer turned scrum master, I can say that my company is a well oiled machine using JIRA and agile methodologies perfectly well. My engineers don't have these complaints. Clearly he's doing it wrong.
I really don't understand why there is such a complaint about Apple finally moving to an open standard.
I mean this is an age old cycle. People consistently complain about the changes in technology. Without these changes there would be no innovation. No updates. Do people want status quo for the rest of their lives!? What's the deal?
Also if you have the money to spend $2000+ on a new computer, is it not safe to assume that you can afford a couple dongles until the industries move to that standard?
This is awful looking Swift code. It looks like a JavaScript dev got into Swift and didn't fully understand the fundamentals of Swift. I know it's doable, but as someone who works entirely in Swift this project looks different than 99% of the frameworks that I use.
One of the major issues I have is with the module name and object names. import ws? I mean come on. What happened to verbosity? It seems like the go to these days is to shorten everything and just use acronyms everywhere. Terribly confusing in large projects.
Finally have a look at existing frameworks such as SwiftyJSON and ObjectMapper. Much more elegant.
I don’t have the numbers, couldn’t really find anything online, but I’m sure the number of Tesla’s on the road is a fraction of Toyota’s