skysight-inc/HackerNews huggingface dataset:
How to make a million:

Sell 1x $1,000,000
Sell 10x $100,000
Sell 100x $10,000
And so on

Why are startups selling expensive underware? Because they want to earn a million with a low volume.
And there are people willing to pay for it!
I've set this up recently with a cheap(~$20) USB microphone and just have it running on the back porch and it's been such a delight. Loving it!
Based on the advices and the feedbacks received about our datas and evidences, we added syntactic sugars to our codes, which is sure to make us more moneys. Thank you for your hard works.

This is indeed excellent new.
Google does that, Microsoft doesn't. Microsoft will ban you from a particular service if you egregiously violate the terms of service for a particular application of theirs, but never the whole account.

Google will throw you on your ass in the blink of an eye.
TFHE – a fully homomorphic encryption scheme based on LWE
That describes most software design and development to a T. The reality is you'll hardly ever get the design right the first time around.
The problem with this is that you're now the Ministry Of Truth of programming tools.
Plex, then maybe Node-red for the lights, then Matrix and Nextcloud.
Agree with this Adam.

Avery and the team at Tailscale are building a fantastic product and totally deserve the round and recognition, huge congratulations - we're super happy for them.

In many ways they're also an ice-breaker for the zero trust overlay network architecture, which means they've got the most work to do. As the current top comment on this thread correctly notes, with huge investment comes the obligation to eventually pay it back.

The market hasn't even come close yet to crossing the chasm and seeped into mainstream conscience to become the accepted norm - yet.

That said, we believe fiercely that networks should be simple to reason about, easy to use and safe to operate. That private connectivity should “just work”, and just work in exactly the same way, everywhere too. Flexible to change, simple to automate and only available to the right things at the right times.

When you think about it, building private networks is actually pretty complex right now and can be pretty insecure too. It's some unholy combination of spell casting meets a yak shaving contest to wrangle firewalls, VPNs, MTUs, and manage IPs, subnets, ACLs, NSGs, VPCs, NAT, routing, VLANs, certificates & secret keys, then hoping a zero-day doesn't show up that drops someone straight into the network via the VPN server, who then starts poking around the squishy centre.

Once you've used products like Enclave, Tailscale or ZeroTier and seen how simple private networks really can be - at a certain point you almost stop and ask the question, why would you not do it like this.

There will always be nay-sayers and people for whom this approach just isn't a fit, and that's fine - but I personally find it hard to imagine that this genie can be put back in the bottle.

- Founder @ https://enclave.io
maybe perl code is a bit unreadable at times, but its documentation is very readable.
Just look at:

https://perldoc.perl.org/perlfunc#Perl-Functions-by-Category

All the standard library ordered as links, by categories that actually make sense!

Also perl5 used to be very accessible, even the parser error message made actual sense. I think that a lot of care has been put into these details, and that this attention to details did have a role in the success of the language.
I'm very surprised they don't make the sitting/hanging notes semicircular, so they're much more visually distinct (like stalactites and stalagmites).

Instead they seem to have tried two different systems for the sitting/hanging notes, both of which look very hard to read to me: https://clairnote.org/clairnote-dn-clairnote-sn/ (although as you say, if you already know traditional notation it's hard to look at this with an unbiased eye).
No, no, no, no. You haven't really experienced the quality of IPv6 routers at home. The only thing that I can (probably) say with confidence is you will not need TURN, and even that assumption can be broken with even more restrictive firewalls that block nearly all UDP traffic or even not know your real public address because IPv6 NAT does exist (https://blogs.infoblox.com/ipv6-coe/you-thought-there-was-no..., https://datatracker.ietf.org/doc/html/rfc6296), but fortunately this is usually found in enterprise stuff. NAT-PMP or router UPnP is probably the wildest: majority don't (remember that I'm focusing on ISP routers since that most people don't bother to switch to actual routers...*), some only on IPv4 (which is even more frustrating), and only few supports it correctly. Worse, those same broken garbage-level routers have NAT-like firewalls: at least you know what address and port you will contact the other computer, but you will still need UDP (TCP handshake will be very problematic) and you will still need keepalives (or otherwise your firewall will just close the port).

* ... and most that do get another router (usually because they have seen that their Wi-Fi on the "modem" is bad) don't turn on** bridge mode which will be a definite headache on both IPv4 (double NAT) and IPv6 (address conflict, especially if you're using an ISP like Comcast that would only allocate a /64 and no more.

** ... because you need to call up the ISP or even outright refused to bridge it (either because they're stupid but you don't have another ISP to switch or the equipment manufacturer of their garbage special router didn't program one).
A project to design, build, fly, and deploy a prototype shadecraft satellite will be the focus of the Stanford EE Computer Systems Colloquium today, Wednesday, May 4, 2022. http://ee380.stanford.edu.
Holy moly, I thought I was the only one!

"Want me to write a specialised API with custom encapsulation transmitted over UDP?"

"Nah fam, we want to watch you code in our super-duper-wiz-bangy-exclusive IDE that you've never used before. Oh, and you have an hour. Oh, and it's going to be super-specific tasks that only we know how to do."

"So, no on the encapsulation, eh?"

<click>
I should also note that I'm glad that there is a movement to make cities more walkable, but I duck out when that sentiment pours over into a sort of religious zeal against more nature-ful ways of life.
Cloud pay-as-you-go may help balance this out. With an in-house cluster, the capital cost is paid, sunk. With a cloud deployment, there is a tangible impact of wasteful code right there on the balance sheet every month.
> Such as not wearing a mask, for example.

That's pretty rich
If uptime is the goal, individual humans are impressive compared to almost all human technology.

The Centennial Light has now been running mostly continuously since 1901, while the oldest living human was born in 1904. The bulb hasn't burned out, but has been shut off briefly a few times, which seems comparable to one's heart stopping but being resuscitated.

I'm not aware of any single "technology," in the broadest sense, operating for a longer continuous period of time.
My advice is : work with more senior people.
It seems to me that people with 10/15+ years of experience will judge this hype train more severely than younger ones.

The dangerous spot is engineers with 5-10 years of xp who have become good enough at writing huge piles of unecessary code and have them work.
Yeah, I had the same reaction. I can’t really imagine this would be any easier to learn, and doesn’t seem to solve any problem I’ve ever had with standard notation (this is with 20 years of music experience across several instruments).
I was so confused by the title, I didn't think that CDs got much trading -- they don't, this article is actually about CDS or credit-default swaps. Turns out that's a load-bearing capitalization.
Besides those lifestyle companies that can afford billboards, there are the 3 million online stores that advertise on facebook and sell product that's on aliexpress for 1/3 to 1/5 of the price. Usually with time pressure built in on the lines of "we're liquidating our collection, take this chance at...".

Except maybe the chocolate. I don't believe the popular brand that he mentioned has actual chocolate in it.
I thought the post was remarkably well written. I had a vague idea what Tailscale did going into it, but this post did a good job of describing the company's values and vision. I'm not sure what the intended audience of the announcement was, but for me it was interesting.
> Is k8s really all that hard? Build a container and you don't have to worry about provisioning it and deploying it again.

No, the deployment of a container to Kubernetes isn't hard. And it better not be, that's supposed to be the advantage.

What's hard is literally everything else about it. And that may be a fine tradeoff if you are at the scale to need it and have a team to manage it. But there are many organizations where that tradeoff does not make sense.
A hash table that compares hashes instead of keys, doesn't support deletion, doesn't distribute keys evenly etc. is not even wrong; criticizing it is definitely not "crap for daring to exist", especially in the polite tone of the linked article.

If Hare is intended to be a deliberately Spartan C replacement, so be it; but pretending that writing a hash table is easy looks like the immature and arrogant opinion of someone completely unaware of his ignorance.
Yeah been there and being there too. I'm kinda used to confluence finally because nothing else beats it yet.
I've gotten a couple interviews. No job though.
They combine lit-html with a "basic scheduler" that they've written themselves. I'm guessing that's intended as a replacement for React, but it could easily be seen as a replacement for Lit, which offers "reactive properties" too.

I think how they gloss over the "we'll just write a library to handle component rendering, lifecycle and state" portion as a "basic scheduler" is a bit disingenuous. The author even mentions they are essentially recreating some features of React, but felt it was worth the tradeoff.
Another day, another overly hyperbolic press rele.... er, blog post

Le sigh...

Let's make tech boring and demure again!
I'm also jaded from all the new frameworks and "paradigms". (Similar to how every exploit must have a catchy name nowadays.) However, I genuinely love the innovation and ingenuity of software engineering. The industry will find simple solutions, but not in the way you think: the language and mental models will advance, making what now seems complex into a simple thing.

Phone calls are stupid complex nowadays compared to the old point-to-point wiring, but we can still very easily "pick up the phone and dial." It's an abstraction/mental model that's held since PBXs became automated.

When I studied machine learning 20 years ago, it was barely used, and everything was "from basics." The applied stuff was very simple, like an auto-encoder. Today, the way you think about, and teach, ML is not "a matrix here and a vector there," but in combinations of ANN layers.
Russian citizens aren’t funding the war machine. The EU, China, India, etc are. But sanctioning them is admittedly actually hard :-)
I'm talking about services like NordVPN, Mullvad, etc. They do not funnel your Internet connection through their servers.
I've been wearing army issue (finely knitted semi-synthetic wool I think?) for a long time, I'm never going back to cheap cotton socks. They're much cheaper, but they're not comfortable.
The crazy thing is grass lawns are HIGH maintenance. It’s effectively an economic signal - “look at me, I have time and money to maintain this useless patch of grass!”

It’s much easier to plant a mix of greens - clover, grasses, etc (effectively pasture seed blend). Requires less water, less mowing, and much less fertilizer.
On the Essence of Computer Science
On the essence of computer science

"I'd like to welcome you to this course on computer science. Actually, that's a terrible way to start. Computer science is a terrible name for this business. First of all, it's not a science. It might be engineering or it might be art, but we'll actually see that computer so-called science actually has a lot in common with magic, and we'll see that in this course.

So it's not a science. It's also not really very much about computers. And it's not about computers in the same sense that physics is not really about particle accelerators, and biology is not really about microscopes and petri dishes. And it's not about computers in the same sense that geometry is not really about using surveying instruments.

In fact, there's a lot of commonality between computer science and geometry. Geometry, first of all, is another subject with a lousy name. The name comes from Gaia, meaning the Earth, and metron, meaning to measure. Geometry originally meant measuring the Earth or surveying.

And the reason for that was that, thousands of years ago, the Egyptian priesthood developed the rudiments of geometry in order to figure out how to restore the boundaries of fields that were destroyed in the annual flooding of the Nile. And to the Egyptians who did that, geometry really was the use of surveying instruments.

Now, the reason that we think computer science is about computers is pretty much the same reason that the Egyptians thought geometry was about surveying instruments. And that is, when some field is just getting started and you don't really understand it very well, it's very easy to confuse the essence of what you're doing with the tools that you use. And indeed, on some absolute scale of things, we probably know less about the essence of computer science than the ancient Egyptians really knew about geometry.

Well, what do I mean by the essence of computer science? What do I mean by the essence of geometry? See, it's certainly true that these Egyptians went off and used surveying instruments, but when we look back on them after a couple of thousand years, we say, gee, what they were doing, the important stuff they were doing, was to begin to formalize notions about space and time, to start a way of talking about mathematical truths formally. That led to the axiomatic method. That led to sort of all of modern mathematics, figuring out a way to talk precisely about so-called declarative knowledge, what is true.

Well, similarly, I think in the future people will look back and say, yes, those primitives in the 20th century were fiddling around with these gadgets called computers, but really what they were doing is starting to learn how to formalize intuitions about process, how to do things, starting to develop a way to talk precisely about how-to knowledge, as opposed to geometry that talks about what is true."

-- Hal Abelson, Structure and Interpretation of Computer Programs, MIT
Anything that uses YAML for starters. It's just too damn easy to accidentally have something indented wrongly by a single space or tab or whatever, and have the whole thing blow up in your face. It makes working with Kubernetes and Ansible a royal pain at times.

Not a fan of Outlook either. Reason #1 - the search capability blows.

And then I'll add OS X. I use a Mac at work for a couple of specific reasons, but on balance I'm not a fan of OS X. I'd much rather use KDE on Linux, but our options here are Windows or Mac. :-(
1Password has Fastmail integration that maps the random email back to the service: https://1password.com/fastmail/

Downside is you have to use 1password AND fastmail obv.
There's a difference between Calvin Klein's regular underwear and their premium ones. The premium ones are comparable in price to something like Saxx
> these companies aren't marketed as lifestyle, just sensible products.

Sensible is the lifestyle they are selling. Sensible is the Tech lifestyle.
I'm also using KeePass and I have my own NextCloud instance, and with the Android app + browser add-ons I have an as good experience as with cloud offerings, and maybe even better since I can also use it as an SSH agent to store my SSH keys.

But honestly with all the updates I'm putting off I'm probably actually more at risk, and a good password manager implementation will encrypt all passwords client-side so you're not actually uploading your passwords to anyone's computer.
To my eyes this is way harder to read than traditional notation, which really isn't hard to learn and works well for most music (and non-12TET music). It's hard to see if a note is on a line or just above/under it.
I love Bitwarden. What I do is self-host an instance, available only on my network (so not open to the world). Whenever I’m home and I use Bitwarden on any of my devices they sync automatically. I’ve found this use pattern to be pretty good from a “devices are up to date” perspective. I get all the benefits of “cloud sync” across my devices without worrying about a service breach.
I yada yada yada’d over a lot. I was first exposed to consultants when I was the newly hired lead at a company in 2016 brought in to design an on prem project. At the last minute, they decided to “move to the cloud”.

They brought in two sets of consultants. One set that was suppose to know about AWS. But they ended up just treating AWS like an overpriced Colo and I didn’t know any better at the time and the other set who in hindsight were just following a cookie cutter script who were “helping” the business manage integrating a bunch of recent acquisitions.

Once I started belated learning about all the services that AWS had to offer developers and for “DevOps”, I knew I wanted to specialize in consulting in that area and set myself apart from the old school network folks who got one certification and called themselves “cloud architects”.

I figured I could bring more to the table from a software engineering standpoint.

I changed jobs in 2018 where the then new CTO wanted to be “cloud native”. He was trying to build out an internal engineering department. He knew I had no hands on experience with AWS. But he liked my proposals.

Two years and a lot of projects later, I had the technical side down pat. It took me a couple of years at AWS to get good enough at the soft skills/customer interaction side.

My original plan was to get a job at one of the big consulting agencies to hone my craft. I got lucky to skip over that part.
The fact is that the limit of 80 characters length is arbitrary. No evidence that code of 80 characters length is more readable than code of 83 characters length.

The other fact is that few devs craft their code to fit 80 characters. Instead they write code and let formatters do their thing. But automated formaters are doing a horrible job, aka if I write a line that is 81 characters long, they will massacre it to a set of unreadable lines with no proper aligning.

So now we are at the mercy of automated formatters that try to enforce an arbitrary constraint that is irrelevant with today's code editing/reviewing technologies.
Hey all, one of the creators of ArcticDB here. We're going to be around for a while and answer any questions you might have about it!

It's open source so if you just want to check out the repo: https://github.com/polarsignals/arcticdb
I'm a specialist in low-level telco code, lots of which is written in C/Perl.

Recruiters are breaking down my door, asking me if I code in Ruby (Rails).

No.
I love Perl. I use almost none of its more esoteric features, and just write "classic procedural" code, mostly using command-line utilities instead of third-party modules for anything I don't want to write myself (mainly cryptography), and I am so fucking happy not having to deal with breaking changes in my language, a rare quality these days.

I used a machine with a 9-year-old distro on it for a few months, and all my scripts ran without issue, and I have high confidence that they will continue to run for years down the road without my having to adjust them for breaking changes in the language runtime, which is more than I can say for most other stacks I've used.

Furthermore, ALL the code examples I can google up will work without me having to check if they're for the right version of Perl, because it has near-perfect backwards compatibility going back all the way to 5.000 from 1994.

About the only other thing with a comparable level of stability has been HTML/JS/CSS, which gets a lot of new features all the time, but, for the most part, if I use only minimal features, remains usable for years without modification.
You have a lot of faith in these brands. Bombas was founded in 2019 by an MBA grad and a marketing graduate. They have no reputation. These aren't like hand crafted sock makers doing this for decades in Italy. They're advertising companies and they sold you.

As to where they're made its unclear:

> Where are your socks made? We produce our products all over the world, including the US, Taiwan, China, and Peru at the most technical and highest-rated manufacturers.

> We're proud to report that all have passed audits with very strict standards for health, safety, and social compliance.

And to note I have both Bombas and Fruit of the Loom currently in my drawer. The difference is negligible in my opinion. You can ask me in a few years if my Bombas held up, but I can tell you my cheap Walmart brand stuff has held up.

[EDIT] Bombas was founded in 2013, not 2019. 2019 was the date they started selling t-shirts. Point still holds that they don't exactly have a track record compared to a legacy player and I still doubt they'll exist in 20 years
Basically every service has already been packed full with so many things that an instance can barely fit on a server, you wont be able to run that monstrosity locally. Which is why they started doing "micro services", out of necessity since when each binary gets over a few gigabytes you don't got many other options. their micro services still takes gigabytes, but it let them continue adding more code. But each of those depends on hundreds of other micro services. And those microservices are of course properly secured so you wont be able to talk to production servers from your development machine.
Can you explain a little more? I don't know what you mean by 'blobs to boot and run'. As far as I know, the latest Linux kernel supports the raspberry pi.
A natural gas furnace is up to 98% efficient. A natural gas turbine is 40-60% efficient; a modern heat pump can have a COP of 3 or even 4, for 150-200% equivalent efficiency (ballpark).
It offsets the disappointment of being a parent that hopes their child can have a meaningful life beyond being a worker drone.
Cloudflare already has a competing product https://www.cloudflare.com/en-in/lp/ppc/cloudflare-for-teams...
Databases are measured in gigabytes and terabytes. If you put only a portion of it in source control, how do you back up the rest of your database? Furthermore, static data is a minor subset of a database. Data by its nature is volatile. Transactions make up 80% of the data. A projection or snapshot/summary is a the summarization of the daily/hourly/minute transactions. If you want a golden copy to bootstrap new environments, I would argue you are better off backing up that golden copy and restoring it using native database tools. Mashing together two very different paradigms will lead to long term disaster. There was a thread about a year ago, when a DevOps engineer was surprised when his "nonproduction" configuration code deleted his production database. If your database is a terabyte in size, by the time you restore the database -- you are already fired.
/me larts @6stringmerc with a very large trout.
It might be annoying to implement well, but there's a reason no widely used programming languages (other than assembly) have add_int and add_float as separate functions.
Very true, but unlike backend languages you can generally get away without knowing much about the internals. Unless you're making dev tools of course.