secondstring

Totally correct - I tried to caveat that in my post by saying I'm skewed hard tech industry. That was the main attention of the article, and my main experience, so I was writing from that viewpoint.

I somehow doubt that Vail Resorts has a non-compete for their lift operators to go work on another mountain (although now that I think about it VR is pretty terrible so this might have been a bad example)

> because nobody involved in the hiring process consciously chose to put that clause in and they probably don't really give a damn.

Yes but I think I didn't convey my point enough. Nobody involved in the hiring process cares, and if it's a good company they probably agree with you. But this standard contract is what they paid attorneys good money to comb over with a fine tooth comb for liability, and eventually sign off on.

Very very very few companies are going to go pay Expensive Law Co. (TM) $500 per hour to review changes to the contract just because _one_ potential hire who still might not even accept the offer says they won't accept if that's in it. It's way out of most recruiters or engineering managers that you might be interfacing with to make that happen, not to mention making their life way harder. Heck even a startup CTO might balk at having to go spend more on legal.

I have had clauses similar to the "we own everything you do 24/day" one and I've pushed back on all of them. Every time, the response is "yes we totally understand but we have no power to change the wording in this contract we use for every single employee" and it just comes down to a gut judgement call on my part on if I feel they will actually screw me over on that point.

Again to emphasise, I totally agree logically with author's and your points. But it's simply not realistic to approach job hunting that black and white unless you're comfortable being out of work for months until you find the perfectly-flexible-enough company.

I mean in principle, I agree with all of these points. But in reality if you stick to these rules hard and fast, you'll basically never accept a job offer. That's clearly an exaggeration, but many-to-most of these clauses are in every boilerplate contract.

Whether it's a small startup that's using a generic contract they've gotten from the internet or their lawyers, up to massive corporations, they're all going to include semblances of some of these points. Probably for different reasons, but the points will still be in there. Startups and small companies might be more flexible to work with you on changing parts, but still the legal headache of changing anything is often far greater for the company than just passing on you and looking for another candidate. Infinity moreso for big companies.

My experience is biased towards technical roles (like most on HN), but I've worked for startups, big companies, and as a freelance contractor. It's the same stuff in most contracts. Obviously my experience is not indicative of 100% of companies and I'm sure I'll have people chime in saying they had success getting company X to change some of their contract, but it's overwhelmingly not going to happen. So to treat these points as 'rules' instead of 'points to be aware of' is a bit too hardline of a stance to take in my opinion.

Heck yeah mate! There's one or two of these here in SF (I'm currently working in the one I'm a member of) and glad to see others are opening up other options. Best of luck with everything going forward, I might reach out to check on your progress the next time I make one of my occasional trips to NYC.

> a development k-hole

Two terms I didn't think I'd ever see used together

Sheesh this should be the top comment. Love it.

Oof this hits for me. Maybe not as much during the day - my mind is running 110% all the time but I'm a very active person so I usually need to be _doing_ something too.

When it comes to falling asleep at night, and trying to sleep to a reasonable hour though, I'm SOL. No matter what time I wake up in the morning, that's the time I'm getting out of bed, because the second I'm awake my mind start churning through thoughts and what I could be accomplishing that day. Case in point - I didn't have anything to do before work this morning, so I would have loved to sleep in until ~7:30 to catch up on some sleep from waking up at 6am every day this week. 6:32am, wide awake in bed, no chance of going back to sleep.

I like it in some ways - I know I'm driven and motivated. But man I'd love to be able to turn it off sometimes.

Easy on that accusatory tone mate. They didn't claim that as their own opinion, but merely gave an alternative viewpoint: "One concern is that...".

Big fan of git-aliasing this to `git back`. I actually use it a ton and that small amount of extra chars plus the "-" makes a pretty decent difference for me.

I couldn't tell whether you meant on HN or on the article, so I went back to see if the article had a comment section.

... I wish I hadn't

You'll find out after biking around for a week or two where the main corridors with minimal elevation are, especially along the main route you take. At this point after ~3 years I know 95% of the best routes to get to/from any within the city proper, and I check directions just for the ending last few blocks since that can make the difference between a steeeeeeep climb or a simple circle around 2 more blocks that's flat.

I also don't have any problem with respect to no bike lanes and crowded streets though, so that might be a bit more difficult to discover. I use Google Maps and it's pretty solid at taking you an extra .25 miles or so just to get you on a dedicated bike lane within the city, and you can always streetview points on your route if you want to double check what it looks like.

I'm going to go out on a limb here and guess you meant 4pm...

Just an FYI, the Hey.com hyperlink in the post seems to be a relative path, just slapping it onto the end of the post route. All of the others work fine, it looks like you just need to add an `http(s)://` on the front and you'll be good.