throwaway7783

What do these workflows do? I can't think of anything that needs to run for so long.

.. by hiring the right humans - which is not always a given

Lots of downvotes and one condescending remark, but no knowledge shared :(

Does anyone think here shortselling should be banned?

Very cool! Adding a client geo would be nice (even if its not very accurate)

No one is in denial. The parent post is just explaining why, and not that the problem doesn't exist.

The biggest issue we have is the mindset of the common (wo)man, regardless of why it is the way it is.

Right after the Islamic and British invasions

This has been my experience as well. Something happened 2-3 months ago with Claude Code. It got slower, starting spinning and getting stuck more and more. I gave codex another shot out of my Claude frustrations, and have never looked back again.

Just tried Claude Code yesterday, and nope, it's the same old bad.

A dirt yard is sufficient if it was to show off land. Grass is not required

In SaaS quality is one of the problems that cause churn. Value,price and politics also play a big role - now matter how good or bad the product quality is

Re: bad design decisions - This can be said about any technology.

..and HA

In most half-decent codebases, including LLM generated ones, adding new features almost never requires a refactoring in my experience. It is almost always when you are fixing bugs, improving performance or changing core behavior.

I think we have to wait and see if long term maintainability will be any different from human coded software. Every single long surviving human written codebase I have worked with, has significant amounts of tech debt and large pieces had to be rewritten from time to time. This is of course anecdotal and I'm sure clean and elegant old codebases exist somewhere.

How does this work in a production setup? Can this be set up like a server, or is it mostly for individual users to play around with data?

This. I hate VSCode as an IDE and is the reason why I have not used Cursor. I wish Jetbrains actually had some brains to build a better coding agent inside their IDEs (which I think are one of the best out there), but for now Im stuck with codex/cc + Jetbrains IDE

"We only need to consult the database for the user's secret..." , which kinda defeats the purpose.

LinkedIn doesn't have any redressal mechanisms for anything. Someone I knew went through a lot of abuse by a LI user and kept making new accounts to harass. LinkedIn's response - "We did not find anything that violates our ToC". No wonder it has become a cesspool of spam, fraud and abusers.

a.k.a the vaunted "Ideal Customer Profile". This is really critical for many many things in business and life.

Can you please elaborate on the differences? They are practically interchangeable, but conceptually there might be another layer on top of entities and relationships for somewhat richer semantics (like describing a relation, or additional annotations on the entity)

Yeah, but now this is implicit information (no price == marker row) and duplicate the entire row. And it is baking in "price" as the special field. This may not be just one field for another temporal entity

Works when there is always an active price. Having an explicit end date allows certain rows to be inactive automatically after validity period. Think of seasonal categories/products etc which dont exist after a specific period

It is at the org level

True, it is the only objective signal, but as you have observed as well, it is also a very poor one.

I said it in another thread. Yes, of course we cannot match the local store interactivity. What I mean is coast to coast RTT is 65-80ms. And the server can be optimized to return back basic operations (adding a comment, a new ticket, reading one back etc) can be done within tens of milliseconds, keeping the entire thing under 100ms coast-to-coast. If one can colocate servers with users, it becomes even less. I'd rather to server side "reconciliation" than do both (because serverside thing doesnt go away even with localstore, it is just deferred).

Based on all the comments above, it is very debatable if it is a better product all said and done

100% agree. A traditional CRUD app (like Linear) can be made pretty low latency without local-first. The complexity is not worth it.

Writing an eventually consistent database is hard, it maybe fine for Linear's use cases, but not knowing if my updates made it to the server (aka my team),is problematic. The sync lags have created untold problems in other projects I have worked for, so I always go for a synchronous solution. All the fancy stuff comes out only if it's absolutely needed. I'd rather optimize my server to be blazing fast, and have the user "suffer" network latency.

Even if we forget "rockstar", there are certainly different levels of engineers. More experience doesn't automatically mean better either. That is not to say experience doesn't matter. It matters quite a bit. Sure , good interns can sometimes have good feedback or spot mistakes. But not consistently enough.

All of this to say that it's not just experience that makes one a better engineer.

Sure, but the context here is only about code.