Some form of action should have been taken when they invaded Crimea in 2014 and Georgia 2008. But even in retrospect its hard to say what except shutting down Nordstream and stopping investments. I still find it difficult for Europe to accept going to war with Russia over Crimea, but I guess this timeline is worse. Sanctions has limits, like we see with North Korea and Venezuela. The worst part of this timeline is that we guarantee that the only way a autocrat is safe, is when he has nukes.
As someone who came into a project that uses postgres notify, it was pretty confusing, as your app would connect to other apps db to listen for changes. There also was no documented nor enforced data format, so it was very annoying to deal with in practice.
I did use jextract for java 19+20, but it looked very messy.
Tried it again yesterday on java 22, and the helpers from jextract are waaaay better. I actually completed a MVP implementation this time in a couple of hours. This could perhaps be released as library if I find the effort to wrap it in a meaningful way!
We currently wrap this in java by calling the binary with subprocesses, which has been working great at some latency overhead. The big bonus of this though, is that we can kill the process from java when it misbehaves. Putting this C code inside Java again, means we likely lose that control.
I had a C library I needed to ideally use from Java directly. The new FFI API looks great, but unfortunately the C API relied heavily on macros and void* arguments, making it incredibly difficult to model from Java.
Good point. That is my conclusion as well, its been a while since I worked on deployments, but that is how we set up. Deploying is just a different pipeline on main branch that runs same exact artifact build in production
Its not a hill im dying on, but when you rebase the default branch, its gonna create conflicts for every single other team member. Its annoying to cause so much noise for every team member. Now I run with auto.rebase set, but that is not the default. Ymmv.
We check for ticks every day you have been in the garden or just outside in the woods. Less than 2% of ticks carry Lyme disease, and there is even less chance you actually get a infection, and that the infection becomes a permanent infection. As far as I know, Lyme disease is not that dangerous, but the bacteria can enter stasis and "hide" in different parts of your body, until it suddenly becomes active again, then really blossom if you are weakened for other reasons. The point is just that there is a less than 2% chance of even getting a tick that is a carrier, even less chance you get sick, even less chance it ends up in the dangerous stasis state. One usually does not treat for Lyme, until enough of the symptoms have started showing.
Ticks are incredibly common. People in my area of the country get hundreds of ticks during their life. It's also fairly rare they carry Lyme disease and gets you infected. You definitively should not be given antibiotics without a clear reason.
Amazon does not have a physical whip yet, but they do have a mental whip of tracking every minute of every day you do at work, and ranking you among all the others working there.
I had a very similar issue with a rather expensive LG monitor. The issue was reduced after a firmware update to the monitor, but input auto detection still does not work at all
On the contrary, I think React still is fantastic, and I have been using it since 2015. I think you all have forgotten how terrible it was to get anything done without breaking things in the server side rendered apps of yesteryear. I remember, because I maintained one of those until 2021. Endless cycles of regression testing. Trying to make any of those pages client interactive, within two days you are longing back to something like React. In theory, you could introduce a little React on those pages, but since it is an older server side rendered app, there are no APIs to call, all the features are html pages that return mountains of markup. None of the css is consistent, and even a button is not a single button, its 25 slightly-almost-the-same-button. At least with React there is a good chance those would actually have ended up as the _same_ button component.
In my opinion, the reason React still has staying power is the care with backward compatibility, and the fact that its very focused on being a View Library. State management and routing frameworks come and go, but those all live outside of React the library. React doesn't directly force you to have your CSS a single particular way. It's still mainly concerned about being a javascript library, even as JSX is quite far from JS, it is mostly fairly obvious how it ends up being plain JS.
If you can do this one-way data dump, it sounds like a good idea. The issue starts when you have seven different sheets that is supposed to authoritatively control some other processes. The people writing in the spreadsheet can basically do any kind of mutation to the spreadsheet, so it will break extremely easily.
I have worked with non-lazy engineers too. The amount of convoluted barely working franken stuff they come up with is staggering. No obstacle will stop them from digging the hole deeper.
Nah, they are alright. The real issue is they are so busy working, they never stop to really think about what they are building.
What actually made the most money for society and not shareholders was probably automating payments for student housing and taking it online. The student housing association are separate from the colleges and are non-profit organizations in my country, so this increased their efficiency by quite a bit.
I think one should argue that starting a business is high risk, mediocre reward. Most businesses just kinda trudge along, not leaving with the fairy tale returns of FAANG. Those are unicorns for a reason. Most of the businesses I've worked for, some of the founders are still working there and while they are pretty well off, they either havent sold yet (no big payday) or they made a meager sale netting them a very good pay, but probably averaged less than an engineer in SV on a 10 year horizon.
I have not written a single python script since I learned Go in 2015. But I still prefer Java for work. Dealing with databases is just completely asinine in Go.
You are underestimating how hard just managing pricing in subscription bundles are once you have expanded to multiple countries and currencies. Pro-rating, different billing schedules, trials, testing the new prices, pricing per region, taxes per region, listing your bundles with different currencies and rolling out new prices is suddenly 6 currencies * X regions * Y products * Z billing schedules * L different languages. All of this while you will be adding new subscriptions, merging subscription plans, discontinuing old plans while gracefully rolling customers over to alternative new plans all the while communicating well with the customers. And since you are doing SAAS, pretty much all has to be automated and self service and well tested or you will drown in customer support and customers leaving.