officialchicken

~85 years prior to the 1915 fair, Stephenson's Planet 2-2-0 steam loco was operating commercially between Manchester and Liverpool (5 built in 1830). The planet was a version 2 of his earlier Rocket already operating between the cities since 1829/30 - utilizing a very design with the boiler between the wheels layout that almost all steam locomotives eventually adopted.

There is nothing that requires a VC to sell part or all of their shares when an IPO occurs. And you can read their S1[0] to verify.

[0] https://www.sec.gov/Archives/edgar/data/1477333/000119312519...

SET TIME ZONE 'UTC'; // or GMT, PST, etc.

Rookie pseudo-footgun - assumed skill exceeds capability error - usually accompanied with blameshifting pronunciation as demonstrated here. Anyone familiar with UTC/tz from another platform (e.g. excel) would be mostly immune or able to quickly identify and remedy.

I really hope this is my last x86-64 CPU, Intel has become an incompetent steward. The "killer feature" for AVX-2(56) at the time of original release was basically lag/jitter-free video playback. IMO, 512 should have never been released for desktop CPUs and restricted to servers. One day I will to switch to a mainstream Neoverse dev box running linux. I also target Cortex-M in rust, so it's got a lot of the typical issues related to missing docs (e.g. bringup of non-heterogenous cores, meaning that M3/M4 still can't be used in a big.little chip)

Reuse is bad / NIHS is good and it's hard to reach token metrics using accepted engineering practices. That leads to the point of having the LLM invent a new specialized job security chip architecture for your IR just to run CRUD app.

I bought a tablet to use with Krita and settled on Manjaro because Ubuntu had so many tablet issues. Everything I tried is especially bad with 4k touchscreen/pen. I started with KDE, then Gnome but DE really didn't matter because they're all so terrible - it's now for watching videos or travel only.

And then the US advertisers came up with "hydration breaks".

There was a case at the highest court in Spain where LaLiga[0] sucessfully claimed that illegal streaming was causing hundereds of million of euros in damages. They essentially petitioned for mass blocking of IPTV, causing Cloudflare, NordVPN, ProtonVPN and a few others to get caught up in a sloppy and stupid dragnet. Whenever there is a football match on, a not-so-small chunk of the internet becomes unavailable. After the match is over, it works again.

[0] https://www.laliga.com/en-GB/news/official-statement-in-rela...

Or is it? Could it be the well established low-effort tendency when the dominant culture is shopping centers, vehicles, similar eating establishments, and the style of suburban housing to a large extent? That would surely encourage the LLM to emit in a similar manner. That sameyness provides a signal of comfort and familiarity.

Building the thing right > not building anything

Building the right thing != not building anything

Seriously, Are we nunchaku yet? If so, I would like a Bruce Lee edition in classic yellow.

No company is measured by "value provided" on any market, it's a feel-good metric. And you\re playing word-games now despite even saying you're not trying. Like I stated earlier, it's entirely a sophomoric take. And now I understand why.

I've been looking for a site like robotica.dev that pulls together news and events from multiple sources. The funding page is awesome and unexpected, a really useful mini-crunchbase for robotics.

I can't agree with 4 - it's sophomoric reasoning at it's best. The code is the product, it's what the system (human/ai/factory/combo/etc) is producing. The IC will always be more familiar with the nuance and the implications of the decisions than the manager. There is only one real stat to track - profit. As for the size of your team, not all human developers are equal, but agentic tend to behave similarly. A small team of highly coordinated things will always outproduce a pile of generic ones acting will little or no methodology. Please deeply re-evaluate at a philosophical level what quality over quantity really means for delivering outcomes.

Trained to obey? More like instructed to obey in an observable manner.

Magical LLM pixie sprinkles ... is that where magic smoke comes from?

Hanlon's Razor - Never attribute to malice that which is adequately explained by stupidity.

The security requirements are well beyond "sandbox". Which have problems with kids pissing in them. They need pristine clean rooms and fully isolated (physically) and partitioned networks.

Me too, despite being delightfully surprised by the BOM widget in the article.

The balance sheets of the AI providers are pretty clear on this ownership thing: I shouldn't own it, NVidia should. Instead, I should pay at least once a very large amount to initially produce it. And then I should have a recurring usage-based monthly fee - for a license allowing me to say it's "my code". That's on top of hosting fees, etc.

Is it though? It doesn't need to be perfect to last. Good engineering practices certainly embrace timeless concepts. I understand if you are working in a feature-factory, but creating inheritable code should be given more consideration however much programmers dislike thinking about things like ROI.

I can only guess dang is on vacation.

Consider applying for YC's Fall 2026 batch! Applications are open till July 27.

Also, "better" is doing a lot of lifting here, meaning it still fails regularly.

This isn't the first year either; maybe US tech companies should start obeying the laws.

Totally agree; we're approaching a time where a single processor has hundreds of threads - it's a conceptual limitation of the author's preferred language that was never considered due to it's ancient 75-ish year old design. "Use the right tool for the job" has never been more important, versus "I have a hammer, everything is a nail"

I don't use the the builtin testing framework, or std, and I often explicitly use a no-heap crate. Check out Embassy and you'll be free to ignore pretty almost everything suggested here, especially when developing and testing. I create a separate [bin] for each test (I usually run out of flash to fit all the tests into a single binary), and a few lines of bash/python to make a test runner/reporter for all the flashing and running of tests. Sometimes I flash up to 50 times a day and haven't lost an MCU (AVR-Rust, ESP-Rust, STM-Rust) yet due to too many writes.

[0] https://github.com/embassy-rs/embassy

Being a curmudgeon is not good engineering leadership. "Seeing everything" is just old people being wistful, not actually contributing or doing in the now. I deployed (via ftp) my first site before Netscape so I do understand where you're coming. There isn't at present a valid or detailed criticism of why X won't Y based on all of that supposed XP - so why mention it? Educate us - why will it fail? Is it because you never mastered CDN's or the exact opposite? It certainly doesn't lead any credibility the assertion that A will become Z because they look similar or embrace similar ethos.

What does this have to do with startups?

> I had to look what "clinical failure rate" means

That should have been the end if the comment; the follow-up by demonstrating such expertise just has me laughing.

Are you the person paying for the hallucinations, or do you just like the free high?