dosethree

my golang code is littered with err handling etc, it’s easy to miss something over the course of dozens of prs. This is something best caught at compile time or by a linter. Or tests which I am often lacking

I find code review unreliable at best for catching bugs or logic errors, but depends on the reviewer

Just phrase it as a question

“Do you think this is too complicated?”

“Is there any way we can simplify this?”

I've ran into bugs multiple times because I ignored an error result, or overwrote the "err" variable and swallowed an error. Errcheck helps a bit.

Other languages that have exceptions that bubble up the stack have a few advantages (easier to instrument with monitoring, stack traces and line numbers out of the box) but developers often misuse error handling as flow control

in the old days I would format before upgrading osx. if you use a bunch of developer tools, they would often break with osx versions. remember macports? wiping every year or so isn’t a big deal when everything is in the cloud. haven’t needed to in years, though

maybe? it’s a terrible newbie experience. but once you know how to use a version manager, things get a lot easier. it’s been this way for forever, and the problem is not limited to ruby.

Isn’t being a good parent not making your family choose between being poor and having a workaholic parent?

Why do companies choose contractors over FTE? Sometimes it’s just because it’s temporarily addition to the work force. If they are vetted and trained like FTE, great. Sometimes the difference is just how you get paid and it doesn’t matter

Sometimes though companies can’t hire FTE so they bring in a of contractors (or outsource), vet and manage them poorly, or give them controversial projects and then they have to lean on the FTE. Also they are often not on call.

how is using cap clunky? works great

re: nose breathing. What i’ve been doing is using Simply Saline (easier than a neti pot) and using breath right strips. Optionally use a mouth guard which can help you avoid mouth breathing

If your interesting in more about this check out the recent HBO Real Sports episode

we’re all just skeletons with skin sacks stretched over them

management should make it clear that working off hours or overtime shouldn’t be done

When I have to install a CLI tool and it's in python I sigh loudly. Happy that many CLIs have moved or are moving to golang

if it was done through your account id imagine you'd be able to see it in your activity log? the distinction is critical

for stateless apps (with HA, capacity etc) its easy

Same thing happened in the US. It made no sense to everyone and degraded public trust at a critical juncture.

Theres a lot going on in Dune, not all of it is explained up front. Its the kind of book where earlier parts make more sense later because theres not a crazy amount of exposition explaining things and how the world works, and theres a lot to digest. The movie ends up being kind of worse in this regard for people new to Dune

Bikes are just super dangerous, at least when there are cars involved. Only injury I've ever had was when a cabbie cut me off going the other way and I flipped head over heals on my rent a bike and fractured my arm

The longer you are in a career, the more you realize opinions are one of those things that always change (and should). Strong opinions weakly held

It's harder to achieve 10x in a vacuum, but if you make 10 engineers twice as productive, there ya go

If there are 10x engineers, it's a right place, right time situation. Very good engineers with the right experience, luck, a good idea, and the relentless desire to execute. Miss any of those things, and you can still be a a multiplier, just probably not 10x.

Even so at my companies the difference between between good engineers and bad is massive (a lot of the difference is talent and motivation). Imagine you had a company full of shitty engineers, a motivated good engineer in the right could deliver 10x the value of some shit engineer

How much does it run you?

well, not literally perfectly safe. just not enough data

nobody ever said the end goal was to flatten the curve. like everything else, we are playing it by ear, to suggest we had plans to do otherwise is just writing your own history

"Resigning over a random employee refusing to say that "white supremacy exists" is absurd"

The founders effectively took everyone's voice away. I think that's a very consistent way to get people to leave - especially people who for whom having a voice is more important than working at basecamp

I've spent some time trying to pick up modern JS tooling. I used to code JS back in the early days of JS and stopped around the time Backbone JS stopped being used

The learning curve right now in JS is ridiculous. Onboarding developers is hard. We wrote a new project in ember js and threw it away for react.

Sometimes new tools, like Ruby on Rails, make it way easier to get started. Not so with JS. But I'm sure you get a lot of dynamic rendering power to make up for it

Technical debt not only makes it harder to add features, it makes it harder to remove technical debt and make technical improvements. Choosing not to pay down technical debt is fine, but at some point it will be such a mess you won't be able add features or fix the technical debt issues without a total rewrite scale project.

Code has to be clean enough. The penalty for dirty code can be quite steep, or none at all. Never let perfect be the enemy of good.

Typically you have doors and windows closed at night, so with reduced ventilation its typical for c02 or VOCs to spike. It must suck to live somewhere (LA?) where opening the windows doesn't help

I assume above commenter was missing a /s. Personally, I don't get the distinction the author is making between production and development apps with regard to heroku