coderheed

Oops, I just misunderstood.

It seems like this is bound to have security holes at least for a while, right?

Run!

I’m only half joking. Hopefully your company is ‘one of the good ones’ and it will work out, but they are few and far between.

The tech lead job varies a ton from one company to the next, but all too often it comes with high expectations without enough autonomy or authority to deliver on them. Make sure your boss provides clear expectations and work with them to clarify boundaries over time. I’ve been on both sides of this process and it is difficult and necessary.

Too often, tech leads are expected to wear more hats than they are able to wear well. Delegate all that you can and if there is still too much work to do, ask for help.

It’s all about communication so actively work on this skill.

"The nice thing about standards is that you have so many to choose from."

But the companies in the metropolis either have to pay good wages relative to the metropolis or hire remote. This won't really be a problem until/unless we hit a tipping point in the number of companies hiring remote and I predict that will take decades (unless something drastic happens).

I hadn't realized this, but it's so true. Thanks for the insight.

Keep in mind that IH'ers are trying to start their own independent internet-based bootstrapped businesses. Having joined the IH community recently, I can attest that the business side of things is where most IH'ers are lacking in terms of achieving that goal (myself included). Their technical skills tend to be "good enough". Hence the value placed on these types of books. Hope that helps to explain.

I was surprised that one didn't make the list.

I'm glad you wrote this article because I think people should put themselves out there more (myself included). By doing so, you open yourself up to feedback, both positive and negative, that can help you improve. You have a good example of this with your 9/29 update.

In the spirit of constructive criticism, I second the "not really good testing" feedback, mostly due to the lack of tuning effort and omission of performance-affecting details like configuration, the wire protocols used, how data is being serialized/deserializaed, etc. (though I am no expert with these technologies so some of this may have been implied). All of that may have been overkill for what you were trying to do, but it's what people look for in benchmarking / "good testing". I hope this helps.

Maybe he's up to some more shenanigans here?