81–90 of 1001 posts
Edit your blog post down to a few hundred words and then I'll read it.
Earlier quoted context omitted.
It's a personal blog. There's nothing wrong with being as casual as you like on your personal blog.
There is if your goal is to attract a wider audience. Call me old fashioned, but if you can't even be bothered to capitalize the first letter of each sentence in your publication, I'm probably not going to read it.
There’s a company in between initial growth and stable company, which has become increasingly relevant. I don’t have any fancy name for it, but it’s the one where your company gets bought by private equity and “creates efficiency” by laying half of your company and limps across the 3 year tax mark as a tired old dog, changing hands again.
Startdown? Enshitterprise?
[flagged]
It seems the author purposely tried to make this article as long as humanly possible. That's not going to make me want to read it more or think you, the author, are very smart because you write a lot of words. Edit your blog post down to a few hundred words and then I'll read it.
Most tech interviews are as relevant to job performance as if hiring a baker required interviewing them about how electron orbitals bind worked gluten together then rejecting bakers who don’t immediately draw a valid orbital configuration.
Matt's analogy works well for transactional hiring like hiring contractors but doesn't really translate well to situations where the mutual expectation is that we're going to spend a lot of time working together for at least the next few years. Most companies that are hiring engineers often need teams of people to bake bread. Sometimes those teams are huge and often the bakers in those teams are responsible for granular (pun intended) steps to ensure the bread is the best bread it can be. So, if I want some good bread and I intend to have a team of 40 bakers with individual strengths and disparate responsibilities baking that bread, then soon enough the responsibilities will become so granular that actually, I do need at least one baker capable of drawing a valid orbital configuration. Now that I've found a baker with strong quantum mechanics skills, I now need to figure out if they are going to be a horrible human to work with.
This is why referral hiring always has been and still is king. There's no greater hiring test than working with someone for a few years before deciding if they are any good at their job.
Wild that explanations of the tech job market like this are still being written without referencing the tax consequences of Section 174 changes.
What is hidden from all this is one of the greatest scams happening in the tech industry: recruiters. I think there is not enough light shone on these group of people but basically they have hijacked the whole process and are not technically skilled to understand good developers. UK tech companies for example have been decimated because of this.
Someone has to do the work of pestering software developers on LinkedIn. If the external recruiters didn't do it, companies would just do it themselves.
Mathematically we will end up with some sort of wealth tax but that just means it’s in the government’s interest to continue exasperating wealth inequality. A wealth tax won’t save the middle class, it’s more likely to be another nail in the coffin. At least now I no longer have to argue with ‘inflation is good for us’ people.
[flagged]
Maybe I’m an old, but this thing called a “blog” was very popular a long time ago, where people would have their own slice of internet to write whatever they wanted.