skysight-inc/HackerNews huggingface dataset:
Fellow data engineer here. I started mine because I felt I was making the same arguments again and again at work, often ineffectively.

I found that by taking time to collect my thoughts and write them down made them clearer and more persuasive. An unexpected side effects it that I started to have greater influence beyond my immediate team, with random colleagues emailing me about posts. Though it hasn't directly found me a job it has resulted in people asking me to apply to positions.

Later I added more technical content and tutorials about the problems I was immediately working on, partly just as a way of documenting things I'd found out and helping myself to understand them.

Overall I think it's been extremely valuable in terms of self development and my career (but this is heavily influenced by the fact I enjoy doing it)

I would say don't think too much about your audience to begin with and just write about things you're personally interested in. I've literally never had negative feedback/trolling (probably because there's no comment section). I have virtually met a number of people interested in similar topics who've contacted me after reading the blog.

Fwiw, by blog is https://www.robinlinacre.com/
Link leads to a download
> I am afraid of sharing though and getting negative feedback.

Then don't. Don't add a comment section. Unless you have built an extensive community around your site, having open comments just invites drive-by criticism or generally people demanding, rather than stopping by to say nice things.

What I am thinking to add on my personal website, though, is a "send a reply" box at the end, where one can directly write to me, and I can respond via email. There is no promise of being published, which discourages spammers and drive-by snark, requires a valid email and promotes 1-on-1 communication which is much healthier and personal than the average Web 2.0 public comment widget.

---

But, in general, do not write for an audience. Write for yourself. Write to get better at writing. Write because someone might find it useful, without having any engagement target. In that frame of mind, who cares if one doesn't like your content? The worst that'll happen is one will scroll by. They'll click the link, skim, and move onto the next shiny thing. We mindlessly and compulsively scroll down our social media apps until something piques our interest. This is the default mode of navigating the internet for most of us. If one stops by, spends time to comment on your post, it means they cared enough to.
Red Hat backing SystemD was hardly an advantage beyond the fact that it had financial muscle.

So for example, Red Hat backing meant that Canonical would have to be pulled in kicking and screaming to use SystemD and Ubuntu is one of, if not the most influential distro in the Linux world.

Ubuntu created and used upstart until it basically lost out to SystemD and had to move over.
The USSR provided the competition that resulted in funding these kinds of projects; does innovation require a multipolar world? (Compare Renaissance Europe and China?)
I like how you can handle lots of languages in a very systematic way, that is cool.

One thing I like about pyodide is that it supports lots of packages like numpy. How would you support packages like this with a WASI approach?
Interesting way to avoid the question. I guess we'll just have to disagree :)
Just write for yourself. Turn off comments, ignore “feedback”. Keep reading books, articles, blogs that you like, and eventually you’ll develop a writing style. If English is a second language, get help from a proofreader. Happy to proofread anything you send my way if you need one.

I would avoid AI tools like Grammarly. They have a very prescriptive style that they think is the single correct way to write. You end up sounding like everyone else writing like that.

You will always have at least one reader of your work - yourself.
I can't find the bibliographic details for the 2013 edition, but the 1992 one was published by Addison-Wesley, so it's quite possible that anyone participating in this project to "liberate" the text will get a cease-and-desist from Pearson Plc's legal department/anti-piracy people.

Caveat: the 2013 edition doesn't seem to be available via Amazon so may well be formally out of print. In which case, Wirth's heirs can issue a rights reversion letter to Addison-Wesley and claw the rights back, then relicense the text libre. Or they may already have other plans for re-issuing the book.

Either way, it'd be polite to ask first before "liberating".
They are when correlated with a timestamp and logs from an ISP
80% of cobalt mines in Congo are owned and operated by the Chinese battery companies, such as CATL, the largest producer of LFP.
Unique perspectives are not made by sex or skin color, but by life experiences.

Two Americans today, whatever their sex and race, have virtually everything in common with each other compared to anybody from 1800, let alone 800. The extreme, excessive focus on race and sex in contemporary writing is exactly what makes it boring and irrelevant. This comment is a great example - you've been taught by contemporary writing that such a tendency existed, when it in fact excludes the objective reality of the tons of works that could not have been said to be "written" or "about" such people even by modern framing, but also the fact that "well-off white man" is a completely meaningless and inapplicable phrase if you go back more than a couple centuries.

The sort of work you're describing is the stuff we're taught to acculturate us to the world we already live in. There's no point browbeating me with even more material that I am already steeped in.
Indeed, why use Dropbox, when FTP existed for decades?
You know what I find amusing about the C compiler? It's about the same size as the kernel in terms of LOC. I don't know why, but that amuses me.

This whole project just really makes me happy. I think it's because it's obviously a labor of love, it's very UNIX-y, yet at the same time, utterly comprehensible. I think this is a nicer environment for just general screwing around than a PDP-11 emulator running real V6. The core looks to be all here, without having to bear the weight of complexity implied by a real implementation.

10/10 will clone and study.
I'm talking about a local caching resolver, not a server running somewhere else on the network. dnsmasq doesn't ship with a DHCP client
I got here from brutalist report. I love being able to quickly scan the first dozen submissions from HN as well as other news sites all at the same time.
The library was the inspiration for the Jedi library in Star Wars movies. Inspiration as in basically a remake of the library.

It's absolutely breathtaking in person
>The FBI was able to identify Coker and gather information about his actions using only location data from his phone and image-recognition technologies. According to the charging document, agents did not even interview him before filing a criminal complaint.
While I agree tooling could be better, while in grad school I found that a lot of academics / grad students don't know that any of the tooling even exists and never bothered to learn if and such tooling existed that could improve their life. Ditto with updating their language runtimes. It really seemed like they viewed code as a necessary evil they had to do to achieve their research goal.
matmuls aren't a syscall though.

Little fun fact: Numpy doesn't even come with an efficient, blocked matmul procedure. It has to be linked against a BLAS implement to really provide any decent performance. This also explains why Numpy performance can vary from distribution to distribution. Anaconda ships it with a different BLAS than Pypi.
Live map of Tokyo trains: https://minitokyo3d.com/
Better link here:

https://www.vice.com/en/article/m7b4nq/fired-comedian-ordere...
It's not so bad. Used to be a jumpmaster in the 82nd Airborne, where part of the job was to stick your head out of the side of the open door of a C141 while in flight to check for issues, towed jumpers, etc. It's loud, but survivable. You can hear yelling over it. Of course we were going much slower...
TBH, we still have the BSDs. Although, in the case of freedesktop, they are quiet dead.
When there's no need for a central server(s) to establish connection.
"long covid" == "Vaxxed and boosted". Prove me wrong.
No job interviews for me. I never intended for it to lead to that, so I am happy with that, but if you want it to, be aware that you need to self-censor. That said, if you do, a blog can be a good in for interviews.

Yes, I got negative feedback, and still do, and I pushed through. However, that is because my blog was not just a tech blog. Keep it tech only, and the problem will be minimized, even if it doesn't go away completely. And as for the rest, just realize that those who are negative are louder than those who like your stuff.

Should you do it? Absolutely. It will make you stand out against others.
Except these automount tools provided exactly the same functionality that is currently provided by systemd. And did it better
Purported Advantages of Monolithic Repositories (Monorepos)
> A good example is validation.

It is a good example to bring up because front end validation is not business logic, it is presentation logic. For some simple use cases that might not be obvious to many people but let's just consider a sign up form accepting an email address and a password. There definitely validations you want to perform in both places - the password needs to be 10 characters and have at least 3 of numbers, uppercase, lowercase, and special characters. Those exact password validations will be the same in both the UI and API.
But let's consider the email. The business rule here is that only deliverable emails that are openable by the person signing up should be accepted for new users. You cant validate that on the front end. The best you can do is check for an @ symbol or run a more complicated regex (whales be there) before passing it off to the backend to actually send an email, encode signup details into a special link, and do all the work necessary to satisfy the business rule.

Its trivial to further drive that point home that UI validations are not business logic even when the same validation appears as part of business logic. You do some minimal checks to save the user time on the UI, but those shouldn't even be looked at as validations. They should be thought of as affordable for the user to prevent wasting their time with trivial, predictable errors.
My question is how do you go from posting to interviews/offers? I've been blogging for years and I do it for my own sake, but I wouldn't mind these fringe benefits.
a barrel of oil is equivalent to around twenty-five thousand man hours of work. sacrificing that would result in a colossal hit to quality of life. and ironically, the additional people needed to mitigate that might actually result in more ecological impact, to say nothing of broadening a global underclass of widget producers

we can and should use our limited hydrocarbons to bootstrap our way to higher-potential energy sources. but "using less" is a misguided assumption
I always recommend using the most secure password manager there is... your own memory and brain power ;)

Create a system or pattern based on url or brand and mentally hash it into a password.
You could do scanning and/or broadcasting.
I downvote almost all humor here, unlike Reddit where I go out of my way to upvote even unfunny but worthwhile attempts.

HN is a high-effort place, relatively speaking. The trick with humor in a comments section is that it’s almost always low effort.

> lol I misread the post title as being about boobs

> lol I bet his mouth wasn’t the only place they found one

> lol Russia

> lol North Korea

Comments like this are pervasive on Reddit. I’m glad on HN they’re not.

When a joke on HN is clever or unique, then I upvote. This happens maybe 3 times a year.
Even with your disclaimer, Tiobe is useless, even as a vague indicator of anything. It ranks Prolog as having higher market share than Typescript for christ's sake, stop poisoning your brain with that snakeoil shop.
He's got a bunch of stuff on youtube.

https://www.youtube.com/watch?v=gRUElVhT97Q
https://www.youtube.com/@jad_s_comedy

He's pretty funny. And as far as standup goes it's honestly pretty tame.
>Ultimately I’d say the core issue here is that research is complex and those environments are often resource strapped relative to other environments. As such this idea of “getting shit done” takes priority over everything.

That conforms to my experience
http://tracker.geops.ch/ shows way more connections such as busses, trains or international traffic.
Count me as another who would be interested in this youtube/blog post. I'm currently at the beginning of a similar project.
it's basically how enshittification is happening.
Nice use of web components!
In other words, programmers tend to over-engineer, and non-programmers tend to under-engineer. Despite all the arguments here about who’s making the biggest messes, that part is not surprising at all.

Both are real problems. Over-abstraction and over-engineering can be very expensive up front and along the way, and we do a lot of it, right? Under-engineering is cheaper up front but can cause emergencies or cost a lot later. Just-right engineering is really hard to do and rarely ever happens because we never know in advance exactly what our requirements and data really are.

The big question I have about scientific environments is why there isn’t more pair-programming between a scientist and a programmer? Wouldn’t having both types of expertise vetting every line of code be better than having each person over/under separately? Ultimately software is written by teams, and it’s not fair to point fingers at individuals for doing the wrong amount of engineering, it’s up to the entire team to have a process that catches the wrong abstraction level before it goes too far.
I started blogging this year, and so far, it's been a lot of fun! Most of what I write is a mix of personal projects and opinions. I recommend keeping a target audience in mind, ideally someone you actually know - in my case, I write for my friends from undergrad. I can't guarantee that you'll get job offers from your blog, but I've certainly received some nice emails. I got an offer because of a project I did before I started a blog, though.

I've gotten a little negative feedback, but that's by far in the minority. Most people on the internet are very nice and I've gotten lots of friendly emails from people I've never met. Definitely give it a try - I would suggest doing a github.io page to get started, but you can of course go the self-hosted route if you're into that sort of thing.
nitpick, BRICS now that south africa joined. which is frankly baffling given that the other members were only too happy to continue doing business with the apartheid regime, excepting only india: https://en.m.wikipedia.org/wiki/File:International_sanctions...
This reads like a burnout.

It's OK if mysticism helps him, but perhaps the working conditions are unhealthy even for successful scientists.
Those small government folks want big government rules against “decisions” that they explicitly refuse to respect
> You can't just type `ls /etc/init.d` to get a rough overview of what services exist

You never really got that on svinit systems either, since there was still inetd, and cron had at least three different places you had to look as well. With systemd, you have systemctl list-units and you're looking at everything -- to say nothing of being able to filter by status. rc files make you implement service control yourself from scratch every time (save for a small set of primitive utility functions), and every one is a snowflake.
Of course they are, it's part of the European continent. This is like saying citizens of Lichtenstein or Switzerland or Norway aren't Europeans.
Good points on using proper CSV tooling 100%; so that’s why the disclaimer “more often than not”

BTW I just realized that I was omitting the field separator ‘-F,’ actually.

For those pesky nested commas from top off simplistic text hat still I’d go back to sed for fun and potential profit:

sed 's/","/"\t"/g; s/^"/"\t/; s/"$//; s/,,/, ,/g' | column -t

Not elegant nor hands-off and might be missing something else; def needs the right data / volume and fiddling as we know ymmv; can get unwieldy quickly etc etc

TLDR; use column -t when applicable
ah yes, I am decent Vim user but hadn't thought about it in that context. Thanks for the context!
Famously subject to the $12 attack - buy a monkey wrench from the hardware store, and hit you with it until you tell me your password. Not as secure as many other approaches?
it's exclusively because engineers are more expensive than grad students
Sleiman...argued in arbitration his stand-up routines stem from his experiences as an Arab American raised in a Muslim family...

Probably a wise strategy - and a useful background to have when fighting the sort of people who sack others for jokes on contentious subjects.
Does seem to have some latency, as I just saw two trains crossing on

https://bouw.live/puls-amsterdam/

with no corresponding trains on the map.
It would be great if someone could make a torrent of all of these in one go.
Or you can write an NPR Best Book of the Year bestseller in your spare time, and still get fired from Apple because your fictional writing "makes people feel unsafe". Sadly no reinstating there.
Maybe the fact that you need the physical, manufactured goods to live a comfortable life unlike 'financial services', that won't cloth you, won't transport you and definitively won't feed you.
Glad that's the case. I do find that in certain areas, with certain electricity costs, solar can be worth it.

But I also find that a lot of people are miscalculating their break-even point.

If I invest $X, the default return is 5% forever for infinity years with 0 maintenance.

So if invest $X in solar, and return 5% for 30 years and then the system breaks, then I lost money compared bonds/whatever.

(Again, most of solar investment drives technology improvements and is a great way to help the world become more sustainable)
> Musk is not, yet, president

will never be.
> Then he indicates that macos’s launchd is an improvement, despite it being one of the most painful parts of advanced macos administration.

This seems like a rather hot take. Most of the Mac admins I knew when I worked in the field were quite happy to have a single standard way to solve that class of problems.
You can't be receptive while being defensive
Might I interest you in https://currenttimeutc.com/. This creates shareable dashboards with different cities, timezones, and airports.
Is there an open source thing similar to this that has a windows gui?
Git has a few (configurable) diff algorithms; 'histogram' is more readable (IMO, but that's the design goal - or rather is of 'patience' which it extends/speeds up) than the default Myers algorithm, but it does still suffer from the issue you describe IME.

Paper comparing Myers and histogram: https://link.springer.com/article/10.1007/s10664-019-09772-z

Naïvely it seems like it should be not that hard to fix (be less greedy?) or even that it's an example of a case where the algorithm should be less smart: it's such a common case, hardcode paren chars for some kind of exception or second pass. But that is a naïve take, I've never looked at the algorithm or source code at all.
> Lack of familiarity with common data structures and algorithms

This part I 100% agree with. I adapt a lot of scientific code as my day-to-day and most of the issues in them tend to be making things 100x slower than they need to be and then even implementing insane approximations to "fix" the speed issue instead of actually fixing it

>"Big ball of mud" design

Funny enough this was explicitly how my PI at my current job wants to implement software. In his opinion the biggest roadblock in scientific software is actually convincing scientists to use the software. And what scientists want is a big ball of mud which they can iterate on easily and basically requires no installation. In his opinion a giant Python file with a requirement.txt file and a Python version is all you need. I find the attitude interesting. For the record he is a software engineer turned scientist, not the other way around, but our mutual hatred for Conda makes me wonder if he is onto something ...

>I think the appearance of "I'm just getting shit done" is often a superficial one, because it doesn't factor in the real costs: other scientists and engineers can't use their solutions because they're not designed in a way that makes them work in any other setting than the narrow one they were solving for.

For the record my experience is the exact opposite. The crazy trash software probably written in Python that is produced by scientists are often the ones more easily iterated on and used by other scientists. The software scientists and researchers can't use are the over-engineered stuff written in a language they don't know (e.g. Scala or Rust) that requires them to install a hundred things before they are able to use it.
Well in their defense a primer for fantastical stories makes for a more interesting animated movie than a historical examination of scribal practices.
sure, nice dream. Dream on! but there are some practical aspects that you totally ignore in this PollyAnna summary. Categorical listing of "problems" can go on for pages, and will be incomplete. Perhaps a few to start it off?

* discernment requires effort.. someone has to make an effort, and do it effectively. In the city, time is money. Few to none in the "competitive retail markets" will seize the day to waste, making no money in discernment. Hollywood knows this for decades, and has many many ways to deal.

"She knew a good movie from a bad one, and knew how to sell both" was an epitaph for a crooked Hollywood agent, who was murdered by mobsters in her 50s not long ago...

* Publication incentives.. as noted many times here today, those who pay to advertise, do not have the incentives of discernment you are so confident in.

* Security by Obscurity -- in a blizzard of new publications with new incentive and cost structure, you will apparently find the perfect snowflakes to promote to other snowflake lovers? maybe.. for a minute.. but look! more snow

source: years in the book industry in a big University town before the Internet
It's not how long you live, but what you do in that time. Both what you get out of it for yourself, and how your life affects others.

Some people die in their 20s, but achieved more in that short life than others who live to be 100 (although I'll avoid to judge on how important any achievements are).

Also: the article mentions exercise, and comes up with a modest 'ROI'. But it fails to mention that exercise may not only increase lifespan, but also improve health / general well-being during the years it's done. So the return in extra life may be modest, but the life-while-exercising tend to be fitter / healthier / happier years.

And of course exercise carries some risk itself - especially if overdone. Risk vs. reward, with risks very dependent on type of exercise.
But to make that work out they first had to fire him! 4d chess ...
I'm aware of zrok/openziti, but I'm looking for something with a protocol-first design. Does zrok have a well-specified protocol that can easily be implemented by others? If not, since you're running a company, you aren't incentivized to make zrok easy to self-host. You can also relicense at any point. Doesn't mean this will happen, but incentives aren't aligned.
The vanilla interface often allows what's right depending on the context (e.g., if an unnamed return value is passed in, it can be move constructed, otherwise it can be copied). I saw some code bases provide an override for a const ref and a normal type.
No that’s something else.