They don't follow basic design principles. If i have to tell the ai every detail of basic design then... Well... I do not consider that very intelligent for a software dev.
I do use AI extensively and get it to spit out vaguely acceptable designs. But I'm doing the design. Even when i have another agent trying to simplify or such the design details are still me.
I don't think people understand how this runs in contrast to the claims of intelligence.
Everytime i read one of these vibe coded projects i wonder: Is AI capable of building well structured programs? Designs with strong separation of concerns. Clean code. Short, well defined functions.
This is not how I'd design much of this. Does that matter? AI and whatever training data used seems to differ.
I'd love to try these new phones. My current phone (Google Fold) is terrible. However
1. google pixels are the best android devices AFAICT. Not a high bar, but that's that.
2. due to the prevalence of spam and scam calls: Not having an AI call filtering is a no-go. google pixel's have a really nice call screen.
Course we could have a competent government that would do something about scams (besides encouraging and supporting them). Then small business could actually compete. But the best we get is a rapist and scam artist.
I left amazon, in part, because of this realization: Much of management was exactly doing that. That was back in the BERT days and even then writing was on the wall.
How do you educate people on stream processing? For pipeline like systems stream processing is essential IMO - backpressure/circuit breakers/etc are critical for resilient systems. Yet I have a hard time building an engineering team that can utilize stream processing; Instead of just falling back on synchronous procedures that are easier to understand (But nearly always slower and more error prone)
I use Jira a lot and... there are keyboard shortcuts. There are keyboard shortcuts for Confluence.
I did not know about the jira shortcuts until recently. Not really a huge deal for me. Seems like linear's are definitely better but shrug. Keyboard shortcuts are not the source of my issues (ha!) with issue trackers.
Confluence shortcuts tho. I'm pretty sure I'm the only one in my company that knows them haha. Which says something about confluence for sure.
You're welcome! I think akka has been making great strides in polishing the rough edges. (Along with the rest of the Scala ecosystem TBH). Unfortunately that doesn't seem to generate the hype I'd argue akka deserves shrug
I've had good success with akka at multiple companies. At Protenus the core ETL is based on akka streams. Which has worked great. No notable issues. Tho we don't run in clustered mode.
At glngn we didn't use akka streams (outside of akka http) but did use event sourced, persistent entities powered by akka typed in clustered mode. Deployed to k8s. Which definitely took effort to set up nicely and enable smooth deployments. Our clusters were not huge so many problems did not show up (split brain).
I haven't used other systems that provided an equivalent to akka typed persistent entities. I can't compare akka in that sense. However the event sourced persistent entities model is really, really effective. Definitely a different paradigm: some stuff is trivial that would otherwise be a trial.
I suspect many of the benefits could be achieved by using something like Kafka feeding non clustered nodes. But never tried.
I do use AI extensively and get it to spit out vaguely acceptable designs. But I'm doing the design. Even when i have another agent trying to simplify or such the design details are still me.
I don't think people understand how this runs in contrast to the claims of intelligence.