skysight-inc/HackerNews huggingface dataset:
Assuming you're correct, it's painful to consider the amount of effort and money that was wasted simply because investors missed this basic insight.
Could you provide explanation on why GNU is polarizing?
We have to change ourselves, fast, and then the change will come automatically.

Stop traveling everywhere by car/plane, stop buying meat/dairy, stop buying plastic (check your shopping basket), reject consumerism, educate others to do the same, organize, then bring off legislative change.

The wealthy are just the minor obstacle. The masses of people not willing to change their habits may be bigger problem.
The triple digit dB user segment? But obnoxious people deserve products that perform as advertised as much as everyone else.
Presumably due to thermal throttling.
I have been coding professionally for over 25 years, and I hate the industry with a passion. I hate the culture of it, the obsession with couching naked capitalist greed in semi-spiritual terms, the inflation of the trivial into the profound ("we're not just building customer relations PaaS, we're changing the way humans fundamentally interact with the universe around them"), I hate the entitlement ("ugh, why are all these poors and their sleeping bags in my way when I try to e-scooter around the city I moved to six months ago?").

I used to be lead dev and CTO of startups, and now I do part-time IT work for a law firm and spend the rest of my time working on my own projects, which are code and music and writing and some inventing and puttering. It's nerve-wracking because I make jack shit and my wife and I live in poverty in England, where my Yankee paycheck doesn't go very far.

But when I apply for better gigs and get hit with the code quizzes and the "culture fit" nonsense and the bullshit, I just can't, man. I'm 44 years old, I don't care about having a free IPA fridge in the office and SCRUM and sprints and learning an entirely new framework du jour every six weeks and all that shit. I work for money, period. The stuff I really care about (like climate issues), nobody is gonna hire me to do. And I've spent enough time trying to turn my own projects into actual businesses that I know I'd rather gnaw my own arm off than have to put up with another meeting with some VC asshole where they want to gut everything that's interesting about my ideas and shoehorn in NFTs or some other stupid goddamn thing.

You gotta decide whether you value freedom or financial stability. Some people find both, but I think it's rare. Most people just decide what they can live with. Me, I'm still trying to figure it out as the first gray shows up in my beard.

Vaya con Dios, man. I don't have any answers for you, but at least know you're not alone.
The hardest part of this cycle for most teams are steps 2 & 3, getting a consistent development environment and build system across projects just does not happen. The loop is interrupted by the process of reviewing outdated docs, finding the people with the knowledge, and chatting with them to get a development environment running and helping with deploys to various QA/test environments before merging.

At Coherence, we agree that code search and code review, along with automated code intelligence, are a huge step forward. Tools like sourcegraph, graphite, codeapprove are all solving important problems in the cycle. But we believe that the general approach of “building” vs “buying” development infrastructure for these key steps is holding teams back.

Check us out at withcoherence.com if these sound like problems your team faces, too! (Disclosure, I’m a cofounder)
Do you have suggestions for similar software that uses the EU/UK Open Banking APIs? Would really be interested.
Good thing US foreign policy is known for being driven by moral obligations..

Meanwhile we won't even let countries thousands of miles away determine their own path, let alone a bordering nation. We're beyond hypocritical on this.
And yet Chinese citizens of all walks of life have been immigrating to my humble neck of the woods for the past decade (and they're welcome to, everyone I've met is super nice and grateful to be here) while I've heard of 0 people moving from my locale to China, I wonder why that is.
YouTube took over that niche. What used to be a blog post is now a 10 minute video.
I think you're saying the same thing as the post but in a way I worry people will take the wrong way. "TLDR, have quality experiences" is going to read as "don't spend $100 on fancy coffee, spend it on a concert" or some equivalent. In other words, just the difference between buying products and buying "experiences".

But of course that isn't what the original post is about at all. So I might TLDR more like... "Bonding with people over shared experiences is more important than the experience itself."

I've noticed this before with restaurants. I used to really enjoy trying lots of new restaurants, finding the best... until I realized all I ever talked about when eating out was the food. Much better to just go to Applebee's--where the food is clearly no draw--and focus on enjoying time with someone.

I think what the original post is really trying to point out is the various ways we get fixated on optimizing what should really be the background (the coffee, the meal, etc.) instead of the real meaningful experience (the time with significant people).
All the best man. I hope you get the freedom you deserve one day.
Thank you! I thought "I've never heard of Pluto.jl", but then realized I've seen it a lot in that course by Grant Sanderson! At some point TigYog will have interactivity like that :)

Good spot on the table. I'll edit the example to fit, and make math blocks scroll more nicely if they overflow.
Sure, it is one of the works by the French artist Jacques Carelman:

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

To be picky the original title of the artwork is "coffe pot for masochists" as it was part of a (mock) "Catalogue of impossible things"

https://www.arretsurimages.net/articles/carelman-lintrouvabl...
It's not normal though. Most people would never consider shit talking their employer on social media. People with poor decision making skills do.
Assuming you have posted everything to the correct accounts, the Trial Balance should be all they need. (Trial balance is a summary of the total on each account - checking that it sums to 0 is the key advantage of double entry book keeping.) If it doesn't, then perhaps the account structure isn't granular enough?

For the report you use, why don't you send a traditional general ledger and let them pivot it in excel by account (columns) and transaction number (rows)?
It seems like an out of season April fool's joke.
> I would also suspect that wasps stinging humans is still fairly useful and that its disadvantages are basically invisible to the biological processes.

Yeah, I think that's really the heart of my question. What are the disadvantages of stinging humans (and nesting near them) vs the advantages. You may be right that the disadvantages aren't enough to bring significant evolutionary pressure to bear.

My other wasp musing that I've never had answered, is when you destroy a wasp nest, what do the wasps that are "out on patrol" do? Do they form another nest with other stragglers, join another group, or just buzz around until they run out of steam and then die? I would assume it is choice one or three. Choice one seems to make sense if enough of the core group is left, but can just one or two wasps manage to regroup and start over?
> Not all warehouse jobs are equally terrible, as evidenced by the people working at warehouses other than Amazon's at lower wages. Amazon pays above the going rate for warehouse workers because of its reputation w.r.t. worker conditions.

I can easily assume that you haven't worked in a warehouse. It's easy for someone working as a developer to maintain that warehouse jobs aren't all "equally terrible." They mostly are terrible. The majority of warehouse workers would rather be working another job, especially Amazon workers. In many of their labor markets, Amazon is chewing through the available labor supply faster than it can be replenished. By the end of this year and especially by the end of 2024 in many markets Amazon will no longer have fresh workers. I wonder where you prime delivery will be then.

Further, Amazon might pay higher than average wages for the industry, but the high turnover creates an oversupply of warehouse skilled labor and actually depresses wages. They offer slight incentives for staying but then overwork their employees to encourage their resignations to hire newer, minimum starting pay employees.

https://www.bloomberg.com/news/features/2020-12-17/amazon-am...
To be clear, you mean the fragment part of the URL, everything that comes after the pound sign. Not a cryptographic hash.
People romanticising the idea of communism and USSR probably never lived under such a system or base their opinion on propaganda.

That being said, if teachers found you had a talent for engineering and you weren't from a blacklisted family, your life would be completely owned by the state. You would be brainwashed and manipulated to become the engineer the state wants and then as a reward sent off to a prison city living and working with other engineers for the rest of your life. One mistake, wrong comment about the regime and you would end up in the forest with a bullet in your head.
That's why they had some impressive advancements here and there, but in the grand scheme of things USSR was just one big pile of steaming excrement.
I think the underlying reason long term plans don't work in most commercial software development is that accurately estimating software development effort or schedule is the same order of magnitude complexity (CS big O) as implementing that software. If people could efficiently generate accurate estimates (and therefore schedules and plans), they would. It turns out to be hard even in a static world, and impossible in an unpredictable dynamic one. The fundamental issue is that developing software is 'design all the way down', it rarely turns into 'mechanical assembly' - in general, each line of code written is designed. That was one of the insights of the agile movement - the implementation 'stage' required considerable 'design' (or re-design, as the case may be). The difference between the coders and the architects is simply the scope of the abstractions. A successful architecture can reduce the scope of abstractions necessary when implementing specific bits - but it can't eliminate them.
I couldn't agree more. I recently discontinued the process with a company over the leetcode garbage.

Those things test one thing: how many of those puzzles have you memorized the solution to.

I'm also an "old" and suspect you're right about the young-pass-filter.
The $4.4B Bet That Changed Formula 1
I agree with this but would state it differently.

This most often comes up in rewrites (which are usually a mistake) and the problem is that time doesn't stop once you start you rewrite (or, more generally, your long term plan). Features get added to the original. Bug fixes are made. Software entropy happens. These need to somehow be folded into your new thing. Or worse, you halt new development on the old while you write the new.

I've seen pointless rewrites with a 6 month estimate take 3.5 years to deliver, all the while the once-leading old version languished.

More generally a lot of this comes down to risk management. Your long term plan needs:

1. Shorter term milestones. Due to changing circumstances you may end up terminating your long term plan early. You should aim to have something to show for it if that happens. Ironically, having something to show for it makes this outcome less likely;

2. Reversibility: your migration (data, software, etc) needs to be reversible; and

3. Incrementality: you need to be able to gradually roll out your long term plan. It can't be all or nothing.

This is a common pattern in data migrations:

1. Double-write to the old and new systems. Start doing this with a small percentage of users (<=1%). Identify problems, fix them, rinse and repeat. Do nothing with the new data;

2. Increase the rollout to 100% gradually;

3. Have the system be able to read from the old or new system and work fine;

4. Roll out a small number of users to read from the new system. If this goes badly, you just read from the old;

5. Identify and eliminate all the old call sites reading from the old;

6. Once old data traffic gets to zero you can switch it off.

I've seen too many systems where the project plan is basically to shut down development for 18 months while you write the new (often leaving non-critical bugs in place), do a 3 day data migration where the system is down and hope everything works.
20+ years as well and this is spot on. I've also been up and down the ladder including coding, management, director, etc. I eventually decided I liked the technical path much more, and that freedom was a very important value for me, so I took the jump to be independent 10+ years ago.

I originally started with multiple contracts doing various support and project work, these days i'm almost exclusively project work that i'm interested in. This puts me back in full control of my time, and I can (and do) take periods of time off.

You may have to slog it out at the beginning of your career, depending on your luck, but you'll develop "career capital" and can leverage it to do what you enjoy the most.
Mmm, tasty tasty PNGs, for that retro 90's "image is loading" feeling even on a Gigabit connection.
It's a UK -> US transfer. I'm on the US side and I'm not entirely sure which step broke down, but I have had a difficult time getting the US banks to talk to me so this information is helpful.

Thanks!
SEO is much like prioritizing lines of code developed. When you set an arbitrary measure and enforce upon that, you will find that the only thing achieved is that arbitrary measure.
Looks cool and seems valid if you run MacOS. On Linux you could try Emacs picture mode together with artist mode if you want to draw small diagrams for readmes and such. The first one can draw boxes around text, the second mode connects them with arrows. You can then render the resulting pictures to PNG using ditaa.
What specific functionality was this mandatory firmware update meant to address? I do not see that in the article, or your response.

A mandatory update implies a critical fix, it would be helpful to understand what warranted this update in the first place, and how that might relate to SQ, SPL, etc.
"do ... while" maps neatly into Assembly for me. I think it is meant as a bridge between low level thinking and structured programming.
I’m not being derogatory, rather stating how things truly are in the psychopharmacological and neurobehaviorogical senses.

If anything, you’ve now shown that you carry a belief that ”getting high” is inherently a negative prospect. What I wrote carries no such default.
Where was this Terminal Bar in Prague located exactly, if you remember?
Great questions. For me:

1. There's a few weeks every summer where planning is a major focus, but then evaluating and adapting that plan might take up to half a day a week on average throughout the year. Basically: What assumptions underlie the plan, and have those assumptions changed? Maybe we assumed wrong, or maybe facts changed. So I try to keep an eye out for things that require an adjustment in our direction.

2. I have 10 year goals, 3-5 year milestones, and 1 year plans. I'd like to push that to 18 month plans, but at the moment I only go into any detail for 12 months.

3. Once per year in terms of formally planning the subsequent year.

4. I can't think of a time where I completely abandoned a plan (as opposed to adapting it to changing data).

5. Interesting question. I would argue "never", because if there's a truly more profitable option on the table, then the plan needs to adapt and take that into account. But are we talking about short-term or long-term profitable? I very rarely change my plans in response to short-term opportunities, because that's a great way of killing long-term profitability.
This is why I added the caveat. It's a culture question mostly but figuring it out is obvious when you think a bit about the kind of work you're doing. If your work is customer facing, there is a good chance you're selling a product. If its for internal use, there is a good chance you're selling something else and instead you're raw business value add, i.e. clear business benefit, given a budget with expected and clear returns. Left alone to make the magic happen.

Or to put it another way, if you're adding core value to the business proposition or enabling their core business you're probably not going to be seen as a cost center. If you're R&D or innovation focused, probably not a cost center.

For example, working on a Wordpress site for a newspaper, probably cost center unless they're extremely tech focused. NYT comes to mind, but they straddle the line between saas product and not. They're selling the subscription service which puts you in product camp but they also have engineering functions that work on enabling their writers produce content. The content is the thing being sold, not your software so its probably some mixed feels over there.

I should probably extend the original "ecommerce or marketing" to any more traditionally non tech business model that has built itself as a tech company.
For example:

Working on a website for an architecture firm = cost center.

Working on cad plugins for an architecture firm to use internally = probably not.

And again, caveats, even for ecommerce you could be considered a cost center if the business is more like a traditional brick and mortar but they've "started selling online".
The turf and stone houses didn’t have a basement AFAIK. Livestock in the basement was always a later thing I think. As well as basically everyone living and sleeping in the same room. Our house was originally built in 1897 and had only been renovated a bit by the family that owned it when we bought it. I’ve always marvelled at the number of people that lived in it and how cold it must have been before hot water heating became ubiquitous. It was mostly clad in wood from shipping crates and insulated with the packing material and wasps nests. Pretty draughty with a whole large family living in about 40 sqm.
>seems like both a limit of the imagination

Imagination of some future utopia is a dime a dozen. Scenarios that actually work are much less easy to find.

>in likewise post agriculture, large scale society

I don't see any post agriculture "large scale society". I see an even more increased role of agriculture, amidst food and resource wars, and society dropping in numbers (and scattering to smaller dwellings), what with climate change, and all.
I haven't used grocery delivery in ages, but the one time I did because I was on crutches so doing a full grocery shopping was really awkward that was my issue: they didn't make reasonable substitutions, made unreasonable substitutions, or fresh goods didn't look great.
Just to add, Apple has helped a little bit in the form of adding a raw image boot mode that wouldn't be useful internally but helps Asahi
's boot process not break in the future.

https://twitter.com/marcan42/status/1471799568807636994
Not everybody has to compromise on salary but I took a significant pay-cut to be where I am now, and took the decision based on work-life balance, meaningful (non-commercial) work and interesting tech with great training and flexible tech path choices (which ironically give me very sellable skills should I choose to leave).

Best career decision I ever made.

Don't let the cliched-career ladder advice generally offered in life (I don't mean here) blinker or constrain you.
Whatever your describing is not energy, because energy follows the law of conservation. If you can describe this property that allows for perpetual motion then please go ahead. While you are at it, create a prototype and make your billions of dollars.
Strange take -- the whole basis of FP is dangerous and bug-prone?

Unlike the imperative `;`, which sequences commands in an absolutely obvious way, right?
Alright, cool. It's a bit confusing to me to create a dependency from your programming language dependency system to the operating system. But whatever works for you.

Wouldn't it be tedious to repackage libraries in Debian format? Why not use cpan or similar directly? Or a local artifact server already supporting existing package formats.
Writing and communication is an engineering superpower. Writing critically about anything is still a good exercise.
Saw this request for donations in a Slack community I'm in. Did some research and figured to share with the Hacker News community.

Buster Neece: https://github.com/SlvrEagle23

Azuracast: https://github.com/azuracast/azuracast

Personal website: https://www.dashdev.net/

GoFundMe: https://www.gofundme.com/f/30-days-to-find-a-new-life-help-n...
In my opinion, it takes a damn good meeting to beat no meeting at all, and most meetings don’t even approach darn good.

Most meetings I attend are held out of habit more than need.
To be honest, GNU coreutils is not a good alternative to GNU coreutils. :-P
Lego RC submarine detailed construction
Every troll is different. Lest none of them starve, feed them all.
I abandoned my blog. I recommend people make Github open source contributions instead.
IMO this site should not allow key upload, forcing users to use ephemeral keys generated by the website, so they're only ever used for this purpose. Then you don't need to worry about them being public and can do away with the AES encryption. This is a cool site though, nice work!
The downside is, the types of skills and mindsets you have to cultivate to make a lot of money might actually be deleterious to being able to succeed or thrive in other fields.

I think of a lot of people who came up in the management consulting meat grinder and left. Even though they almost all hated the work style and cultures of the firms they left, they often cannot help but replicate the dysfunctional cultural tendencies and management styles that contributed to their burnout in every other place they go. There's a lot you have to unlearn before you can really pivot, but when you've been trained early on that certain inputs are your ticket to praise and promotion it's hard to think any other way.
You can tell what kind of Jew someone is by how they pronounce Adonai. Orthodox say "Ah-Doh-Nye", Conservatives say "Ah-Doh-No", and if they're Reform they say "Eye-Dee-Nye".
> Good/extensible keybindings

Really wondering why this is so neglected in all browsers. I know quite a few users that like to accidentally press CTRL + T when trying to write a capital T after sitting 2h on a site to put in some info.

It is good that browsers grow more sceptical of sites capturing hotkeys, but some sites really benefit from the question if you really want to leave that page. As far as I know this is the only long-term supported solution. Restoring tab might work but not on all sites.

two leading spaces changes text to code formatting
perhaps lines are closer together here.
Yeah I agree, I generally like gnucash but the mobile receipt upload is really critical for me.

I do keep track of incomes, expenses, and transfers. A bit complicated setup initially but not bad
Same level of experience here (lots of gigs up and down the ladder). This is excellent advice.
Just because an anarchist leaning professor wrote some ideologically driven ideas in book form, doesn't mean it's the way things are.

>I won't try to discuss with you

I figured as much
That's funny because Kryon is a religious cult if you look into the website he shared.