HN user

djbusby

5,180 karma
Posts2
Comments2,095
View on HN

brutally test them

I cut my teeth in the industry on the test side at MS; it was a bit adversarial with the dev side. And there was a third side to get us both on documentation.

It was frustrating but, I think we made Good Stuff (NT4, Win2k).

I have not seen that rigor since.

We had this problem at work too. And didn't want yet another service provider. Built our own, in Go, for incoming and outgoing. Has some routing features too. Client Webhooks configs stored in that service and our main app API to that thing to configure.

Not optimized for scale, likely only a few thousand per second capable.

This is especially problematic in early business when the team is small and manager act with same policy/process as when at BigCo.

In this case don't estimate the time to build a poorly defined $something - invert the problem to estimate the value of $somethig.

It's amazing how many of those managers asking for estimates push back when they have to put one out. With all the same reasoning that engineers have when estimating.

A good manager should start with the Value first and allocate time-budget that makes that Value payoff.