HN user
"industry malfeasance" is 1984-esque lanuage.
IED airbags, HIV injections, babies without limbs, etc. are industry malfesance.
So the phrase implies:
No acts of corporate greed including profiting by killing people could ever excuse murder.
Assuming you are a coder lets see how that works for you..
Someone comes to you saying they need a website. You say "absolutely ... clearly you need one!". So you build it.
The decision to pay you however comes from some 3rd party who says "denied". Now the customer keeps their site and you don't get paid.
Will you stay in this coding business?
The real solution is a public health system. Which has issues (apply queuing theory, because you will have to wait for the limited resources you are niw denied) overall it is better though since it can in theory be optimized as a whole.
Serve content that is reversed proxied by something that terminates SSL - cloudflare, cloud gateways, Nginx etc, ingress controllers ...
See also https://vale.sh
1. Do this ^^^ keep reminding us!
I think a 3 monthly submission to HN saying "Ask HN: who is looking to meet up" where the comments are used to meet but it is a bit of an ad for your site."
Get a nod from the mod before proceeding though!
Bambino might be OK stock?? Not sure. Only change the OPV if you have a problem to solve. For me it was slightly too fine gets zero extraction and the pressure compacts the puck. Then go a bit coarser and it spews out.
Pre transformers paper emails. Fun to read.
Depends what you are waiting for.
Maybe an in memory cache hit---that you explicitly code---causes a sync resolve to happen, woohoo!
But if it goes to IO and you are waiting for the event loop to schedule you back in you could be in for a shock even if the IO op is tiny. Especially doing it alot.
Only matters probably on a high CPU usage server which hopefully you avoid by scaling up on cpu and using all the cores.
On the other hand... you are being cooperative :)
But tight loop IO is an antipattern ... as is doing a lot---millions---of IO ops from node (per request or job) that you need to worry about this (use a different language for your DB server!).
When he trashed the aldi espresso machine I think he was unfair. The main issues with it are probably the same issues you get on a Breville until you tune the OPV and get a seperate grinder. That said I dont think he is the screwdriver to espresso machine type.
Start a wrapper company.
Transformers is the AI
AirBnB is profit driven. So buy Ikea stuff or similar, paint the walls white, make it feel middle class for the $ but at the same time easy and cheap to maintain.
Oh yeah blendergpt is a bad name unless blender refers to a food processing gadget and AI is controlling that.
:) now I will ha ha. There is value in UI just as there is value in a corner store reselling milk. Not everyone needs to be a cow.
I understand what you are saying.
They should still offboard of course!
They should design their service (as in customer service experience) to decouple cancellation from offboarding.
I cancel. I stop paying. Now do your offboarding process.
If that loses them too much money then ask for that upfront as effectively a retainer.
Now you go in to the relstionship eyes open. You pay 3 months upfront then you pay monthly. When you want to stop you click "unsubscribe" with a few are you sures.
Then you stop paying and they offboard you when they get their shit together. After cancellation and prior to that offboard meeting you are getting some bonus free subscription time.
If the offboarding dude is on paternity leave then treat it as extra free subscription as it is on the company not the customer.
Fighting to unsubscribe and chasing companies up sucks.
I use copilot at work. Why? Corporate IT/compliance. Getting cursor vetted ain't a hill I want to fight for.
QVC!
Ok then ask for that shutdown money in advance. (Or write it off if someone churns).
Or make the recurring payments quarterly or annual.
Very high inflation in the US.
The next administration is dealing with a high inflation environment but their policies are also inflationary adding more fuel to the fire, while the DoGE stuff is pretty unrealistic. You will probably get tax cuts funded by QE.
Erdős found stronger drugs
There needs to be a rule that any recurring revenue service can be cancelled on the bank side. Then to cancel you contact you card provider not the company.
A UK direct debit is like this I think.
If this breaches contract then the service provider needs to get a lawyer.
The finance system should serve people first - and then tax and law follow. Obviously KYC AML excepted.
Such a system might knock 5% off the SP500 but we will live :)
This is r/assholedesign
Big shout out to Plausible Analytics. You click unsubscribe and you are taken to Paddle (I think). One more click and you are done. You get a follow up email which you can reply to or not. You are done.
Anyway. Startups - use Airwallex or similar and create multiple cards. Easy to cancel anything. Then if they wanna chat in April 2025 about it then sure.
Maybe less coffee :)
On the other hand get them to try and debug code. And then you might realize the redicilous amount of unwritten lore that software engineering has. OTOH software engineering has courses but you need to work with people to get good not just read books. Like math.
There was a great documentary TV shown about this story.
I didn't learn big O at high school though.
Yes if I have an ethernet cable in each room, I just extend that to the device. Palaces may be exceptions to that.
It is used so much across the board for FE and BE and CI and config.
Despite the heavy usage I it hasn't been canned and I have never heard anyone at work complain about JSON for any reason.
You could say it is network effects but if it were crap you could replace it much more easily than say moving from Python to Java or whatever. Especially for internal microservice stuff and perhaps front end.
JSON and the tooling is basically solid. It is a non-concern.
ROT13 also scales. Anything that uses minimal compute can be embarrisingly parallelizable.
I think it is more interesting how protobuf is used. I am not experienced in it but roughly it seems like you design a schema for tight packing data. Therefore there is more work in accepting a protobuf and you cant just add arbitrary fields and let old versions of sdks ignore em. I think!
This is good and bad. It is the schema vs schemaless and compile types. vs runtime types.
There is also the efficiency of protobuf vs slightly more verbose JSON.
Fast inverse square root lookalike.