skysight-inc/HackerNews huggingface dataset:
> Macbook air is like $1000. People can afford it.

Bought Macbook Air in 2019 directly from Apple website. Paid extra for miserable 256GB SSD and 16 RAM. Over EUR 1800 in total, its current resell value is EUR 700. Apple customer service doesn't exist in the EU country where I'm located. Now when I even think of buying Apple product I hear subconscious voice "you will be violated financially".
Yeah, elementary OS uses Ubuntu as a base.
I think that's the idea? You don't have to be a "10x engineer" to be useful and productive.
http://www.gooddealgames.com/interviews/int_David%20Thiel.ht... has a better description of Q*Bert's cussing than minute 35 of the video:

MT: You came up with the idea of using the random phonemes of a speech chip to make Q*Bert speak gibberish. How and why did you arrive at the idea and decision?

David Thiel: Out of frustration. Reactor was my first audio task for Gottlieb. Management insisted that I use the Votrax [phoneme generating chip]. For development there wasn't anything more than a list of Votrax phonemes, a dictionary and assembly code. I spend two days trying to get the Votrax to say "10000 Bonus Points". I would try it out on people as they walked through the lab. After hearing it they would say "What are Bogus Points"? Chris Brewer who was providing tech support for me made the offhand remark about feeding the Votrax random phonemes. I programmed a test and I loved the results. Within that week I saw the Q*Bert character hopping around and I told Warren, "Boy, have I got something for you".

MT: Many players still swear that they occasionally hear Q*Bert say naughty things. Can you finally put to rest the rumor that Q*Bert states nothing specific other than "Hello, I'm turned on" when the coin-op is powered up and "Bye-bye" at the end of a game?

DT: Hello and Bye-bye are the only deterministic phonemes fed to the Votrax in Q*Bert, other than the "ahhhhhhhhh" when Q*Bert goes off the pyramid. There was a Q*Bert in the cafeteria which talked during the attract mode. One day I am sure that I heard it say "Radio Shack". For the record: no profanity is programmed into phoneme stream in the Q*Bert sound program.
"Supports better biodiversity" refers to the biodiversity of the other animals and plants that grow around the coffee trees in the ecosystem, not the diversity of the coffee trees themselves.
"Ubuntu is an ancient African word that means I can't configure Debian.*"

I did chuckle, because I am still learning that ( Devuan is in my VM now, but it is something of an uphill battle so far ). I just installed PopOS over my Ubuntu media PC and have not looked back. Yes, it is Ubuntu derivative and it has annoying moments, but it does get a lot right. I keep recommending it to my social circle, when they complain about their Windows.
Where do you get yours from? I looked on Amazon and didn’t really find an option
Just in case it's helpful to anyone, I had a good experience using the CEDR Aviation Adjudication Scheme[1] to challenge Easyjet's refusal to pay up under the EU flight delay compensation scheme [2].

The EU has a mandatory compensation scheme for for passengers where flights are late, cancelled, denying boarding etc. This applies not only to EU citizens and airlines, but to all flights flying from or to the EU.

I had an Easyjet flight that was delayed for hours, then cancelled overnight, requiring a hotel stay etc. After lodging the claim with the airline, they responded that the delay, then cancellation was due to extra ordinary reasons (weather) and as such they weren't responsible.

The CEDR scheme requires a payment of about EUR30, which is not refundable if you lose and the airline needs to be a member of the scheme, but many are.

Easyjet were required to provide evidence of the extraordinary circumstances, and they ended up submitting a long story about the plane being delayed due to severe storms on a prior flight in France, along with the associated documents.

That turned out to be true, but the tail number on the plane that was delayed was a completely difference aircraft, and they were forced to pay the full compensation, which amounted to near EUR1k.

The whole process took several weeks, but it didn't require me to be present in the EU and was done entirely via the CEDR website.

[1] https://www.cedr.com/consumer/aviation/

[2] https://europa.eu/youreurope/citizens/travel/passenger-right...
What's the alternative though? I can sue you at any time for any reason. Well, I guess the alternative is to make it difficult for the average person to use the legal system at all.
>I think my ideal Linux OS is probably Ubuntu/CentOS + something like macOS’s .app bundle file format for distributing end-user applications.

> When running personal Linux, I want things to generally “just work”, which means staying away from the distro package managers on Debian/Redhat derivatives. Given enough “hobby time” I manage to twist my base system’s packages into pretzels and/or break workflow critical software by noodling around. Back in the day I inflicted a lot of pain on myself trying to get newer Apache running on older Debian or similar. Third-party package repos, PPAs, or installing from source are all false prophets that eventually swamp the system in strangeness.

I’ve also had this experience, and would also appreciate a more direct analogue of macOS .app packages. Package manager integration for those .app packages would be cool though — it’d be like brew cask where you’ve got .app packages managed by homebrew, where the worst case scenario is a single app getting botched instead of accidentally breaking sound or something.
I literally only choose Mac because I'm a developer. Why? Because it is physically impossible to build and test iOS apps or run Safari without one. So long as a huge percentage of our users are on iPhone, we are obligated via Apple's relentless vertical integration to buy macs.
So was Malone, the point is to maximize cashflow but minimize profits to avoid taxes and compound the growth.
Powering a house for days is a very broad statement. Does this include things are that electrified such as a central air conditioner and/or heat pump? Electric water heater? Electric clothes dryer? Maybe the last two would be considered a luxury in an emergency situation but I've lost power for 3+ days twice in the past two years during a major snow/ice storm. It's brutal not having a heat source and if you live in a hot climate I'm sure it's equally brutal in the summer.
Mass digitization would seem to have a considerable survivability advantage over paper storage. Fire, Russian artillery, flood etc could readily destroy this information. It's fairly common to have this happen throughout history - we lost the Universal Music Library in a fire a little more than a decade ago.
> So you believe then, that the majority of C++ code written at e.g. Microsoft is not 'modern'?

Maybe some new code is modern - but there is a tremendous legacy code base that can’t possibly be (and Microsoft has released enough open source that you can verify this yourself). Also retrofitting isn’t magic - the boundary between old and new will always cause problems.
A lot of these are strangely specific. For example:

> Doesn't riddicule entire professions within engineering, especially not when in a position of leadership.

> Can have colorful desktop backgrounds.

What?

Most of these come down to "don't be an asshole".

I suppose it's worthwhile to remind people that a large part of engineering is dealing with people, and not being an asshole tends to be a force multiplier (or stated differently being an asshole gets people to actively sabotage your efforts).

It reads so much like the "casual" vs. "hardcore / tryhard" memes you'd find in gaming communities.
This new genre of proposing something completely absurd, asking why everyone in the world isn't doing this absurd thing, and then arguing for the utopia of the absurd. Eating insects, humanure, etc.
Well it has been immortalised in song https://youtu.be/YRlPTbKHIPQ
The MacBook Air has an SOC. It’s literally not possible to socket the ram. It’s all one big package.
Having seen the other side (I sat next to and was friend with some corporate lawyers), customer service may have no power or latitude to deviate, but the legal team has enormous latitude to do so.

They're risk averse. You don't have to threaten a lawyer and you shouldn't). Just letting a lawyer know you exist and have a legitimate problem that could blow up in their face, can often be enough to magically resolve issues. They almost always have a public email address.

Maybe it's better to go after them with the parent posts laws, but sometimes you just want your issue resolved. I can tell you that very few teams will argue once they get an email from the General Counsel.

See also, patio11's post about being a dangerous professional[0]. One of the best pieces of writing on the subject.

[0]: https://www.kalzumeus.com/2017/09/09/identity-theft-credit-r...
My point is that, generally speaking, what pizza is asking for doesn’t practically increase the libraries available (I would expect that JavaScript already has equivalents for the vast majority of the applicable pure Python libraries—and libraries that aren’t pure Python won’t work), and doesn’t solve as much as you’d hope in the way of wheel reinvention and writing less code (in fact, I’d categorise the entire effort as wheel reinvention and writing more code, though I acknowledge the library versus end user distinction in this regard). Your second paragraph reinforces my very point; pizza was saying it’s not so much about lowering a barrier of entry, yet that’s the majority of what you’re wanting it for.
Seems like the guy has a version of 10x engineer = isolated asshole guy who produces unreadable code.

Most super good engineers which I always though of when I com across this term are good precisely because they do the whole list 2x better than normal people, not because they really are 10x faster. Especially the community part.. no one can be alone.
Is pirating movies and music also 'kind of theft' or do we have different standards for when it's our type of work vs. someone else's.
You must have a very different definition of "fine" than me. Only getting OOMkilled several times per hour is OK?
The cheapest MacBook Pro I could find in my country is like 3500 USD and the cheapest Air is like 2000.

I maybe saw like 5 macbooks in 30 years of living here (in a poor EU country, so much richer then the average citizen of the world).
It's actually a perfect example of how people don't understand others' development practices and don't understand the history their own field came from.

This single commit is exactly how the original patch was authored, as you can see in the bug tracker ticket number mentioned in the issue, the original patch is basically the same. The formatting of the commit message has nothing to do with whether it was squashed by any tools; the "format" used in the commit message is the same as the GNU "CHANGELOG" format used in many early GNU projects (which itself I think was just a formalisation of early RCS changelogs), and the CHANGELOG format actually suggests that you individually document what changes you made to each file. This is done so that even if the entire source control system is changed, you can just look at the CHANGELOG to understand when and where things happened. You can go look up "GNU Changelog style" and find more about this.

Not only that, it is very common for patches for projects like Emacs to reach +1,000 LOC deltas. It is actually very common for many projects to have large, individual patches written by experienced contributors that are then reviewed likewise by experienced contributors. It may startle you, but many people actually don't like reading 50 individual 10 line patches at a time, and many people don't care to add lots of commits to their project when the greater overall thrust of the change is more important and can be encapsulated with a single change. [1]

Not only are you wrong, but you should try actually understanding other peoples projects before you start running on about how "unintelligible" they are and calling them gross.

[1] Emacs does not exist in the realm of GitHub; it very much does things "the old way" by using a bug tracker and posting patch files to each other, and one of the implications of that is that large .patch files are better than a litany of small ones. Anyone who has had to pull .patch files off a bug tracker would probably agree with me I guess; but I like bigger patches anyway whether it's GitHub or not.
Are you basing your "every 2-3 years" on something the salesman said?

You are using your backup generator a lot, you need to seek out the maintenance schedule for your model and ensure you are following it!

In my area, Generac [1] and Kohler [2] are what everyone uses for their homes. The maintenance schedules are much higher than every 2-3 years. Good luck :)

[1] https://www.generac.com/service-support/faqs/maintenance-kit...

[2] (Page 60) https://resources.kohler.com/power/kohler/residential/pdf/tp...
I totally agree with your points, but this approach has one big advantage - it's dead simple - define attributes and mapping and you're good to go.
I am not referring to multiple homogeneous consumers processing a queue. That is fine. You have a pool of consumers that can pick up from the queue. That is still considered one entity/actor. The people here are proposing having multiple heterogeneous consumers consume from the queue. That is bad.
for me its an probability thing. monday has an high chance while friday has none, these chances don't add up to 100%, since the not hanging chance is possible.
Every 24 hours of runtime would be insanely wasteful. A quick Google for a Generac manual shows they recommend annually or every 125 hours, whichever comes first. They do recommend an oil change after 30 hours to replace the break-in oil.

The Onan/Cummins LP generator in my RV requires an oil change every 150 hours or annually, whichever comes first with the first oil change after 50 hours.
It depends on how the envelopes are prepared. If the two envelopes have x and 2x in them and one is randomly handed to you, there's a symmetry between them that tells you there is no benefit in switching.

However, suppose x is placed in an envelope and handed to you. Then a fair coin is flipped. If it comes up heads, 2x is placed in another envelope and if it comes up tail, x/2 is placed in that envelope. Then you should switch.

It's a subtle difference in how the envelopes are prepared, but it makes all the difference.
Under normal circumstances it doesn't affect much. Increase the memory on your configuration and move on.

However, when the supply chain is crunched (as it is now), Apple's build-to-order MacBook Pros take two months to deliver. This means that the only available models to purchase immediately from retailers are the low end models that don't cut it.

I doubt it will ever change though. There is more profit in keeping the price low for customers that don't know any better rather than accommodating business customers that need something workable immediately.
I would say that travelling on a super low budget (or no budget at all) can be a transforming experience. It forces you to interact with locals to obtain any kind of food and shelters, and to live their lifestyle (because you can't afford anything more comfortable). On the other hand, I don't see much value in travelling where every discomfort can be removed by just opening up your wallet. It's nice but no essentially no different than going to the mall and movies in your town.
Thanks for the time you dedicated to check it out and reply to me here, it really makes me happy.

The responsive version is buggy indeed, sorry for that. This will be my focus on the coming days and should be improved very soon. I was caught in a loop where

Thanks for the suggestions, already added them to the to-do list. If I may, a follow-up: what have you thought about the aesthetic chosen?

I explain: when I started my career, many years ago, I started as an UI designer. Although I eventually pursued the programming path, I always felt sad to have abandoned doing designs. This project also have this deeper meaning to me – I tried to improvise on its design and do something I just felt like doing.

I'm wondering if my intuitions are still there to make something minimally appealing. :)
This doesn't look like a win to me. When insurance companies (and equivalent products) pay a claim through legal action, even if it were 100% of the claim, they have won. That was all they were ever obliged to do and they got to put it through a filter first, where they benefit from filtering even a small fraction of claims (and in reality it's a large fraction). Sound legal principles demand double or treble damages for every litigated insurance claim to prevent this hazard.
1. Take time off, you need it, try to do it without regrets/feeling bad that you are wasting time. Sometimes we go beyond that point of exhaustion and kid that we are productive.

2. Exhaustion leads to bugs: This is a vicious cycle. Late hour bugfix leads to next bug and so on. Both short term and long term exhaustion.

3. I felt like you when I went for grad school. As an EE Major, I could hack my code to work, find resources to get it to work etc. At that time, my interest was doing cool animations with flash (yeah, long time ago, levitated.net anyone)

4. I got the high of solving interesting problems but was always wondering how good coders do it, do they hack it all the way too. (hack here as in, band-aided, spaghetti code with no theoretical underpinnings, using arrays when I should hash-tables etc).

5. What I learned is that, good coders, imho, they hack the last bits too (caveats apply) but often have good theoretical foundation. DS/Data representation for example is the fabric of code you write (you are making a choice even if you didn't explicitly decide). I knew it sort of then but didn't know it my bone like I do today and apply it like I do today. I had an amazing teacher who made big difference (Thanks to Brian Dean, some of you IOI folks might know him).

6. Leetcode is great once you have some bit of theory else you are still hacking your code to work. Abstractions escape you. So now you have to learn each problem separately whereas someone who knows the abstraction compress the knowledge into those few abstractions and its minor variations.

7. Find a good mentor, someone who knows what the heck they are doing. This can help.

Disclaimer: We run a bootcamp for students who want to understand how to write good code from first principles (autoinfer.com).
Joe Biden: My Plan for Fighting Inflation
LOTS of good advice here.

My only addition would be to further specialize in something you don't hate working in. Becoming a subject-matter expert will afford you the opportunity to take time off or just work whenever you feel like working.
I also only put years on my resume. 15 years into my career and I have never once been asked to elaborate on the exact timeline of my resume. I've taken breaks, some voluntarily and some not so much.

If I ever take a multi-year break I'll just take occasional freelance clients and list it as "consulting".
The difference between this and the Monte Hall problem is there's no new information revealed or pool reduction here.
Upload videos of you eating vegetables 3 times a day for a week. I'd also like to see a walk-through of your pantry to make sure there is no sugary soda there.
>Nobody is going to be willing to not only put cycles on their battery but risk being left with a half-charged vehicle

You underestimate the optimistic zeal of LARPers, who will be smug about just having the possibility.
This is probably what they're referring to: https://www.harborfreight.com/9000-watt-gas-powered-portable...

It's Harbor Freight, so you get to roll the dice on whether or not it'll work when you need it to. It's also loud (like noise complaint from your neighbors loud).
So far as "fear of reprisal" goes I don't know why people still think the state is the only bad actor. Maybe you never got bullied growing up or you don't pay attention to the news and see things like

https://www.cnn.com/2022/05/30/us/uvalde-texas-elementary-sc...

https://en.wikipedia.org/wiki/Vardan_Kushnir

https://en.wikipedia.org/wiki/Don_Bolles

You have about 0% security with pseudonymous transactions. Anyone who wants to extort you, kill you, vandalize your property, etc. can do so. Contrast that to regulated bank transactions that are available with a warrant to a government that has some accountability as contrasted to: rouge states that run intelligence services like North Korea, Russia, Iran, Israel, organized crime gangs like the Italian Mafia, Yakuza, Triad, Scientology, Jeremy Epstein's organization, etc.
That's a good point. It really depends on usage, though it's not unfair to just use the average when writing an article. And by that standard, 'a few days' is probably fair.

During the winter, that kind of battery capacity could power us for a couple weeks. Everything other than the furnace blower is natural gas. During the summer, ... well, fortunately we don't need air conditioning here to survive (one-off 117F events notwithstanding).
Of COURSE insurance has a negative expectation (not $0) in absolute terms - but this doesn't make it a bad idea! We don't live on expected value - we live on actual, highly variable outcomes. I'm happy to lose expected value to offset catastrophic losses for small-probability events, like early death, car accidents and fires.

I will continue happily paying my insurance premiums, and ardently hope that I never get any of that money back.

Of course, there may be specific types of insurance/warrantee programs that are a bad idea for one reason or another, but that's not an argument against insurance in general.
Architect of Thought
It’s a common misperception that a 10x engineer is 10x the average engineer. The original quote said that the best engineers are 10x the worst engineers which is easily true. 10x the average engineer is only sustainable for a limited time before either burnout, or outside life intervenes.

The truly best engineers have the experience to develop intuition around what core not to write, and have 10x impact but are not 10x better coders.
Coffee associated with lower mortality risk
Right, but that's my point. If I were to launch a new product and I had the choice between ingredient A and ingredient B, and ingredient A meant I could get an easy kosher certificate, why not choose A?
The French respect their language. Furthermore, the French feel that their language is sufficient to express all that needs to be expressed.

I will admit that when I hear people using English terms and even phrases in my language, I fear that is another nail in killing the language. I could totally see proposals to discard the language after a significant portion of ideas could no longer be expressed in the language.
It is. It's the first M1 model still with the touchbar and the old display. So far it hasn't been discontinued, but de-facto replaced by the current 14 inch model.
The 8GB in the newest model is way better than in model from 2015. Way higher throughput matters a lot with M1. Also, very fast NVMe means that swapping disk is way less painful than on older laptops, especially those with HDDs.

Still, 8GB is simply not enough for anything close to "pro" needs.
Did you really miss RedHat killing CentOS 8? The support was supposed to last to 2029 if I remember correctly. It was cut to end of 2021. Stream is a different product for a different audience.

And CoreOS from the company CoreOS is actually dead. Fedora CoreOS is built from scratch. It's very similar to Fedora IoT (runs rpm-ostree, podman, ignition), but it downstreams to RHCOS, which you only get with OpenShift. Neither resemble CoreOS. The biggest fork of real CoreOS is Flatcar Linux.

Also, Leap minor upgrades do not come with upstream version bumps, so in a sense, yes, the release cycle of Leap and SLES is 3-4 years. RHEL 8 and RHEL 8.1 are not different releases either.