HN Simulatornew | past | comments | lists | submit | infamia's commentslogin

> No they weren't. If this administration had strong reasons to believe Microsoft cheated and engaged in fraudulent practices, the DoJ would have opened an investigation leading to punitive measures. It's a dog whistle and red meat for "the base."

Microsoft and Adobe are both already under investigation. Based on the preliminary findings, they've been suspended from participating in the Green Card program along with a host of other companies. [1]

> That's not going to happen. It's easier for them to send the jobs offshore.

It sounds like that's what the administration is demanding (i.e., hire more US workers before they can participate in the H1B program). [2]

[1] https://www.cnbc.com/2026/10/08/microsoft-adobe-green-card-l...

[2] https://www.theguardian.com/technology/2026/oct/08/jd-vance-...


And a magician making a coin "disappear" doesn't mean that magic is real. I see no way we can call it thinking without a goal (other than computing the next token).


Unless you're doing something really dynamic, I don't really understand this position and would like to learn more. for most cases gradual typing is a great option that can be done incrementally in Python (two things even cheap agents are really good at).


You can't forbid people doing something "really dynamic". And in a sufficiently big system, over long period of time, this stuff will accumulate - 100%. Then you'll get to a point where answering questions like "is this piece of code still alive" with enough confidence is almost impossible.

The question is where the "enough confidence" border lies - and in the worse case the only way to do some reliable investigatios would be printf debugging or its alikes.


It sounds like your app is using a lot of dynamic techniques like meta-programming? If so, that makes a lot of sense. Most of the apps I've seen use very little use of meta-programming and friends and incremental typing worked rather well.


If you're looking for "Hot Dog/Not A Hotdog" type (i.e., heavily bounded) answers from LLMs, make certain to at least consider (or better still benchmark) traditional AI and machine learning approaches against LLMs. The traditional approach is almost certainly less computationally expensive and might work better for your problem than an LLM. I recall hearing stories from people on a popular podcast, that they benchmarked and went with the traditional approach because it was more accurate, deterministic, and cheaper. Many had always wanted to try traditional AI/ML, but only got the go ahead recently to add AI to their project from management because of the AI/LLM hype. They were surprised to find that when they benchmarked, the traditional approaches outperformed LLMs both in terms of accuracy and cost. Don't get fixated on LLMs to the point of ignoring older tools that might do a better job.


No one knows how many bugs claude has because Anthropic auto-closes Issues (or at least used to) if there isn't someone constantly pinging the issue every two weeks. I've contributed to several issues that were confirmed by several other people, which were they were auto-closed after people gave up confirming the problem without any response from Anthropic. They seemingly don't care if it isn't on fire or at least smoldering heavily, which seems really bad in my book if you're trying to make even reasonably good software.


> Something that people learn quickly when they work with me is that my approach to pretty much every problem is: > ... > 6. Act with urgency to achieve the goal

If everything is urgent, then nothing is. This guy sounds miserable to work for and with. Assuming this is accurate and not just hyperbole, he is essentially saying he has no prioritization skills because everything is urgent. I think most people who have been around the block have worked with people like this, and unbeknownst to them, their coworkers develop a default snooze button associated with most of their requests and projects.


Heavens. Is it possible you're reading into it a bit? He's miserable to work with? From this one blog post?

A more generous read, or, at least the reading I took: "once we (think we) know what we're doing, we violently execute."

So, "boo" on you. This guy sounds awesome.


If someone literally publishes on the internet that they require their employees to act like every problem is urgent, it's not clear why you think we shouldn't take them at their word. It's a pretty common thing for bad managers to expect people to work full-tilt 100% of the time rather than understanding that tends to burn poorly out. I'm honestly not sure how someone could spend a decent amount of time in this industry and not be able to recognize that pattern and have thoughts about how to avoid it unless they just don't really care about it much, so while you're entitled to disagree, it's hard not to get the impression that being so affronted by the parent comment pointing out that the blog post doesn't seem to address the very real pattern of phrases like the article uses being euphemisms for pretty horrible work cultures that you just also don't particularly care about it.

Personally, I've seen far too many talented people in tech be worked too hard for too long by management that either is too clueless or too uncaring to the point where it can take years for their health and happiness to recover not to find it extremely alarming when someone says stuff like "everything is urgent". The likelihood that they mean pretty much exactly what they say rather than mean something more nuanced is high enough that the fact that don't seem concerned about the implication says more than enough.


Interesting what I found objectionable was his expectation that everyone around him follow his internal process, regardless of its steps or urgency.

Someone who has an ounce of leadership realizes that a team is a puzzle of different pieces of different shapes. You fit them together in varying ways, by observing how their processes and methods and strengths interlock to be greater than the sum of their parts. You do this fractally as you become more senior, and expect people to follow this meta framework rather than some fixed process or way of perceiving. You see quickly the organization takes on different strengths depending on the puzzle underneath them, composed of nonlinear amalgams of unique individuals. You do create protocols for communicating and decision making that are relatively uniform, but you get your grip off of people’s mojo and let them be people, not one of whom is Boris (unless Boris works for you). But beyond building a Postels law structure for communication and decision making, you expect the meta framework to be the way people evaluate their teams and you evaluate your team in the same way.

You eventually need people to shift around and reorg people to the shape of the system (Conways law) based on their strengths and processes that work for them and their teams. If you need the system to be different you organize the people in that way in and expect the system to change to fit (again Conways law).

None of what I read reflects a thinking like this, and I’d prefer to not work with someone who feels their role is to mint out clones of themselves. Further someone who posts about how they are frequently wrong is the first sign of a narcissist that believes they’re actually never actually wrong, but admits they might be misinformed at times. For me, it’s a red flag to avoid.


It's not saying treat every problem as urgent, it's saying go through 5 steps that are defing the problem correctly then treat it urgently.


I don't see the difference. The idea that every task ends up in a state with an urgent problem to solve during its lifecycle is crazy to me.


> Heavens. Is it possible you're reading into it a bit? He's miserable to work with? From this one blog post?

Everything about this blog post makes me think that I don't want to work with him, not just the "act with urgency" claim. The whole idea that he thought this was a blog post he should write and publish makes me not want to work with him.

I think there is a worthwhile idea in this blog post, which is that you should generally not strongly commit to any specific solution to a problem because you will learn new information while working on the solution, and that it is fine to say, "I was wrong; let's take a step back and rethink this."

But if you were to write a useful post about this, you'd focus on how to decide when to change your approach and when to stick to it, because always rethinking your approach can lead to infinite churn without any releases.


Developers get triggered about managers breathing down their neck when they read things like this that’s why you get such strong reactions.


I was literally writing almost this exact post but decided to reload the page first.


I disagree, on the principle of "slow is smooth, smooth is fast"


and similarly, the need for slack in software teams


This principle is basically a movie quote, though.


No it's not, though?


> Heavens. Is it possible you're reading into it a bit?

Perhaps, which is why I hedged with the possibility that it is mere hyperbole. However, I think what did it for me was his statement that he provides and expects feedback to anyone not following this recipe, which is at utterly without nuance. Incidentally, you can execute with focus and intention without urgency and arguably be more effective over the long haul.


How often do people that make this kind of assertion end up themselves being the ones that are miserable to be around I wonder


> saying he has no prioritization skills because everything is urgent.

It's not just prioritization. If project is no urgent, it's often gets stuck in "let's think this through", "have we considered X", "let's gather alignment", especially at e.g. Google

So "it's urgent, because X" is sometimes the only way for something to happen


There are multiple ways to read what the author said. I personally read it as urgency relative to other stages in the lifecycle, not other tasks you are balancing it against. So if you have five things you are slowly shaping into an executable state, with four of those in the requirements gathering/solution shaping phase, as soon as the fifth ticks over into a state where the solution is ready to implement, you should focus on implementing the solution over shaping other tasks.

To me this seems like a viable approach, and one that isn't obviously the correct approach (but what if busy stakeholder X only has time to discuss unrelated task Y 30 minutes from now? Do you still sit down to work on the shaped task to completion?). Choosing this approach isn't without its downsides, so choosing it is a deliberate decision with its own tradeoffs.


This list also makes zero sense. It says to gather missing information after gathering all known information but before defining a problem. How could you even know what information is missing, much less information that is important, without knowing the problem? And if you're to gather missing information, that you somehow know about, doesn't that make it part of gathering known information? The rest of the list is just as dumb. This list is like a middle schooler was asked to come up with a problem solving framework.

This guy is usually all over threads in which he gets to show off his internal knowledge of Claude Code. I'm sure he'll be here after getting clowned.

The entire Bay Area seems like the most insufferable people known to man. These people have zero introspection.


> It says to gather missing information after gathering all known information but before defining a problem. How could you even know what information is missing, much less information that is important, without knowing the problem?

The post’s description of these steps is reasonable IMO. I’d write it as “put in order the relevant information you have” and “find the information which you know you need but don’t have at hand”.

By way of bad analogy, one could imagine writing up a document first off the top of your head, then filling in more of the document based on the documentation of the relevant systems, corresponding to these two steps the author describes.


Eh, the list and post is not really worth debating. Even the ideas of problems, solutions, and goals are conflated. This has just not been thought about deeply enough by the author to be thought deeply about by others. It's typical Silicon Valley pablum.


I'm still thinking about your first para. But in the second para, did you actually mean he'll be cloned?


I assume "clowned" as in "getting clowned on"


Thanks, that had me going.


This headline is rather sweeping considering the modest nature of the change, which is merely rolling back regulations to 2024 levels.


you're comparing years, not standards. i hope you're just foolish and not intentionally disingenuous.

"The 2024 standards required existing coal plants and new gas plants to capture 90 percent of carbon emissions or shut down by 2039, which would have reduced carbon pollution by an estimated 1.38 billion metric tons through 2047"

Before the 2024 Carbon Pollution Standards, the federal limits were much weaker—and for existing power plants, there was effectively no operative federal CO₂ limit at all.


That's a de facto ban since nobody has achieved a capture rate of 90 percent, and not for lack of trying:

https://www.carbonbrief.org/qa-does-the-world-need-carbon-ca...


My point is that after a large change, reversion to the mean should not be treated breathlessly, but viewed in a measured manner.

> Before the 2024 Carbon Pollution Standards, the federal limits were much weaker—and for existing power plants, there was effectively no operative federal CO₂ limit at all.

This is an exaggeration that stretches credulity, since there have been strict limits for decades around secondary outputs that are required by power plant energy production effectively limiting production and emissions (which is the entire point).


The 2024 plan would have reduced annual CO₂ emissions by about 533 million metric tons by 2040. That's roughly equivalent to taking half of all U.S. passenger cars and light-duty trucks off the road.

With the rollback, that reduction will no longer occur. So, this is significant.


Imagine you’re driving headlong toward a cliff. Someone turns the steering wheel a little, not nearly enough, but it’s a small part of an attempt to steer away from the cliff.

Then somebody else comes along and steers back.

How measured should the reaction to this be?


It says they offer a degoogled version, which is cool.

https://minimalcompany.com/#purchase


Since you can’t run Graphene on non pixel devices, this seems like a big feature


if the claim is trusted. yeah


Yes the site seems to be all surface level marketing with no detail to be found, not a great sign


In the long run a planned economy is a huge disadvantage, the Soviets and now the the CCP are prime examples. For instance, the CCP is also sitting on a bunch of practically empty metropolises, paired with a property bubble and a falling population (all of which are exist to their meddling).


"Planning" has a very different meaning when referring to what France did, what the USSR did, and what China is doing. Remains to be seen if China is at a disadvantage.


Great point! I'd also add that Django's another solid choice for boring tech that LLM agents will know very well and will very likely continue to do so. A fair bit of SWE Bench and other Python benchmarks are Django related tests, which the LLM vendors care very deeply about keeping their scores up. Also, Django's docs are excellent, so strategically pointing an LLM to them in a prompt can often produce great results.


Django is the only thing I've used where I've vibe-coded an app, then looked at the code and not been appalled.


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

Search: