It would seem likely they were consumed by the proximate concerns of evading notice and making it to the plane and had no idea or thought about the dangers of being at such high altitudes.
There are enormous pressures on a new parent -- stress about getting back to a normal work routine and lack of sleep compound into a unique kind of stress and things start to slip.
For me: I decided I could just slow down a bit. Standing out isn't worth the stress. I don't want to slack, but I don't feel compelled to cram productivity into every moment.
3x more than the Marine Corps, for those at home keeping score.
A military branch (either de facto or de jure) that exists for the majority purpose to directly target, round up, and imprison or deport individuals on U.S. soil - especially with a proven record of limiting due process - should have NEVER happened. I cannot stress enough, we're a few bad days - and more and more likely 1 executive action away - from at-scale "Tree of Liberty" stuff.
We were 38 with our first. I strongly agree that is too late to have them, especially given the likelihood of birth defects. Thankfully, we avoided issues there.
A few years in and I feel "back on my feet", but it was harder for being older.
At face value, I think I agree -- especially the format of the website being in a sort of hand-designed style.
"Assembly Theory" is a sort of applying (kolmogorov-esque) complexity theory to physics and other natural sciences. I don't know much else beyond that it's a "real thing".
So with that extra background, I give it a pass. I think it's an interesting idea at least.
Sort of both. I believe there are massive polarized forces that invest heavily in understanding and gaming the system. Sort of like a big multi-player game of tug of war .
The system must be understandable or people wouldn't incorporate and collaborate on extracting an edge. Slack in the system represents a lower price point, which will be corrected by a corresponding purchase order.
An individual has an effect, but it's miniscule compared to the massive forces in play. Unless you have a TRULY novel analysis of a situation, you are going to have a very low probability, success rate and out competing the market.
My understanding is the notion is about getting an application to "work" without any underlying theory of operation or evaluation of the imported context.
Supabase is really tough to make secure, and it is probably a poor choice if you are interested in vibe coding. Row Level Security is likely to be insecure if the author author doesn't have a deep understanding of Postgres or isn't paying careful attention to all of the generated code relevant to the database.
Is there a low-code backend/full-stack which is secure by default? I remember some clunky UI to define filters and projection in Firebase. Can a Django/Laravel app weekend project get there before Supabase?
Just "vibe coding" something minimal in a Cloudflare Worker, or even, ironically, a Supabase Edge Function that directly connects to the DB would 9 out of 10 times lead to something more secure than using RLS. The LLM will always default to RLS when using Supabase as that's what they promote the hardest in marketing materials, so that's what it's trained on.
Secure by default? No such thing by virtue of the fact that security is case dependent.
That said, all of the full fat frameworks make it pretty easy to define what should and shouldn't be visible to what users, the use case that he has would not have been harder to do using rails, phoenix, django, etc as a backend, and it would have been very easy to control the failures that he had.
It doesn't have to be full fat, it can be literally anything as long as it provides a backend layer inbetween the DB and the FE. It can be a single Typescript file that uses literally whatever the LLM defaults to, probably Express given its training materials, or Hono for something more modern, or any of the 1000 other options.
I think that this is the answer. Maybe someone who is great with Postgres Row Level Security will have an OK time with Supabase security, even if they are vibe coding. They wouldn't think of asking the AI for something that won't work.
Right. There are two problems with software generally like this: interface and culture.
Becoming expert at a tool like git involves building familiarity with the concepts involved. While it's not entirely hidden in the --help and manual pages, the descriptions provided there do not consistently use higher levels semantic descriptions of the transformations. You are REQUIRED to look elsewhere to understand or worse -- develop a privately held theory of what's actually happening.
Culturally, a lot of engineers have a basic ethos of "getting things done". Getting the job of the moment done is a "win". There are tons of how do do XYZ articles that are separated from "why" and unmarried from useful additional context.
Like, one should be proud of learning a new tool, but it shouldn't be a personal endeavor to conquer Everest. I think it would do a LOT of good for tools -- especially collaboration tools -- to have completely standard introductions that the community enforced in collaboration. "Oh you don't know XYZ? You probably haven't read the standard introduction."
> And you DO see companies laying off people in large numbers fairly regularly.
Sure but, so far, too regularly to be AI-gains-driven (at least in software). We have some data on software job postings and the job apocalypse, and corresponding layoffs, coincided with the end of ultra-low interest rates. If AI had a recent effect this year or last, its quite tiny in comparison.
Layoffs happen because cash is scarce. In fact, cash is so scarce for anything that’s not “AI” that it’s basically nonexistent for startup fundraising purposes.
