sebastianconcpt

Surprisingly close minded and selective read. That way you'll see black swans even in paradise (or the whatever utopialand of your choice).

Quite some time ago I said and now repeat:

Convenience is to humans, what bulb lights at night are to bugs.

Ok fair, thanks for explaining

I am the only one surprised about anyone's need for a study to conclude that?

Mark these words: The chances of this being an unsolvable problem are as high as the chances to make all human ideologies agree on whatever detail in question demands an ethical decision.

Nice. Sounds like will converge to QA as a Service

> I am currently writing much more, and more complicated software than ever, yet I feel I am not growing as an engineer at all.

This sounds like approving bad/poor abstractions too prematurely and keep building on top of that.

What about the satisfaction that comes not with struggling but from the calmness of an elegant functional model that dynamically covers all the flows and all the edge cases you could (deep and slowly [1]) think about?

[1] maybe refining in different days, in the shower, after recovering breath in a hard set in a workout session, after a nap...

India pays one 1.4 GW nuclear power plant in yuan and they start talking about global de-dollarization as if people can't think in proportions anymore?

Someone inside and up there neglected the "a bicycle for the mind" part of the vision.

Pity they don't have their own thing at that level. They had a great start introducing Siri then totally missed the train.

And how China compares its 2024 to 2025?

But at that point why not Rust then?

But how would you do what in Rust's Tokio is a `spawn_blocking` in Swift?

In Cursor you have Sandbox mode to deal with that issue?

I feel more like is forcing to write better engineering not just the code.

The disruption comes from the economics of cognitive labor, the synthetic assistants are making feasible things that before were unbearably cognitively costly so manually we invested all that energy into the code parts.

I've made this to leverage that:

https://github.com/sebastianconcept/ai-squads

Isn't plenty of space of efficiency value in SaaS over AIs? And depending on the use-case and what the optimization is, also performance?

Only depend on platforms as redundancy. Never as primary source.

Break that discipline and you are exposing yourself to this danger.

The issue is that one of the services is the events hub for the rest to remain in loose coupling (observer pattern).

The criticality of Kafka or any event queue/streams is that all depend on it like fish on having the ocean there. But between fishes, they can stay acyclicly dependent.

Okay yes, agree. This goes inline what I do and promote among teammates all the time "maintain one-way dependency discipline".

Tree or not, it will render you acyclic graphs.

> Why vibe code with a language that has human convenience and ergonomics in view?

Because you would not be able to audit the code if you don't (you'll be terribly slow to read and understand the inner flows correctly and that's if these aren't so bad that would do you some brain damage).

Dang, AI is pushing us all to become managers.

The reports about our death were greatly exaggerated.

Well we need like successful technological disruptions like in 7 dimensions before this can be scale and ROI positive.

Dang. I won't be able to sleep tonight

The feeling of the hang up is so satisfying. An important piece of UX.

Just on bad rule could more than double the cost. Or even put your project completely out of any feasibility region

What's the use case?

Haahahah true! Well put.

No autosaving. That's the wrong way to try to be minimalist.