The behavior attributed to Indians in the article is universal. Admission to few college seats is a zero sum game anywhere in the world.
In SF, see if companies share knowledge if they are after the securing a contract from the same B2B customer.
In UK, drivers give way as a courtesy many times even though one has the priority. In return the other driver thanks using hand gestures. However, there was a local football match on a weekend and parking was very hard to find. Parking spots are zero-sum game. People started violating many rules. People started driving against the arrows on the road in desperation to grab the spot. Parking in places which were not marked as parking spots. All the manners & niceties went out of the window. It has hunger-games for parking spots.
BTW, google (and other big companies) hiring top graduates and researchers to deprive others of the same talent is hoarding.
Welders, millwrights, machinists, carpenters, lots of trades have qualifying interviews. I’ve taken written exams in interviews for machining and welding as well as hands on show me parts.
Not that I agree with absurd interview process of software development but they often see themselves more akin to attorneys than tradesmen. The difference being attorneys have to pass a bar exam and even trades have journeyman cards to provide credibility.
Software development has none of that. Real engineering has PE licenses but how do you achieve that in such a broadly scoped field of software development?
We either play the interview game or find a way around it.
I may have a outdated notion about the trades you mentioned, but I have seen an "apprentice" model a lot. I have seen it with a masonry where the experienced guy was bringing in his nephew and teaching him on the job. A lot of these trades are family owned and have seen taking in people based on someone vouching for the new guy.
Maybe this varies country to country. I have seen this in India and UK atleast.
In UK atleast there are trades like roofing, landscaping, exterior building cleaning, masonry, tree surgeon etc which I have seen them are mostly family based.
This trade has never helped itself by insisting on being taken for a profession. A lot of these kids have never known the joys of time and a half - or the incentive that gives management to try to have all their s—t in one sock, every once in a while, for a change.
Right. Acting. It isn't more difficult for men because their part is, uh, hydraulically obvious. More to the point, it isn't less hard work for women. I get why guys assume it would be, though. Good grief, I bet you probably think you've never seen anyone fake an orgasm outside a porno, too...
Someone has reflexively taken offense at something here. It's clear who and I think I see what, but I have to confess myself still mystified as to why.
All I've said is that women also act and that's also hard work. I didn't say it is the same job, only that it is no easier. Why does that bother you so?
Young men are adorable, but really I feel for you. What you really desperately need is a role model, the same way I did at your age. None is to be found here.
So it's less smart than that. The smaller page size sounds like a sensible probably a sensible call (that I didn't make).
2, 3 and 4 are spot on.
Theres's two connection pools one for reads one for write. Writes are batched every in a single transaction every 100ms and renders are pushed out to each connected user if there's a change max every 100ms (with back pressure). Reads are read only, and writes are transaction mode immediate.
Here's the schema:
CREATE TABLE IF NOT EXISTS cell(chunk_id INTEGER, cell_id INTEGER, state INTEGER, PRIMARY KEY (chunk_id, cell_id)) WITHOUT ROWID
Each user render is querying 2000 rows that then get converted to html elements, compressed and sent down on every change (including scroll). But, because renders are at most every 100ms changes effectively get batched.
On the whole this is relying on the brute force of SQLITE rather than anything too clever (eg: Hilbert curves or encoded chunks).
The point is that there could be any number of states. I wanted this to be quite general as for me this is more of a CRUD app demo.
That's a good idea. I should probably mention it's hypermedia too.
At some point I'll write up a blog post. Virtual scroll was surprisingly simple in the end and mostly leverages CSS grid.
The funny part, is it't not really about Datastar (I use a fraction of its features). It does make pushed based hypermedia simple which opens up a lot of options.
Clojure/JVM and SQLITE is where the interesting stuff is happening for me at least. I guess that's the nice thing, Datastar gets you back to programming in your favourite backend language of choice and then gets out of the way.
If a tech works 80% of the time, then I know that I need to be vigilant and I will review the output. The entire team structure is aware of this. There will be processes to offset this 20%.
The problem is that when the AI becomes > 95% accurate (if at all) then humans will become complacent and the checks and balances will be ineffective.
80% is good enough for like the bottom 1/4th-1/3rd of software projects. That is way better than an offshore parasite company throwing stuff at the wall because they don't care about consistency or quality at all. These projects will bore your average HNer to death rather quickly (if not technically, then politically).
Maybe people here are used to good code bases, so it doesn't make sense that 80% is good enough there, but I've seen some bad code bases (that still made money) that would be much easier to work on by not reinventing the wheel and not following patterns that are decades old and no one does any more.
I think defining the places where vibe-coded software is safe to use is going to be important.
My list so far is:
* Runs locally on local data and does not connect to the internet in any way (to avoid most security issues)
* Generated by users for their own personal use (so it isn't some outside force inflicting bad, broken software on them)
* Produces output in standard, human-readable formats that can be spot-checked by users (to avoid the cases where the AI fakes the entire program & just produces random answers)
We are already there. The threshold is much closer to 80% for average people. For average folks, LLMs have rapidly went from "this is wrong and silly" to "this seems right most of the time so I just trust it when I search for info" in a few years.
It is frankly scary seeing novices adopt AI for stuff that you're good at and then hearing about the garbage it's come up with and then realising this problem is everywhere.
Gell-Mann amnesia. After I saw the subtle ways LLMs can off mark on things I know about, I am very wary to use it for any subject I don't dominate. I don't want to learn some plausible nonsense.
Except that we see people in this very thread claiming they shouldn't review code anymore, just the prompts. So however good it is now is enough to be dangerous to users.
This is how we did it at mailchimp. I think this is ignored or overlooked because this means devs might have to care a bit more about operations or the company has to care more.
That is what most tenanting scale-ups do. "Jumbo"-tenants get relocated either to separate partitions, or to partitions which are more sparsely populated.
