ak39

Please don't stop there! How did the conversation go? How did he convince you that you won't be double-crossed?

Terminating a bus factor 1 employee is not the problem. The real problem is not recreating BF1 reloaded with the new hire. Even a team of two is not completely ideal.

Many, mostly small, companies just cannot justify an IT department to mitigate Bf1/2 risks. Also, most times this bus factor problem manifests in non-IT jobs too: sales, contract law, accounting functions.

Small companies need to first become big companies to afford de-risking from BF1. Part of the growth story really.

Nice!

Finally: https://youglish.com/pronounce/been/english?

"Been" pronounced "bin" is slowly moving to "ben" (mostly in the US usage).

LOL. What did this comment (no pun!) do for your HN karma points?

SQLite not supporting "stored procedures" is a deal-breaker for me. The idea for stored procs is not to "put the process as close to the data" but simply that we have a single place for language-agnostic encapsulation of data procedures.

Paul MM Cooper's podcasts and video essays on YT are excellent. There's info on Mansa Musa in this episode: https://www.youtube.com/watch?v=GfUT6LhBBYs

A whole new generation of developers is learning what the previous generation termed "briefcase applications". When client-server applications were the thing late 90s and early 2Ks, internet speeds were a serious limitation. This forced many architectures to work with "local-first", disconnected dataset, eventually-synchronised desktop applications. Microsoft ADO famously touted the "disconnected dataset" for this after Borland's "client dataset" pioneered this concept for the Windows desktop. Eventually even Java got disconnected datasets. All these techs more than two decades ago had real practical problems they solved: one of them I worked on involved collecting water flow data from several thousands of rivers in Southern Africa. Hundreds of users had mobile laptops that fired up desktop apps with authentication and business rules. Users then came back to head office to synchronise or used a branch with network to upload.

They worked and they were necessary.

Things changed when internet connectivity eventually became cheap and ubiquitous and the complexity of developing such applications then didn't merit the effort.

Now, the swing back to "local-first" is mainly for user-experience reasons. The same theoretical complexities of "eventually synchronised" that existed for the "briefcase app" are still present.

Is the complexity worth it though?

Slightly off-topic:

The top Reddit response cites some good reasons why this may be so. The writer mentions they needed to move from Node to improve "throughput" (and .NET was suggested). In what way would .NET improve performance that Node can't satisfy. (Isn't Node's worker thread sufficiently close to ASP.NET, ISAPI multi-threaded scenarios?)

Does it handle stock splits, consolidations, dividends etc? Calculating returns (basically tracking growth) is a non-trivial problem.

Always use surrogate primary keys. Use alternate keys (AK) for your "natural keys". Modify the AK business rules as and when needed. There are several advantages to using meaningless random integers, sequential integers or UUIDs as your table's PK. The most important one is that if the PK participates (or is expected to participate) as a foreign key in other tables, it's crucial to us a design where you never ever have to change the PK!

I’ve never truly used DISTINCT and felt comfortable for using it. Always felt using it revealed a design smell in my query. (Been doing SQL for 30 years and still!)

2019?

"Probably the fundamental problem here was a sub-optimal schema, but sometimes you're just working with what you've got. Plus a commenter on Reddit pointed out that if we used pure SQL functions instead of PL/pgSQL, we'd also have seen better performance then."

So, would the better advice not have been to use simpler SQL instead of complex recursive statements, instead of taking a drastic approach to abandon ship (move logic to a completely new layer)?

Also, if you're doing string concats manually for your Json, this might cause some overhead for larger objects. ??

You can horizontally scale the database directly.

"2. Push all your application logic into Postgres functions and procedures"

Why are functions and procedures (an abstraction layer at db layer) considered harmful to performance when the same abstraction layer will be required at the application layer (introducing out of process overhead and possibly network traffic)? I don't agree with this advice. (Or I don't understand it.)

A few "give it time" replies is emblematic of the culture of "chalega" ("it will do") in Indian commerce. This is hardly what Apple will tolerate.

100%. My projects are DevExpress heavy.

Embarcadero insane pricing of Delphi is the reason I haven't continued beyond my old version Xe2. I guess they are making hay while the sun shines with the locked-in customers.

Not being snarky: what's the risk of using UUIDs for session tokens if they are created by the server/db and are always verified by server (db) (for authorisation etc)?

Same. Do you have any guess when this is likely going main branch?

“That’s one heck of a nurse” after hitting the Nuke button which was right next to the “Nurse” button.

Can you guess which music video that’s from?

Thanks for this. I have yet to read Blood Meridian. I have read The Road and NCFOM. Both were great and absorbing reads. But I have one major gripe with CM (if I am allowed to do so). It's not his style - in fact it's his unique and great style of writing that would make anyone forget about what I'm going to say.

My problem with CM: his themes of post-apocalyptic, desperate humanity at war with itself and the singular savagery of ONE man against all - takes the assumed position that humans by nature (generally, of course) will almost always reduce to selfish savagery even to the point of normalising cannibalism. Of course, he needed to create this assumed backdrop for many of his stories (eg The Road needed this literally visceral danger for a father to demonstrate his instinctive protection for his only son) but CM's imagined scenario of a society that's eating itself is far from real evidence we have seen of humans. Real evidence shows that during catastrophic moments like earthquakes and prolonged famine and even war, human societies have shown remarkable strength to save and to protect and to help one another, sometimes at great individual sacrifice.

I know you can't criticise a work of fiction this way, an author is entitled his artistic philosophy and outlook. But when the writing is so masterful, when the rest of the philosophies of the stories are so elevated and cerebrally engaging, one can't help but find the story of humans cultivating others for food jarring and out of place.

(This is my first "criticism" of any work of literature.)

And yet, after all these years, Svelte is a response precisely to that design philosophy: taking us back to accepting that two-way binding is nothing to be scared of. The endless loop of thinking in the JS community is expensive.

And Svelte is a “reinvention” of Knockout, just requiring a precompile. (Not complaining at all, thank goodness we have such choices.)

Well explained, thank you.

When did "data binding" become "reactivity" (why the need to create a whole new lexicon for the same ol' thing)? A lot of this confusion (as per the OP) could have simply been explained away by saying we needed frameworks to bind HTML (visual components) to data. Two-way binding existed in many desktop frameworks before SPAs were even thought of.

Twice the effort wasn't implied as twice the speed. He just meant that going from 50% to 100% effort wasn't translating into double the speed.

Serious question: why is the US trying to (or is already preventing) China from acquiring EUV chip tech? What’s the reason for such an aggressive intervention in a free market?

Thanks for linking this. I've had this fruit before, fond memories of a childhood visit to Mumbai in early 80s. It's known by the Marathi speakers as "targolay". Its taste can be roughly described as a mix between a slimey coconut flesh with a distinctive sweetness found maybe in litchi fruit, but not as intensely sweet. Some rumour that it is intoxicating after a certain quantity - not sure about this. But it's a taste sensation unlike anything I've ever experienced since. Recent visit to Mumbai (2016) in Dec yielded nothing as explained by a dismissive street hawker: "tadgolay won't be found in winter". Much disappointed!

I wish I could write like this. This is music in words. Thank you.

Delphi has legendary ARC not just with its VCL and object hierarchies with TOwner model but also with its wrappers of COM's IUnknown and QueryInterfaces. Yes of course, developers can still make mistakes about sequences and memory management but a well constructed class hierarchy and discipline to manage the freeing of resources immediately after they're no longer needed is the cornerstone of basic Delphi applications.

edit: The objects that are IUnknown linked don't even need to be explicitly freed! There are several clever use cases for this for example changing TCursor from hourglass back to normal when a procedure/function is complete. It just works.