skysight-inc/HackerNews huggingface dataset:
I'm relaying what I understand to be the truth, which obviously could be wrong. The pieces seem to be out there, as near as I (a person who never studied biology) can tell

Example: https://journals.sagepub.com/doi/full/10.1177/10915818211009...
Telomere Length and Arsenic: Improving Animal Models of Toxicity by Choosing Mice With Shorter Telomeres

The abstract discusses telomere length and sensitivity to arsenic toxicity.

If my understanding is wrong, I'd be interested in guidance to correct it. I'm interested in understanding how things really work, and Weinstein's explanations (before the Covid thing hit) made sense of otherwise paradoxical facts.
Also from an organizational point of view: it ceases to be maintained, or the developer disappears, as an independent unit.
It's pretty obvious that antidepressants help people, but I pretty firmly believe they are unnecessary.

Vigorous exercise (morning is better) and time outdoors should be the first thing prescribed to these patients. The former being probably the most important.

I was on and off SSRI's for awhile. Pretty chronically "depressed" through my late teens up to about mid 20's (shocker!). Exercise, talking to someone, and realizing that I am the one who's in control of this has helped me more than any anti-depressant. Similar story with several of my good friends.

The jump to medication in my case was a result of laziness and impatience. Once I got past those two nasty traits, "depression" was a just a bout of sadness that comes when I should feel sad.
Dodo – Synchronize your Twitter timeline to a local database
I don’t know if it’s this difference in structure that makes it so or not, but what I’ve found with USB-C cables (very limited experience on my part compared to lightning cables) to be more flimsy. Somehow it seems to wiggle more or is loose to connect well and the fit isn’t right sometimes. It’s tough to use such a cable when charging something like an Apple TV remote where there’s no display to show charging status.
I'm surprised the last of the elected officials didn't call for foreign intervention, though I'm sure no country wants to go in there and fight the street gangs for control.

I think the US would have the best shot of restoring order (assuming the Hatian govt asked them). I would imagine no gang in Haiti wants to (or is even capable of) a ground war with the US Army, so the "intervention" would be 90% aid and 10% a show of power.

But who knows. I'm Monday Couch Quarterbacking this.
Good points. Agree with slim models and I personally like a service layer.
FBVs are great, CBVs are ok, GCBVs are of the devil
> It may be the sloppiest, crappiest definition every, with dynamic types

Funny you said that since a microservice API is always dynamically typed and its usage cannot be checked by compiler. And the more microservices you use the more dynamically typed the whole project gets overall.

While you can opt into a free for all everything importing everything, all languages do also support creating modules which define APIs for consumer and maintain compile time type checking.
I think I've seen a post from https://texts.com about that they. I don't think they ship you the iPhone though, the host it themselves.
I've been heavily inspired by this styleguide over the years, but I still think it's a bit too complex. A few random thoughts:

- I think "services" is too much of a loaded term. I prefer "actions", and I always use the function-based style.
- I hate the naming of "APIs" in this document. They use the term "API" when they mean "endpoint" or "view".
- "Reuse serializers as little as possible" is the single best piece of advice when using DRF. The inline InputSerializer thing is brilliant.
- Having each each endpoint only handle a single HTTP verb is brilliant.
- URLs and views should be separate from all other business logic (models, actions etc).
- For read endpoints and associated business logic, I'd encourage https://www.django-readers.org/ (disclaimer: I'm the author).
For sure! I've been writing C for about 40 years and didn't know that such innocent identifiers as "total" were reserved.
> That's not what microservices means. You're intentionally equating all services to microservices, which is not the case.

Eventually everyone provides a service to someone, I guess, but there is a clear division between those who serve end users and those who serve the servers. The service that places your food down on the table at the restaurant is not thought of in the same was as those who get to the food to the restaurant. The latter camp is often known as a supplier, but we in tech call them a microservice instead. There is no suggestion that all services are microservices.
But how often do you need to run this? You can run 8xA1000 on LambdaLabs [0] (no affiliation) for $8.80/hr. So you should be able to run the entire data set for less than $350.

[0] https://lambdalabs.com/service/gpu-cloud#pricing
Haha I heard about this at Narita Airport earlier today. The announcement was something like “Flights to the US are delayed because of a system error”.

I was thinking it was a problem at Narita!
Yes. One shows an ongoing vulnerability to foreign actors. The other is a blip that can be fixed with some overtime.
> Just look at the recent attacks on power stations

Quite a lot of those have been linked to domestic extremism, and there's some distinctly partisan problems in even looking at that possibility.
If you plan your architecture carefully and modularize a lot, there is very little that will prevent you from branching out modules of a monolith into microservices when the time comes.

If you produce spaghetti code with tightly coupled components, well, then you are going to have a problem.
No, of course not - by definition, advice is advisory only.

But we can and should default to trusting advice from reputable people over hearsay; credentials inform our assessment of how reputable they are.
> I mentioned the trouble to my USPS person who we'd become familiar with due to the fridge - she asks me for the tracking numbers and said she'll see what she can do.

Unrelated to providing snacks/drinks - I find USPS support to be absolutely stellar. The amount of effort they've gone through for us to track down packages in the past is amazing.

The other day I had a visit from a USPS worker who noted that one of their delivery drivers' scanner had died while performing their duties and a package meant for us had not been scanned. They were simply following up to make sure the package had actually been delivered.
Edge Flags
My Org Mode and Emacs use has been a progression. I was looking for a flexible note-taking program without lock-in. I found Org Mode. I had to learn Emacs to use Org Mode. That is a crazy thought now that I know the implications. The magic is in the simplicity, if all you want is a folding outline.

The folding outline and flexibility were the greatest attractors to Org Mode but it of course did not end there. I originally read, took notes, and taught from my outlines. That was all for home and personal life, but it quickly invaded note-taking at work. Next, I started using it to store data snippets and run code which could present results in the same file. This solved a long-standing annoyance in my statistical keeping workflow. I created shopping lists for home and synced them with my phone. I have contacts stored using properties. On and on.

Now, the magic comes from the amazing flexibility. Start simple and easy. Keep learning.
Yes I am, we're talking about "the Future Dominance of Solar and Wind Energy".

It's a very localised future, won't work for half of the year in half of the world, the half in which most people are living.
What I got from this thread is that Terraform was created for this exact reason - to be able to work in a mysterious state that just happened to be there. Therefore Terraform normalizes existence of unknown unpredictable environments (which is already absolutely normal in the real world, as stuff is never exclusively black or white). But, on the other hand, isn't making stuff extremely predictable part of our job? Doesn't it contradict our goals we strive for when creating software?
If you don't have money for testing I hope you're saving up to afford to fix it twice.
> change the beds, but the sex workers

CTO (& middle management) are the sex workers, the beds are the run of the mill employees.
ES5 had "future reserved words" including class, const, export, import, and let.
I'm picking up a theme about the US health care system - that doctors respond to conditions caused by environment with a drug.

Our lifestyle (activity) is unhealthy, our food is unhealthy, our houses are nice but we don't get out of them, our relationships are unhealthy, even our culture creates anxiety. I speak for myself, but also everyone I know.
I mean, maybe?

But, like, that's after they were making EVs. The roadster was announced in 2006, and started production in 2008 - 15 years ago.

They went from making EVs, which are cars with some software inherently in them, to making different cars with even more software in them. They're a car company first, who have been increasing the amount of software they've written to put in their cars.

The comment I was replying to was suggesting they were a software company first, which then pivoted to making cars. Which is... just... what?!?

Yes, you technically answered my question, so thanks for taking the time and making the effort and whatever, but just not in a way that is actually helpful in the context that I asked it.
While I agree with you, the good part is that each generation is (slightly or significantly) better than the previous one. I remember using static generation in the 90s but the tools we have now are more powerful. Kubernetes is a great piece of software: it is well-designed, easy to work with (at least the managed versions that most companies use; administering the cluster is another thing), it applies a set of simple concepts in a consistent way that makes scaling a breeze. Soin the long run we benefit from the hype, although I can hardly understand folks running k8s for a 3-container setup.
Required workflows and configuration variables to GitHub Actions
I wonder how much US anxiety about foreign election interference is really projection. Most other countries don't do it, and if they do, don't do it extensively (a couple of bot networks any developer could set up) or nearly as well.
link to other articles is NOT evidence
This guide has been around since the early 00's. I read it, start to finish (well, some chapters weren't finished back then :) when I was a teenager and it got me started with electronic circuits.

I ended up becoming an electrical engineer and credit this site significantly for giving me the courage to choose EE in uni.

The guide does an excellent job of building up knowledge without assuming any prior knowledge - just what a curious 15 years needed to get started.

dspguide.com is another great resource and thought me Fourier transform when I barely knew what cos() and sin() were.
Manage like an engineer
As they say, the plural of anecdote is not data, and here we don't even have a plural.
HN is made of people. IT'S PEEEOOOPLLE!!!!
The article fails to demonstrate why Linux is less secure than Windows.
You could get hit by a bus tomorrow. I know people who died of cancer at 34.

Plan for the future, but it may never come. Or we might hit Japanese "stagflation" and returns are flat.

Make smart choices, but don't forget to live.
> And sometimes when you’re driving you’ll pass a car upside down in a ditch and think ‘glad I’m not that guy’.

No, I'd stop and see if I can help.
I have heard that when transistors were new, there were a bunch of people claiming the theory behind them was nonsense because it treated current in p-doped semiconductors as a flow of positive charges (holes.) (These were not physicists - mostly hobbyists, some electricians and maybe a few EEs.)

Once you get to capacitors, inductors, transmission lines and antennas, you are no longer just considering electrons, but also fields (usually via classical approximations to the underlying QED.) In electrolytes, you have both positive and negative ions...
It's more like "disregard them at your own risk"

The issue here is not GCC/Clang. It's developers

You risk having a name collision if you define a strfoom in your code and then later the C committee decides to add that to string.h
Have been hoping for something like this for a long time.

Anyone already using them and able to comment / recommend / criticize?
Huh, that's the video I use to test hardware acceleration too.

Good taste.
> Doing it alone, or with some burnt out druggie friend is not likely to work except by pure accident, and making it worse is just as likely.

This claim, that doing it alone is unlikely to work, or likely to worsen your situation.

> That psychedelics can worsen mental disorder?

That sentence is not the same as the previous claim.
I’m working on a low core project that is already using content addressable source code that is stored in IPFS at https://github.com/yazz/yazz so it can be done
Any word on the technical details of what happened?
Correct, although “Program Files” and “Program Files (x86)” are still primary paths IIRC. (“Documents and Settings” is an alias to “Users” now, but I don’t think they did a similar thing to “Program Files”, although I could be wrong, I don’t have a windows system handy.)
Try this: every page, come up with a question to ask. Even if it's shallow nonsense: "why was his shirt blue?" and write it down.

It doesn't matter if you only end up with a few good ones, the point is to make a habit of asking questions in the first place.

Eventually you'll get bored with the shallow questions and start asking ones that begin to expose what your author is up to, like why write this story in particular?

If you notice an answer to one of your previous questions, write that down too. You're also developing the habit of looking for answers.

I learned this from my wife who is a highschool English teacher. I reread several books after picking up these habits from her and definitely got a lot more out of them the second time.
Am I the only one here who thinks that this movie is bland, very shallow, not really funny and immensely overrated? Maybe because most people watched it as a child and still feel attached to it emotionally somehow?
First Orbital Rocket Launch by ABL Space Systems Fails
> The point is, abstraction is your friend.

Yes, but the point they were making is that you don't have to abstract across a network boundary. A proper module system and package management can divide work and organization without introducing IPC overheads.
That's another example, but not the one I was thinking of. I clearly remember the photo, and yet it seems impossible to find on the internet. Closest thing I could find is this one, but it's Mao instead of Stalin: https://11points.com/wp-content/uploads/2011/11/maofuneral.j...

(From https://11points.com/11-famous-doctored-photos-dictators/)

Perhaps I'm misremembering after all and it was always Mao instead of Stalin.
Head Transplant Surgeon Claims Human Brain Transplants Are Technically Feasible
With all the hate in HN regarding SOA, here’s a great example of adding resilience by separating concerns at a systems level.
Reaching Google scale means you'll be sat on a beach wondering how to spend your multiple billions - scale is someone else's problem, might as well leave something in it for the next person.
I like the method of adding a "deleted: true" flag to records that are ready to be deleted which makes them hidden in the UI, then log or email something like "INFO: 592 records to be deleted". Then, after another couple days or weeks, a really simple filter removes the "deleted" records.
Input Director (win64): use the same mouse and keyboard across multiple laptops

AutoHotKey: create custom hotkeys (ie CTRL+RightArrow to skip to the next Spotify song)

Chromacam: add a custom background in MS Teams videocalls
> KDE connect - basically apple's handoff but open source and for Linux and windows.

AND Macs :)
Desire itself doesn't necessarily justify billions of dollars of OPEX.
Or option 3: let dog sleep in owner's bed.
…Yes?

So many people have very little respect for the effects of the fact that this field is so ridiculously young, including the fact that all of these definitions are incredibly wishy washy.

Being able to take a statement like “an external dependency is a microservice” and not completely discounting the point being made is incredibly valuable.
> Why have a single repo when we can have 200 tiny repos?

you could have a monorepo. you just need to build each service independently, which you can do with bazel/gradle/make or other build tools.
A related odd quirk I ran into once: if you use an Amazon S3 Storage Gateway as an SMB share, the Execute File permission suddenly matters. I don't fully understand why, but Windows won't run an .EXE file off the share without setting that security bit. It caused us quite a bit of pain. Normally it doesn't matter at all.
There is nothing about microservices that require them to be distributed over the network, it's just something that they enable.

Most of the pain points I hear about microservices are to do with versioning and deploying them independently. But again, this is just enhanced flexibility, you don't have to use it.
Latency is additive. You get a small window within which people don’t notice and network calls quickly consume all of it.

Micro services have a few advantages but unless you desperately need them it’s a huge hit to performance, productivity, and reliability unless it’s your only option. Netflix needed it because of their complicated network architecture with servers distributed inside various ISP’s, why do you?
Apple announces full Swift rewrite of the Foundation framework (2022)
Instead, consider using DaisyUI[0] as a design system, which is built above TailwindCSS. As a bonus, it's just styles, so it works with any JavaScript system (or none).

0: https://daisyui.com/
You've never rebooted a computer to get it working again, without immediately knowing why it crashed?
The linux kernel is more siloed than one might expect, a lot of code is architecture specific or in drivers, which facilitates having a wide group of maintainers.
> It was no mind-reading trick, the Catalan numbers are certainly the
most common sequence that people don’t know about

Guilty as charged! I learned about this sequence after looking it up in the OEIS, back when I was still a young student.
Your comment is why everyone should start their engineering experience as a consultant.

Primary thing that I learned being a consultant - you can leave and you don't have to suffer the disdain from the management. You learn to disconnect yourself and be replaceable.

It makes for a less frustrating life.

Sad that it happened to you. Don't invest yourself in someone else's child.
Although true to some extent, this is also a tooling issue. We use OpenAPI and generate clients. Strictly speaking the interoperability layer doesn't know the truth on the other side, but when generated correctly, the developer doesn't need to worry about it.
Sacked Twitter UK staff claim unlawful treatment in ‘sham’ redundancy
Trying to keep it simple (to a degree). First of all, I would say that its OK to still have a monolith and even build a whole product as a monolith and break it down as the need for microservices arises.

My understanding of whether or not you should take a monolith and cut it into pieces is that it depends on what you want to achieve.

Every monolith is specific, or are they?
Without knowing what your product does I bet you have an API, a UI layer or two, some business logic and maybe throw emailing or a payment service. Well, guess what? We all have those!

How to decide.
For myself, I’ve tried to boil it down to 3 questions:

1. Will I need to scale this part of the monolith more (often) than others?
2. Does this part of the monolith handle an entire process on its own from start to finish?
3. Does this part of the monolith require a lot of different code or resources than the other parts?

The questions are simple. They aren't philosophical. They don’t have a hidden meaning. Rather, a series of simple booleans. If something needs to be a microservice it'll most likely hit 3 out of 3 of those.
The corrected numbers still look like the 3%-5% range, which is still probably enough of a reason to switch stove types... if all the other reasons weren't enough already.
I've worked in incident/crisis management for several big, complicated, grown-via-acquisition companies with a tangle of internal systems that were never quite fully integrated.

When TSHTF and we need some expertise from the original builders or operators of a system, it's a lot nicer to have them on another team than at another company. If they still work for us, somebody can make the case to them (or their boss) that borrowing them for a few hours to fix it is in everyone's interest. A lot of times they are in some kind of management position now and they kind of smile and say "Wow, I haven't thought about that system in a long time. Sure, I can take a look." and it's even kind of a fun diversion from whatever budget meeting they were in.

If they work for somebody else, the answer is often "sorry, I'm busy" or just a hangup when you explain who you are and why you are calling.
In Germany if you are liable for an accident the health insurance of the affected people will bill you for all incurring costs. At market rate, not at "health insurance discount" rate. I wouldn't bet that the cost in that case is lower than in the US.
Do whatever feels right for you. There are some people for whom there is a psychological cost to being on medication and medication for them is a step towards being "normal" but for many other people (like myself) medication is a tool I'll continue to use for as long as it feels helpful.

That said, if you do wish to stop taking medication like Lexapro or Zoloft, try to frame it as an experiment in finding the ideal dose for yourself: you hope it'll be 0 but it may not be. Stopping cold turkey is a very bad idea for the obvious side effects you experienced, but you're also missing out on the opportunity to understand whether you can live well without the medication (i.e: your entire quitting Lexapro experience becomes consumed by the horrible side effects, rather than the change in your mental health, which is difficult to measure when you're suffering an inability to stand up right).

I am not a doctor or the parent commentor, just a Zoloft consumer, so take this with a spoonful of salt, but... the standard dose of Zoloft is anywhere from 50mg to 200mg: if you're on 200mg and feel that maybe now is the time to come off Zoloft, then gradually reducing down from 200 to 150 to 100 to 75 to 50 to 25 to 0 will give you many helpful checkpoints to determine whether the medication is required, e.g: if you get down to 100mg from 200mg and start to struggle, you know that 100mg isn't enough, but 200mg is more than you need, so maybe a good new dose for you is 150mg. Repeat every time you feel like quitting. Swap those numbers for whatever Lexapro's dosage range is.
+1 for the two-passes approach. Get lost in it, enjoy that, then again with an eye for craftsmanship.
I don’t think it’s about “documents” versus “components”. It’s about consistency and maintainability.

Keep the local styling for the component local to its place in your repository - absolutely. Give it sensible defaults - for sure. But if you’re using it in something complex where the overall design may evolve it’s a maintainability nightmare to hardcode the styling at the component level and/or designing by classname.

I get why initial development is faster BUT… if you want to make a simple style change on a 100 component site - do you really want to be editing a load of components for every change down the line?