HN2new | past | comments | ask | show | jobs | submit | guywithahat's commentslogin

Well it's a retort on the 2022 IRA bill, which increased the IRS budget by 80 billion over 10 years, and paved the way to hire 87,000 people. There has been a lot of hiring recently so it's hard to tell one thing from another but this isn't so much of mass layoff as an attempt at returning to normal.

Please provide evidence for what you considered to be normal to be an effective workforce for the ongoing task at hand (nation state tax collection).

The evidence was the baseline before the increase

The baseline was there was significant tax evasion by high net worth individuals. The staff up was to counter that, staffing down puts us back at reduced enforcement.

Someone has to pay to operate a nation state, you can’t borrow forever to fill the gap and there’s nothing left to cut.


I think the point of the article is that on sites like HN, people used to need domain expertise to answer questions. Their answer was based on unique experience, and even if maybe it wasn't optimal it was unique. Now a lot of people just check chatgpt and answer the question without actually knowing what they're talking about. Worse the bar to submit something to Show HN has gotten lower, and people are vibe coding projects in an afternoon nobody wants or cares about. I don't think the article is really about writing style

It looked to me like it was just due to recurring build issues. Lots of "swift can't import these conflicting C++ versioned libraries concurrently" and "can't use some operator due to versioning or build conflicts". Basically it sounds like trying to add swift to the project was breaking too many things, and they decided it wasn't worth it.

It's a shame, I think swift is an underappreciated language, however I understand their reasoning. I think if they tried to just use swift from the beginning it would have been too ambitious, and trying to add swift to a fragile, massive project was probably too complex.


Looking at their integration, with cmake, they definitely took the hardmode approach to adoption.

The list of issues does not seem to stem from whether they had used this build tool (CMake) nor others (nor official build environments).

I have the same thought, my X algo has become less political than HackerNews. I suppose it depends on how you use it but my feed is entirely technical blogs, memes, and city planning/construction content

I mean if I want two day/fast shipping, it's still the only place that can do it without costing me $45, and even then a lot of places won't get it in the mail that fast. They also have a much more reliable and robust return policy, which is a headache for other sites. While I agree the experience has worsened it's still the best online store as far as I'm aware

This is something Electrek does regularly and isn't unique to this article but I don't like how they suggests the Tesla crash reports are doing something shady by following the reporting guidelines. Tesla is reporting things by the books, and when Electrek doesn't like how the laws are laid out they blame Tesla. Electrek wants Tesla to publish separate press notes, and since they don't they take their frustration out on the integrity of the article, which is worse for everyone.

According to the OP, all other autonomous driving companies publish complete accident reports.

This is (one of) my point(s), Tesla does publish accident reports to all the major government agencies, and then those agencies make them public. Electrek wants a press packet, which Tesla isn't doing for them. In response, they try to make it sound like Tesla is shady and hiding things, or otherwise acting in some nefarious manor nobody else could think to act in. It feels disingenuous and will only serve to hurt autonomous driving optics for all companies

> Tesla does publish accident reports to all the major government agencies, and then those agencies make them public.

Electrek says they aren't made public, if I understand correctly (?). Do you know where the public can access them - do you have any links?


My thought too, HR’s only care so far as they have a range they need to stick to. I don’t like to be too specific but I usually suggest my salary, possibly higher, as a minimum

I’ve also noticed this, and it causes real issues long term when you want to build the product. Suddenly management is surprised your senior engineer with no relevant experience is taking a long time and needs to bring in a half million in consultants to actually do the work. It stresses everyone else out and then you end up with a lot of churn, a lot of burn, and very little internal knowledge to build off of for the future

I’m not sure this article really applies to my experience. There are lots of companies who have extremely rigid pay ranges, and if you ask for wiggle room on a low salary they just move on to the next applicant. You should apply to jobs because you’d rather work there, and should come in with minimum salaries you’d accept. Thinking you’re going to negotiate 50k more after holding an offer in your hand is a good way to have the offer taken back

When Tesla engineers/Elon talk about it it's usually pitched as a safety thing, by standardizing on one sensor they reduce "sensor contention". Famously Karpathy once described radar as a source of noise that held their vision sensors back.

I don't know who will end up being right in the long term, however I don't think this was a form choice, I think they believe a pure camera system will be more functional.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: