skysight-inc/HackerNews huggingface dataset:
I've struggled with ADHD my whole life. And based on my behavior, you'd think it was obvious. I have the inattentive flavor. When I'm "locked-in" on a task or subject, I can focus on it completely, and be completely inattentive to the rest of the world: the house might be on fire, but I've only got one more piece of code to finish.

Also, if I did manage to interrupt my fugue, it was almost impossible to finish the task: for a fossil collection that was half of my natural science semester grade, I spent a weekend walking a creek and limestone quarry and collected 500 fossils, twice the required, but after going home, I never sorted and labeled them, even though I knew what they were when I collected them. I ended up failing the class because of lack of 1 hour of cataloging.

This continued through the rest of school. I entered university with 29 credits due to testing (I can ace any test), but dropped out after two semesters because projects and self-study just didn't happen.

I got lucky in a job as a troubleshooter. Fly into a factory with a software problem, work 18 hour days to find and fix it, and leave a hero. Great for the career, but I would lose a fortune, because I would wait so long to do expense reports and pay credit cards.

This type of ignoring things that you desperately need to do, in lieu of the current easy to focus things is one of the major diagnostic distinctions between being lazy or unmotivated, and ADHD.

I was formally diagnosed with ADHD at age 42, and prescribed Adderall. And it was like shining a light on the world.

I'm 53 now and still taking Adderall.

There was definitely an Adderall honeymoon, but the lasting effects are also apparent.

I now 100% pay my bills on time, I maintain my car on schedule, I keep the house clean. My credit score went from about 500 (poor) to about 800 (excellent).

I still accrue debt and then have to work to pay it off, and lose money on interest, when had I planned I could have just paid cash.

And I'm still constantly harassed (good naturedly) by my Managers to do expense reports (they know I have an issue and accept it and are willing to work with me).

Probably with the right coaching, methods and strict oversight I could have done all these things without drugs, but I would have hated it.

I think the drugs improve my quality of life, and reduce the stress in my life immeasurably (I could probably measure it by stop using them for a year, but I'm not gonna!)

So I think the test needs to be:

1. Does ignoring the things you need to do make you miserable and feel like a failure?

2. Is your quality of life suffering?

3. Do you lose jobs,Relationships, because of these failures?

4. Does it prevent you from doing the things that would make you happy in life?
First layers of ice melt around -240 deg, below bulk freezing point
In cold climates they never were a problem. Family just waited for a freezing weather, and spent a night at a neighbor house.

For a bonus, leave a hot kettle at the house center, so cockroaches gather near it and can be easier to remove once frozen dead in the morning.
I assume it lets you know where to buy one as well.
Unfortunately, the "wisdom of the tribe" cannot be written down for the laymen.

Most juniors can't look at a design-pattern, and somehow immediately understand why it is good or inappropriate.

Almost all recent grads are similar to the following fellow:

https://en.wikipedia.org/wiki/Eddie_the_Eagle
Can you give an example of a nontrivial application of category theory to business or engineering?
It is also possible that you don’t notice the slow downs?

Teams installed directly from the App Store or Microsoft on any device I own (high end windows/mac/ipad) devices are all terribly slow
got it, I will not build micro services, I will build just regular one.
Are there not already "right to repair" laws that clearly give the user of a legally purchased device that stops functioning because of a defect (even if the defect's origin is that Spotify has defectuous management) the right to repair that device?

I do not see how the right to repair does not mandate that Spotify publish any and all keys and documentation to allow the purchased devices to be repaired.

RIGHT?
I would think the main thing would be no network hardware and ideally no network stack. After that, a minimum of local storage- nothing persistent outside of firmware, and certainly nothing that would provide any type of file system visible to the host computer.
Yeah - I forgot about their opaque pricing tiers.

One other benefit of paying up front is that I think you are less restricted on S3/Cloudfront in what you can host. I think Cloudflare has some restrictions (video files?) to keep costs more sane. Otherwise, you could spin up a YouTube clone extremely cheap.

And just to reiterate, AWS pricing can be absurd.
> Possibly to keep her around.

Hey now. I think you have other issues than your job.

And to be honest, it sounds like you don't like your job because you're gunning for a promotion.
While true, but that’s totally devoid of information. People still need to make decisions. Even people who lack the wisdom to make them well.
I have companies in Blockchain, and in AI, and in Cybersecurity and can say that it is not the same. Blockchain never delivered for most people. For example, blockchain promised banks for the unbanked and the unbanked now use PSPs with mobile phone apps but not crypto. AI is delivering... I wonder why I need to explain this. In the dot com era there were a lot of hype about Internet... few consumers, then... kids don't know what Internet is while using mobile phone apps.
I'm on a OnePlus 11 (upgraded from a OnePlus 6T) and it's great. My only issue is that there's a small selection of cases for it, especially if you want one that's magsafe compatible.
Shutter Encoder – A better HandBrake alternative
To be clear, the resentment and public statement is important and relevant IMHO.

> combined with its lack of usefulness

the language capacity of these systems makes them useful to interact with humans. The purpose of that interaction is a question for legitimate social theorists, policy and law enforcement.

An emotional "gut reaction" of anger and disgust is not misplaced, but it is essentially personal, therefore in the category of drama more than policy.
I feel like at this point in my career I've worked in all four quadrants of the spagehtti/encapsulation plane

^
monolith
|
|
<- spaghetti ----+------ clean ->
|
|
independent services
v

I really feel like it doesn't correlate. I think the real cause of spaghetti monsters is *mismatching* microservices to applications that are actually a single project under the hood, or monoliths to applications that are actually multiple applications under the hood.
Anyone used it yet? Was posted here a while back. I'm interested to hear whether it works and how good it is rather than many "this looks great" comments. Perplexity.ai itself has been pretty poor for me after I got past the honeymoon phase
Is this the first hype cycle you've ever experienced?

AI alone has had many and this is just another one of them. https://en.wikipedia.org/wiki/AI_winter

Just because we have made progress since the last one doesn't mean that _this_ time it will be magically different.

So what makes you think this will be any different?

Keep in mind that each hype cycle was started by a leap in progress, so you can't say this time it is different because we made a big leap in progress.
Putin's ego and desire for the old ways.
China could have lifted their people out of poverty on their own. We didn't need to sell them our manufacturing base to do that.
Honestly I never really understood the hatred that people on HN have for microservices. Everyone acts like "OMG THEY'RE SO COMPLEX!!!!", but a) that's not unique to microservices, b) monoliths aren't somehow immune from this complexity, and c) most big systems end up getting pretty complicated regardless of the model.

Yes, Kubernetes is a pain in the ass, and libraries getting out of sync can be real problem, and distributed systems are inherently difficult, but I think that the benefits of something like event-sourcing with lots of individual, self-contained, "I don't care where this data came from" services outweigh a lot of the complaints. It's not like most of us are reinventing Paxos every day; we're using well-tested off the shelf components like Kafka and Consul and RabbitMQ.

Also, I don't really understand the author's point about individual scaling not being a good thing. It can be very hard to measure things like memory usages for individual components of a huge service; the smaller and more atomic the service is, the easier it is to find out how many resources it actually needs. With a big ol' monolith, it seems like people just go off intuition (AKA self-righteous guessing).

I dunno, even for home servers, I still basically do the microservice model. Maybe I'm weird.
It's not just security, but simple functionality too. Connected devices rely on remote services, by definition. Those services' APIs will change and get deprecated over time. At the very least, you need to keep clients up-to-date to conform to those API changes.
But that's not really what's happening here, is it? Theyre complaining that cloudflare doesn't have a way to revoke certificates after the user specifically asked cloudflare to create one for them - transparently, so they dont have to bother with the keys to this certificate.

I'd wager the reason why this feature doesn't exist is because - by the time someone will want to revoke it, the private key for the certificate will have already been deleted, making revocation impossible.

Honestly, this article has probably been written by someone that doesn't actually know how the certificates are created and revoked, forgot to remove a cname entry on their DNS and now wants to drum up controversy for clicks from ppl that probably shouldn't participate in the discussion either, as they're most likely not as informed as they think they're.

And while I was a sysadmin around 10 yrs ago, which gives me a rudimentary understanding of the lifecycle of these certificates... I wouldn't call myself an expert either .
If you have dev tools open you get blocked also.
This parody sums up the issues with mircoservices very well: https://www.youtube.com/watch?v=y8OnoxKotPQ
Tbh, the best way to do this is likely the hybrid model adopted by, e.g., gitlab rails and Grafana Loki etc.. air usually let's the operator select if they want to run as a monolith, service with multiple components where some are instanced, and full micro service mode.

For small deployments you can just use the monolith and be done with a single "service" while you still have the ability to scale out for large deployments. This gets even better when they allow you to do an in between where one component does A and B while only C is handled by micro services.
I know you are advocating that position. But, I have seen lots of failed projects because of that thinking. They failed to get to customer #1 because they were building something to handle customer #1,000,000.

Unless you are building something that can kill people if it goes wrong just get it out the door and be as disciplined as you can along the way. If it is successful then you have the money to split it up into a SoA when you need it.
The lack of openapi anything is a weakness of the ecosystem, as there's a ton of tooling that's left on the table. Even Python has a bit of a leg up here.

On top of that, the number of bugs that could have been avoided with static types is a bit depressing- the only true way to avoid them entirely is duplicating what you get from a static language, but manually with extra unit tests.

There's plenty of really nice things about Ruby and rails, but you don't actually get features faster without sacrificing something.

The team puts out code at more or less the same pace as I would have expected from teams working with other languages, though I haven't seen so many nil errors since working with a bad Java code base.
> Self-confidence is good. On the other hand, too much self-confidence means disaster. - His holiness the Dalai Lama

I guess it's true for microservices as well.
I lol'd when I got to 'Why would you ever want to allocate more resources to one particular part? It’s not like the other parts will eat up the extra resources. If your system needs more RAM, it needs more RAM. Why would you care about which part needs more RAM?' and stopped reading.
Ancient Mycenaean armor protected users in an 11-hour battle simulation
New rule of biology? Instability may be vital to life
If you don't care about IAM permissions / authorization, just give them all permissions. That's simple, but probably not secure. If you follow "best practice" you'll spend half your time dealing with granular IAM roles, permissions, security groups, and a ton of other stuff.
Files as an interchange format, sure. But as a primary storage system for application structured data they leave a lot to be desired:

- Portability of metadata is lacking (and can be sneakily removed when you least expect it), as other commenters have pointed out.

- Filtering sets of files from out of a (possibly deep) directory hierarchy based on different criteria requires writing a lot of subtly different loops to check metadata. Querying e.g. SQLite handles that part for you once you express what you want, without as much risk of messing up one of those loops.

- Similarly, a schemaful database can prevent your writing incorrectly-shaped (meta)data up front, where filesystems are flexible enough that bad writes may not be noticed until your program tries to read that data back out.

- The accessibility of file-based internal storage systems to human users can sometimes be too high, a la the joke about someone "organizing and renaming things in the win32 folder". Cracking open and messing about with a flat-file all-in-one DB is a higher barrier to screwing around. To be fair, permissions mitigate this risk substantially.

- Intermediate failures with some single-flat-file DBs are much less impactful than with many filesystems. Two parts to this: one is that a more rigid structure in a DB prevents certain invalid writes entirely; the other is transactionality. While plenty of local-flat-file "myapp.library" DBs don't have a good atomicity story underneath (I'm always saddened when I poke at a proprietary data library format and find that it contains a bug-ridden, informally-specified implementation of half of SQLite), and while some file systems make logical atomicity possible to achieve (e.g. via CoW copying data/directories, doing mutations, atomically swapping a source-of-truth link to the new version, and dropping the old), filesystem-as-database systems tend to fail-corrupted often due to unexpected issues (from bugs to "oops, don't have write access on 1/1000 files" to SIGKILL/power loss/drive failure) during data modifications. While I wish more file-based systems were as robust as maildir, I won't hold my breath when SQLite is right there.
I think that shame is likely worse than anger, though parents worldwide use shame as a method for controlling their kids. Hopefully in the future kids are given more tools for how to recognize and deal with shame.
Lizard that Hulks out shows off its superhero genes
> Look at those great Israelis. If they wrote Die Hard, John McClane would just be flattening Nakotomi Plaza to kill the bad guys and free the hostage.

That's quite a broad brush. Yet I'd have to agree the current Israeli government are very hard-line and far right. Still, that's more likely cultural than breeding since there is considerable opposition to their strategy among the populous.
A Declarative System for Optimizing AI Workloads
Why should the people pay you to entertain yourself? Do you pay people to entertain themselves?

You can write up your "highest art and sophistication" and sell it to whoever wants it.
Microservice design is a solution to scaling up people in a large organization.

Regardless what HN people believe, some people like & proficient in a few languages that may not match the existing codebase. Eg. 50% of the team is Go enthusiasts in a Java/Python shop.

Microservices solve that. If your company is tiny, you don’t win much using microservices.
I would love the day when WASM + WASI fulfill their promise and let us write our modules against an interface so you can easily swap the underlying implementation without changing something in your app, this way I can care less if I'm running a microservice or a module, let that decision to the devops/management team.
Perfect minor application would be using this to get ahead with resume scanning/ATS
I think there are different types of anger. It depends on why you feel it, whether it is out of control, and whether it is linked to hatred.

Christianity has both the idea of anger as a deadly sin and the concept of righteous anger.
You can destroy your indoor plumbing this way.
Massively parallel characterization of regulatory elements in developing cortex
The main problem with adopting microservices is the hype and many times the person who defends it doesn't have enough data! "We'll rewrite this into technology X, because this doesn't scale", but sometimes anyone measured it, tested or doesn't have a good knowledge about. Another common pattern is if a module is buggy, you start to listen people screaming that this need to be a microservices. My basic thought is to write modules and when non core features evolve in such a way that the team needs to be splitted, demanding more allocated people, this features needed to move somewhere and at that point the projects will benefit!
The quality of writing in this article is terrible*.

Here's the original source:
https://www.nytimes.com/2024/05/10/world/europe/russia-nucle...

Non-paywalled: https://web.archive.org/web/20240524013552/https://www.nytim...

(*E.g. site is misspelled "sight", author uses tautologies and doesn't always distinguish assumptions from fact, phrases like "way more" are used instead of quantifying, and some inferences just don't flow).
I've worked on quite a few defining products with a friend, business partner, and all-round designer-engineer genius. About a decade ago, we decided to answer, especially in the early stages, that anything that needed our opinion was - "It depends."

There isn't one silver bullet for most problems or situations; it all depends on several factors.
> There are two distinctive events that are basically impossible to hide: The disruption and the payment.

These seem easy to hide. Sure, it incentivizes quick payment, rather than dragging it out for a week. But for 99.9% of employees, this is "the computer network was down, but IT fixed it quickly". For the 0.1% of employees who understand or suspect it was ransomware... thank god corporate got it fixed before 80% of employees were laid off.

The economic losses from thoroughly investigating all widespread network outages (including many not ransomware), seems to outweigh any benefit this could have in (eventually) discouraging ransomware. Just the other day they were talking about how Pixar lost a whole movie but for a copy on some remote worker's machine... in a world where ransomware payments were criminalized, that sounds an awful lot to me as if it might've been one. How many months would they spend combing through log files trying to rule it out? How much does that cost a company like Pixar when they're trying to meet deadlines?

I'm hesitant to point this out, but I've seen shit like this my entire career (thankfully, none of them ransomware). I still have a career, thankfully, which indicates I was only tangentially associated with such incidents. But they're common. There have been big Atlassian, Amazon, and Google incidents as HN headlines within the last 2 years... and whatever explanations they gave, clearly those were just coverups for ransomware payments (or at least people could reasonably suspect that, were it criminalized).

This still seems unenforceable to me in any practical way. But I guess if we're going the totalitarian police state which ruins the economy route, there is some slight wiggle room.
Nuclear weapons are all about posturing. Both sides know the consequences of detonation and do everything in their power to avoid it. Thus posturing.
Separation is a critical part, and that could be modules that form a separate microservice, or split off into it's own "macroservice", the mechanics are the same.

I've seen many cases where there is a service that does like 3 things. 2 of them are low importance and one of them super critical. A low importance one will have a bug, crash, introduce latency regression, etc and take down the critical one.

Time to separate the critical one into it's own deployment to isolate and improve reliability.

The other is on trade-offs, super important that every decision makes has them, just respect that and realize the answer is often "it depends".
Is there a non-Apple way to do this? It seems natural for Google news to step in here, but somehow Google News just keeps finding ways to get worse. I stopped using it when it kept showing me the same fake news shady WordPress blogs hosted out of Brazil attempting to impersonate US news outlets. Super weird phenomenon.
I do wish this kept going and went "and as a last step, we need to add in torque" because pretty much everyone stops at regular force vectors, but torque transfer is so ridiculously important.
We want the monitor, not the tablet. Plus the probably needed software for Windows, macOS ánd Linus to handle the color scheme.
> partly because once you have the skill you find it's surprisingly useful.

A statement I find to be true in general.
Why do you call it "a major Excel fuck up" when the error arose from the language port?
> I’m not sure why people have come to the conclusion that certain emotions must be entirely avoided

I don't think "avoided" is the right term for these teachings, but the emotion itself is generally not fruitful, particularly since it urges you to dwell on it. Injustice should be addressed because it's unjust, not because you're angry at the injustice. What does the anger add to the equation? Maybe motivation? Maybe it's important to explore why the injustice by itself is not sufficiently motivating.
Apple Says These Are the 100 Best Albums. Even If You Think Different
Really appreciate the feedback, thanks will sort out these issues