5,356 karma · joined April 22, 2008
https://www.grandviewresearch.com/industry-analysis/bakery-p...
What I would be curious on is tracing from errors back to the source code. Nearly every language I’ve used prints line number and offset on the line for the error. How that worked in the Diana world would be interesting to learn.
Montreal likely doesn’t do it because it would lower the density of buildings.
A true pivot of Kodak was moving from just doing chemicals for film to doing chemicals for the pharmaceutical industry. That actually involved employees changing what they do, changing factory equipment, etc.
There is a good basis to this. Every new mile and station you add to a system compounds on the size of the system. The 11th station connects you to 10 places. The 51st station connects you to 50 places. Build small and you never get the critical mass needed to see widespread adoption.
I don’t know of any real estate investor who doesn’t use mortgages. The norm is interest-only mortgages and not paying down principal at all.
I mean the first sentence about enumeration and efficiency just shows how shallow the discover article is; the whole area of optimization is about efficiently finding optimal solutions without enumerating all possibilities.
1. You have to remember all the technologies you need included, my company template already has them.
2. LLM doesn’t have a standardized directory structure, so you end up with different projects having different structures and file naming conventions. This makes later refactoring or upgrades across multiple projects less automatable (sometimes this can be solved by having an LLM do those, but they often are unsuccessful in some projects still)
3. LLMs have a knowledge cutoff. If your company has already moved to a version after that knowledge cutoff, you need to upgrade the LLM generated code.
I very much prefer having a company template to asking an LLM to generate the initial project.