Lots of bold, unsubstantiated claims. I think every time there is a big peak, or a big valley, some percentage of people are always peddling "but this is different"
I'll never understand this sentiment. You don't have to have alerts from slack outside of business hours. Or respond in general. If I responded or looked at my messages every time I got one, I'd never get work done... so I simply ignore them until I am taking a break or otherwise at a good stopping point. It's not that hard.
You gave yourself away as ignorant when you tried to explain that the system is optimized for doctors.
This is especially rich on a forum like hacker news, where we have many software developers who went to school for ~4-6 years and fairly regularly make as much as the doctors who round the hospitals, who also kept incurring debt and made basically no money until they were 30.
This seems like there isn't buy-in to the OKRs across your employer. My company does OKRs and it's taken seriously by VPs as well as the devs. Here, it's very reasonable to say no to something (and have that be respected) because it's not contributing to your team's OKRs. If it's a VP or something and insists it needs to be done then that means the OKRs need to be updated to reflect the nature of this work.
I think I agree with you - I'm just trying to understand the other perspective from someone that seems to think not having exceptions is an improvement. I've mostly worked using java and go and to be honest I think I prefer exceptions because you should (almost) always check error codes in go anyway, and if you forget, you just made debugging much more difficult.
Aren't you supposed to check all the possible errors in golang anyway? How's that any different than java code being littered with error handling code?
You think this guy is a hateful hipster, but most of what he says probably resonates with most software vets. To me, it's mostly against the REST zealots who demand REST is done in a very particular manner. I've seen companies with a very stable, robust RPC framework that had a small faction of REST zealots who were extremely against it because it didn't do things according to REST. It didn't matter to them how stable it was or how well it worked.
Also, REST is relatively not popular - what percentage of the world's APIs use REST do you think?
TBH, you're the one coming off like the hateful hipster to me.
To counter anecdote with anecdote, I've had no issues with coinbase and have found them pleasant to use. That includes transferring to gdax/selling/withdrawing, etc.
Weird, I always ignored the news 'show' but this prompted me to watch it and it had nothing that you just brought up. It talked the Barcelona attack, Bannon getting fired, and a couple of other actually worthwhile things. Granted, there were a couple of dumb things (like Taylor Swift's social media disappearing or something), but it still exceeded my (admittedly low) expectations
As a recreational player that plays in tournaments from time to time and is active in my local chess community, this post really only exposes that you don't know what you're talking about. For context, I'm not amazing but I'm no slouch (~95th percentile in the US) and memorization accounts for so little of my defeats or victories that it's practically meaningless. In fact, studying the openings is usually considered to be the least value-adding way to improve unless you're a titled player (usually 2400+ US ELO)
Funny, I have almost the exact same experience. Quit my job as a CPA at a big firm to go to a coding bootcamp, made myself put in the same number of hours coding/learning as I was working my old job (70+/week) until I found a job... got a job at a startup first and 2 years later got a job at one of the "big 4".
I also don't list my bootcamp anywhere mostly because I'm worried about assumptions people will make about my technical knowledge if I do (rather than judging based on my actual performance). I'm also hesitant to recommend it to others because while I have to say it was 100% worth it to me... I've tried to help too many people learn to code who just failed because they weren't willing to fight past the frustrations of the learning curve (which is very steep at first). I just assume now that most people don't have what it takes (and that is NOT intelligence or cleverness... it's mostly just discipline/work ethic/intellectual curiosity).. so I'll never really encourage people to follow my path.