I show people coming from object oriented backgrounds this page first in order to correct the perception that TypeScript is best used with that programming paradigm.
> I show people coming from object oriented backgrounds this page first in order to correct the perception that TypeScript is best used with that programming paradigm.
I think you're confusing things. Languages like Java or C# impose an artificial constraint that free functions don't exist and functions can only exist as members of a class. You don't see this constraint in OO languages such as C++.
Also, it's a simplistic assertions to claim that classes have no place in TypeScript or aren't idiomatic. That's just nonsense based on specious reasoning. Classes/objects with function members are still the best way to implement some features. I'm seeing too many people writing absurd typescript code who go through great lengths to avoid a class because they think a class is taboo. They pull out convoluted stunts like passing closures as object members, just to avoid the sin of rolling out a class.
To clarify, I’m not claiming that classes have no place in Typescript. What I’m saying is that many people coming from OOP backgrounds tend to have the mistaken belief that TypeScript is best written with that paradigm. While it can be in some cases, it should not be assumed to be the best way. In fact, the documentation linked above asserts that “free functions over data” are extremely powerful, and “tend to be the preferred model for writing programs in JavaScript.”
CloudNativePG is automation around PostgreSQL, not "batteries included", and not the idea of Kubernetes where pods can die or spawn without impacting the availability. Unfortunately, naming it Cloud Native doesn't transform a monolithic database to an elastic cluster
We’ve recently had a disk failure in the primary and CloudNativePG promoted another to be primary but it wasn’t zero downtime. During transition, several queries failed. So something like pgBouncer together with transactional queries (no prepared statements) is still needed which has performance penalty.
> So something like pgBouncer together with transactional queries
FYI - it's already supported by cloudnativepg [1]
I was playing with this operator recently and I'm truly impressed - it's a piece of art when it comes to postgres automation; alongside with barman [2] it does everything I need and more
I'll add another really positive review here. Sonnet 4.0 had been really struggling to implement an otel monitoring solution using grafana's lgtm stack. Sonnet 4.0 had 4 or 5 different attempts - some of them longer than 10 min - troubleshooting why metrics were supposedly being emitted from the api, but not showing up in Prometheus. Sonnet 4.5 correctly diagnosed and fixed the real issue within about 5 min. Not sure if that's the model being smarter, but I definitely saw the agent using some new approaches and seemingly managing it's context better.
Great write up. We’ve migrated to NextJs App Router where I work. While RSCs introduce a certain level of complexity, we’ve appreciated their benefits. The telemetry on the backend is something we’ve been looking to improve, and there doesn’t seem to be a lot of info out there, so this helps.
This is absolutely my take as well. I see the points that the author brought up as additional contributing factors. However, the leading reason for this “phenomena” is that many companies are brimming with individuals (including managers) that are simply not competent or motivated enough to meet the demands of this profession. In the author’s story, this is probably why X10 decided to leave the company, because they were tired of working with incapable co-workers.
> Greg's use of discriminatory language against a gender-transitioning team member. Despite many promises to address this issue, no meaningful action was taken, except for Greg simply avoiding all communication with the affected individual, effectively creating a hostile work environment. This team member was eventually terminated for alleged under-performance.
High probability this “discriminatory language” is just someone having a hard time switching pronouns. Listing very minor grievances like this give the letter less weight than it otherwise could have.
I think minor grievance gets upgraded to major grievance when it’s a leader of the company no longer engaging with you, effectively turning you into a pariah and unable to do your work leading to termination.
Thanks for sharing what worked for you. I've been wondering if light-moderate drinking might be affecting me, and it seems to be a common thread in what I'm reading about this condition.
From a cost basis, this could possibly be true. But, with that type of attrition, you would probably see a greater percentage of high-performers go because they have good options. Then, you not only have lower producing staff, but it also becomes more difficult to hire top level talent back, because they want to work with other folks like themselves.
Isn't that attrition going to happen anyway? And with mass layoffs, wouldn't top talent, with plenty of options, be wary of a company who is likely to layoff 7% of its staff to please stockholder share pricing? I don't know the answer to top talent retention, but it seems easier and less expensive to turn your existing staff into "top talent" under the tutelage of the existing top talent and implement a hiring freeze with no huge news cycle.
Yup, I’ve been listening to them for a number of years. I appreciate the balance of discussing technical concepts and general banter on developer life.
https://www.typescriptlang.org/docs/handbook/typescript-in-5...
reply