Once I digest some of this and give it to Claude, it's mostly smooth sailing but then the context window becomes the problem. Compactions during implementation remove a lot of important info. There should really be a Claude monitoring top level context and passing work to agents. I'm currently figuring out how to orchastrate that nicely with Claude Code MD files.

With respect to architecture, it generally makes sound decisions but I want to tweak it, often trading off simplicity vs. security and scale. These decisions seem very subtle and likely include some personal preferences I haven't written anywhere.

This isn't about anthropomorphism, it's context engineering. By breaking things into more agents, you get more focused context windows.

I believe gas town has some review process built in, but my comment is more to address the idea that it's all slop.

As an aside, Opus 4.5 is the first model I used that most of the time doesn't produce much slop, in case you haven't tried it. Still produces some slop, but not much human required for building things (it's mostly higher level and architectural things they need guidance on).

To speed things up we decided to correct the ID types for the server response, which was key since they were generated from protobuf. But we kept everything using number type IDs everywhere else, even though they would actually be strings, which would not cause many issues because there ain't much reason to be doing numeric operations on an ID, except the odd sort function.

I remember the smirk on my face when I suggested it to my colleague and at the time we knew it was what made sense. It must have been one of the dumbest solutions I've ever thought of, but it allowed us to switch the type eventually to string as we changed code, instead of converting the entire repos at once. Such a Javascript memory that one :)

Given a dumb TV is going to be more expensive, I can't see a market for it based on a small marginal gain for the consumer. And 90% of people don't even care enough about the poor user experience vs the marketing that hypes up features no one uses or needs.

Comments URL: https://news.ycombinator.com/item?id=41872632

Points: 3

# Comments: 0

For those unfamiliar, Product Lifecycle Management (PLM) is software used to track the lifecycle of a product (and it's parts) from design, through to manufacture and distribution.

My team are software engineers from hardware backgrounds, and we've built Bomello (link: https://bomello.com/) by borrowing systems and concepts from the software world, where development practice is light-years ahead of hardware.

One of our key analogies has been to Github - which shares some similar purpose to PLM. Like Github, PLMs are the centralized data store where engineers input their work, so that rest of the company can deploy it into the hands of users.

We see the current landscape of PLMs as ripe for disruption. The market is highly fragmented, and polarized. Older players (such as Arena), work well to develop structured development processes, but are overly complicated and often require a dedicated engineer to administer. Newer entrants focus on flexibility, or introducing brand new technology such as AI. On this side, workflows and process take a back seat - which in my mind should be the core of PLM.

What we've built focuses on workflows, centered around a detailed review process with side-by-side comparison of incoming changes. We guide development process towards industry best practice, using modern UX inspired from software dev.

I’ve been a long time fan of HN, but this is my first time starting a company. It’s been just as stressful and exciting as expected! I would really appreciate any feedback, so let me know if these ideas resonate.

A note on PDM:

Product data management (PDM) is a different class of software, but key to PLM (and is often included). PDMs are focused mostly on the engineering users, synchronizing their work such that it can later be reviewed and released into the PLM. Some parallels could be drawn between PDMs and git, although functionally they are very different. We currently aim to be PDM agnostic, as they are typically tied to users’ CAD choice and deeply integrated. However, we have not ruled out building our own PDM in the near future.

Comments URL: https://news.ycombinator.com/item?id=41799045

Points: 2

# Comments: 0

Edit: ah! I think you meant engine immobilizer

I was under the impression for quite some time that it wasn't that bad to have 2-3ms latencies compared to a co-located DB which is typically <1ms. However, we recently switched from Neon to a colocated, managed db and there was a huge improvement. Some of our queries were executing sequentially (due to our ORM, Prisma), and so what was a 3 second transaction was reduced to only 1 second. Yes this could be rearchitected better, but it illustrates a major floor in my mind for these companies providing only a DB.

Managed vs. unmanaged is a massive difference and would be worth it. But these days I was under the impression most hosting companies also offer managed DBs.

Are these reviews completely paid for? What's going on here? Or are all the options awful.

I am in the position to choose our provider at our (small) company, but between Gusto and JustWorks and the majority of our employees being in Texas there was slim to none options except united.

It seems like the alignment you refer to inspired the launch of Voyager 1 and 2 because they could visit so many planets at one time, and indeed it did slingshot them at quite some speed. However newer launches have reached similar speeds, and will escape the solar system due to improvements in launch technology.

$160-185k base, with founding engineer equity

Looking for a founding fullstack engineer who will work alongside me (CTO of Bomello), as a peer, to build out a product from scratch. As revenues grow, I am committed to only hiring experienced and self-starter type engineers so that we can do more with fewer people.

Starting date Jan 2024, but we are flexible.

Message me via the email on my profile, or https://www.linkedin.com/in/roberttod/

Tech stack (open to change): Vercel, Typescript, React, RedwoodJS, Postgres, GraphQL

If this does indeed become world-changing, leading to AGI, then the best hope we have is that those with all the power are ethical. Giving it to everyone could be chaos. Giving an advantage to other superpowers would be terrifying.

Not ideal, but in their position I can't think of a better alternative. I am not saying I want anyone to have AGI btw, just that this is going to happen eventually (perhaps not via OpenAI/GPT) and getting there first may be game over for all other parties.

> Technology progresses more or less independently of the stock market.

Progress could be defined in many ways, but sure as hell there is less money in the tech sector, and funding is very difficult right now as far as I understand.

I do agree with the sentiment that the market shouldn't affect your timing if it can be avoided, but I wouldn't expect it to be very easy to start something capital intensive with a long road to profit right now...