skysight-inc/HackerNews huggingface dataset:
The first thing I did for my PhD in experimental quantum computing was to rewrite the lab control equipment in Python. It was written in LabView and while it worked well it was an absolute mess of (literally) tangled spaghetti code. I designed and implemented one of the first MVC frameworks for quantum computing in Python. It had an interactive IDE where you could execute scripts and store snippets (e.g. for qubit calibration), an instrument manager that allowed initializing and managing all lab equipment (locally and over the network), a data manager that allowed capturing and exploring measurement data in real-time and instrument frontpanels that allowed interacting with instruments (e.g. microwave sources or waveform generators).

Initially my supervisors were very skeptical and thought I'd waste my time, as they did not see any value in software development. Having a programmable and well organized software framework was absolutely instrumental for my work though, and I think I couldn't have succeeded at my experiments (demonstrating quantum speed-up for a simple quantum algorithm) without it. Today the software is still in use in several labs and as far as I know they also hired a research software engineer to keep developing it.
Not the France I'm living in. For tech jobs remote multiple days a week is the bare minimum, and for non-tech jobs, even old school institutions have optional remote work.

Baring some exceptionally shitty companies where the top management can't figure out computers and think everyone just slacks off the whole day from home, or companies in sensitive sectors ( defense) partial remote work is the norm now.
If you want to be web scale, the easiest thing is to use /dev/null as a data store.
6 days ago 500 points 100 comments: https://news.ycombinator.com/item?id=31520483
The same one I read every day. The One Year Bible. It's about a 30 minute a day read. Excerpts from Old Testament, Psalms, Proverbs, and New Testament. It reminds me wisdom doesn't just live in my head. It also reminds me much has gone before me and much will go on after me.

https://www.amazon.co.uk/One-Year-Bible-NIV-ebook/dp/B007EF7...
I think that’s a modern way (or maybe techie?) way to think of the old adage that time is an illusion.
Change nothing for you, perhaps. But surely you aren't the only person who matters?
On my world corner, HP-UX, Solaris and Aix were still the UNIX workhorses we would thrust to put into production, with CERN being the exception where I used Linux in production.

Yet, even CERN in early 2000's while migrating from Solaris to Linux (my office had a pile of pizza boxes to be thrown out), most researchers were using Windows 2000 with Framemaker/Word for writing their papers, with remote tooling to access the devenvs.
Wikipedia policy about biographies of living people prevents this kind of “expose” type article from being written.
They should pretend to work somewhere else: Elon on working from home
Fun discovery: some of my own pictures are up there around my house! I've documented hundreds of species in my garden using iNaturalist, with all photos CC0 in the hopes that they'll be useful to someone. Neat to see that some at least are getting found and used :)
There is a huge difference: Universities don't do reseach, and they don't care about the research their employees do. If you switch jobs, your old employer doesn't hire anyone to continue your research. Instead, you usually take your project to your new job.

In the industry, your employer tends to own the projects you work on.
Atatus Real User Monitoring can definitely help you to identify frontend errors and fix them when it is so unstable
Nice to see the emphasis on the advantages of "plain text". Nearly all my important computing is just "plain text", including the 100,000 lines of typing of .NET code, that appears to run as intended, for my startup's Web site.

For calendars, right, that's important data. Sooooo, I wrote some software that is correct back to Pope Gregory. E.g., can read Gone with the Wind, look up the date of the firing on Fort Sumter, and then know the day of the big BBQ!

But my plain text calendar program just prints out for any given year, for each month, a traditional calendar format, e.g.,

January, 2022
Sun Mon Tue Wed Thu Fri Sat
__ __ __ __ __ __ 1
2 3 4 5 6 7 8
9 10 11 12 13 14 15
16 17 18 19 20 21 22
23 24 25 26 27 28 29
30 31 __ __ __ __ __

Right, for the movie:

April, 1861
Sun Mon Tue Wed Thu Fri Sat
__ 1 2 3 4 5 6
7 8 9 10 11 12 13
14 15 16 17 18 19 20
21 22 23 24 25 26 27
28 29 30 __ __ __ __
__ __ __ __ __ __ __

Right, there is a lot more we
want to do with calendars!

Sooo, I wrote code in Fortran, Rexx, and Kexx (macro language for "plain text" text editor KEDIT, by far my
most important computing tool) that, given one of either (a) month, day, year or (b) number of days since the start of the Gregorian calendar, will return the corresponding other. So, easy to calculate number of days between two dates, day of week, etc.

Then can easily write other little programs to do a wide range of applications of manipulations of calendar data!!

So, there's another theme: End users get some general purpose tools, e.g., subroutines that do the hard work, and with those tools write short programs that give them what they want, likely all in easy to work with plain text.
Japanese are not poor for a long time, but still they die of overwork.
There must be a cultural thing pushing them hard like this
I'm fairly sure he's explaining the glitter he's using is "environment friendly"
> To make a blanket statement like this shows a lack of judgement.

In other words, nothing new. If there's one thing I associate with Elon Musk it's blanket statements that show ignorance/stupidity/lack of judgement/bad character.
I think minimizing compile time is a weird metric to prioritize. It's essentially asking "Would I rather guarantee my program is more correct or save a few seconds each time I compile?"

I would also point out that not forbidding bugs that would be caught by a type-checker will decrease efficiency. You just won't realize it when it happens.

Lastly, the impact on compile time doesn't have to be so great to be problematic. Plenty of languages with more expressive type systems have reasonable compile times. Some do not, I agree, but I'm not asking Go to leap to the forefront of type theory... I just think they could've done better.
You need to be very good, knowledgeable, always willing to learn and research, hard working and you make 50% of what a guy who did a 3 months bootcamp makes for working at a Rails crud app.

Where do we sign up?
A glorious past is pretty irelevant in the current market when you consider all the EU hardware jobs that have been lost or offshored in the process of Nokia's decline.

It's one of the reasons why embedded gigs pay so little in the EU.
My favorite feature [1]:

> PASSWORD PROTECTION: Want extra protection on your domain when changing certain features or getting an authorization code? Within the Password Protection section in your domain Details area, you can set a password by selecting the toggle switch "ON." From there you can create a password that will be required to enter when managing certain aspects of the domain.

They also support security keys (WebAuthn) [2]. I’ve used them for 3-4 years and have no complaints. I don’t like the handshake stuff, but you can’t blame them for wanting in on that windfall.

1. https://kb.porkbun.com/article/175-domain-details-area-expla...

2. https://kb.porkbun.com/article/119-how-to-secure-your-accoun...
> What makes a Wordle square yellow? The answer is not so simple

Well, I would say the question is poorly posed. The answer to the question as posed is simple as can be if the guess contains no duplicate letters. But if the guess does contain duplicate letters, the question as posed doesn't necessarily have any answer. It may - if all duplicates should be yellow, or if some of them should be green while all the rest are yellow, there's only one valid way to color the guess. But in the general case, you have some number of green squares, some number of yellow squares, and some number of dead squares, and you can swap yellow for dead without affecting the validity of the coloring.

So the question you should be asking is not "should this square be yellow?" but rather "how many yellow squares should this guess receive?". Then you can just choose appropriate squares to color yellow arbitrarily.
As someone who had never really dabbled in the markets before 2020, and only parked his money in passive investments, the amount of money floating around was an eye opener. It was also terribly demoralizing - there’s literally billions and billions of virtually free money that it makes working hard at a job feel stupid, if not worthless.

I made more money from a lucky gamble in a crypto coin than I did in 3 years of work.

I can’t be the only one in this boat. I suspect a part of the labor shortage problem can be attributed to people finding out how cheap money really is, and that “working hard” for money seems like a scam.
Human memory is a strange and wonderful thing.

Reading the article and comments brought back floods of memories. Of the exact circumstances when I bought each of the paddles I've owned [I've been kayaking for 35 years, in most disciplines, in 3 countries. So I have bought a lot of different paddles...]. Likewise all the trips, marathon races and canoe polo tournaments in bad weather when wind gusts tried to snatch the paddle out of my hands.
Need a software engineer? Hire me, then. My last employer was charging $150 an hour for my time, and I'd say most clients felt it was a fair deal, or a good one. I quit to do other important things with my brief time on earth, and now that I'm looking for a software dev role again, it seems I'm hardly worth a third of that.
I'm sad to say this even happens at FAANG. So many engineers seem to either not want to or not know how to optimize their own workflow as they're building it. It's really frustrating when you want to contribute something to their project and the development workflow for verifying the application still starts after making any changes is "upload the 5GB deployment bundle to AWS". Like come on, you can't seriously expect people to be productive that way.
By definition, 50% of jobs are going to be below the median wage. That's what the median means. Why would an entry level job that doesn't require a college degree pay more than 50% of all other jobs?

According to this[1] the median is $19.33/hr, so Tesla is not far off. It's above with overtime.

[1] https://policyadvice.net/insurance/insights/average-american...
Interesting tool, but their video has the worst example of soulless stock music in it I've ever heard
Solid is great, you can also use it with hyper dom expressions: https://github.com/ryansolid/dom-expressions
Academically, it would fall under “guerrilla marketing”. It is a high risk, high reward technique. If it pays off, you can get quite a lot of attention for very little money.
Congrats. v1 is very good.
Hire Talent and Ability, Not a Skillset
RSEs should not be working on, or assisting, research at the PhD level. By that I mean news/skunkworks stuff. They should be taking the output from a PhD and turning it into core software for the group. That doesn't solve the collaboration issue between PhDs/Postdocs, but there is a particular point in a research project lifecycle where it makes sense to hire an RSE.

A bigger challenge is that most PIs are not project managers and have no experience as such, so they don't know how to express what they need in a structured way, or how to steer their group to collaborate properly. Outside computer science, many would struggle to budget software development or compute properly on a grant application (and the assessors have zero idea either).
> thanks for heardle! have you tried nerdle?

https://www.samandfuzzy.com/3138
In the world of ever increasing cost of living, sane ppl will always take best compensation offers.

Everyone has the same thinking that we will be here 40-70years and our finite time is worth more and more.

Im sorry for the ppl tho dont have options to do better for w/e reasons.
> Why, in your opinion, do we need to use those gas turbines?

Because we need the power, simply. That's unrelated to the other plants we have, though.

> I showed limits (stated in the very same document)

These limits are not preventing NPPs to participate in both primary and secondary reserve mechanisms which are used to balance the power grid. See [1] for more details.

[1]: https://hal-edf.archives-ouvertes.fr/hal-01977209/document
It's not the full cost though. That's just the operating cost.
The document you linked has 38.3% of "grazed grass" and 26.3% of "conserved grass". That's 64.6% of grass.
That's how it's now, but can you predict it will be this way in the future? Things change over time.
Lookup the recent Hacker News history about Namecheap.

It turned out that they are mostly a Ukrainian company, and when the war started the CEO decided to terminate “services to users registered in Russia” with only four work days notice.

I don’t know if any customer account was actually suspended. I also don’t know what “registered in Russia” means, is it nationality, residency, billing address, customer’s IP address or the A record. Some EU clients also received this letter.

I can relate emotionally. But this way to address existing customers, which have paid for their services, is whimsy and unprofessional. I also think that discrimination based on region or nationality is unnecessary broad. It certainly didn’t stop Putin.

Just to be clear, I believe Ukraine needs and deserves all kind of support to win this war.
Is this real?

https://mobile.twitter.com/WholeMarsBlog/status/153180754672...

> …

> Anyone who wishes to do remote work must be in the office for a minimum (and I mean *minimum*) of 40 hours per week or depart Tesla. This is less than we ask of factory workers.

> …
I suggest you search for the relevant terms with "site:archive.org", then if puzzeled by the suggested audio formats klick on "show all" and voila!
It wouldn't have the performance that it has. Cassandra does the same. YugabyteDB does the same https://docs.yugabyte.com/preview/reference/configuration/yb....

> I would expect stronger guarantees from databases.

You can configure it and get lower performance.

> Maybe it's inpractical to expect this in cloud environments...

For benchmarks they use raid0 on local disks(not EBS) in aws vps.
Create Reddit Videos with just one command
canoe polo is kayaking, no?
But that is what falls into "affordable housing" category. Comment I reacted to said it is not needed, because people move.
I don't know, it seems pretty common for people to be straight up on HN. I didn't get a sense of superiority or insult from the comment - just statements that the author believes to be true.
Definitely not a no-brainer. Don't want my CSVs integrating with APIs (or in the cloud at all), and I'm confident the desktop version handles large files better than a cloud solution would, as well as being far more responsive, quick, compact than any web-based solution.
And then you choose one questionable metric, and didn’t explain why you found it compelling or how it is is meaningfully related to work culture?
I know several communities who happily moved off FB for discussions. They often don't care, and also heard how FB can be bad for your mental health. You just need to show a better way and help them convert.
I didn't see mention of textual, another python tui library. But it's also great for good tui programs
loot boxes = gambling for children
Yep, work in b2b banking as well and there is a huge issue with banking ‘test’ environments. Our partners (100s of companies, mostly banks/brokers/insurers/etc) mostly don’t even have test envs and if they do, they don’t represent production at all (sometimes the api is a completely different version etc). Our software allows to spin up a test/dev env locally or where ever but nothing much works without the partners and to dev/test those, those, you will have to dev/test against their production systems with real money.

In the beginning (more than 20 years ago), I insisted that we implement test systems ourselves so we didn’t have to test in production; that was naive; it was expensive and there is so much complexity that this does not work well.
I mostyl use PlantUML and C4 Model (by Simon Brown). I have my own collection of PlantUML related resources [1]. I've also recently found these examples [2] which are really nice.

I also do some sketchnoting (using pen & pencil) when I design a system for the first time. I wish I could easily convert those sketches to PlantUML.

[1]: https://brainfck.org/#PlantUML
[2]: https://skyksit.com/programming/uml/plantuml-samples/
So now we're reverting to haruspex...
The deemphasizing of peer review BEFORE publication will kill science. The amount of noise and nonsense proliferating just causes confusion and lost of trust...
So how do you square they circle "Don't design to scale but scale up quickly when you need to"? You can't rewrite your stack just because you took on a new customer that is suddenly killing you.

I don't think that it's stupidly hard to get basic things set up for scaling at the start. These don't apply to everyone but:

- use a cloud provider, they let you grow

- write infrastructure as code (terraform, pulumi, cdk), it's not that hard and it makes building your 2nd, 3rd data center easier

- for the love of God think for 10 minutes about a scalable naming convention for data centers, infrastructure components, subdomains, IP ranges etc. This type of stuff causes amazing headaches if you get it wrong, and all you have to do is consider it at the start. Many AWS resources can't be renamed non-destructively, and are globally namespaced. Be aware of this. Don't paint yourself into a really stupid corner.

- even if you're not doing microservices, consider containers and an orchestrator that has scalability baked in (like Kubernetes). If you use a managed Kubernetes with managed node groups or fargate, you can basically forget about compute infrastructure from this point on

- deploy Prometheus, Grafana, Loki etc day one and build basic dashboards. With Kubernetes, you can get this installed quickly and within a day you'll at least be able to graph request/error count and parse logs.

- deploy an environment for developers to deploy to and use the product (even load test it)

The development cycle is now set up for building what you need to build. You can easily find developers at any level who have experience with containers, Kubernetes, Grafana so they can onboard quickly, be productive and troubleshoot their own stuff. They can refactor the monolith without having to invent service discovery, load balancing, ingress etc.

My personal experience with Kubernetes began at a start-up with a tiny team, none of whom had prior experience with it. We had started building a single monolithic app. But within a short time we figured out how to make a helm chart, add ingress and boom, we were "online". Every time someone was about to spend time and effort inventing something, we would quickly scan through the Kubernetes docs and CKAD material to see if we could avoid having to build it at all. We leverage cloud stuff too, where it was cheap and easy and scalable (like AWS SQS/SES/SNS/CodeArtifact/ECR/Parameter Store)
Definitely, yes. It is very accurate.
https://lwn.net/headlines/rss
https://www.theregister.com/offbeat/bofh/headlines.atom
https://xkcd.com/atom.xml
It looks like a distinction without a difference. We can consider `None and f()` pattern as explicit syntax that unwraps objects as necessary without infecting other code.

Background: an object that either None or true in a boolean context (true unless overriden for custom objects).
Given such object, we can consider it in a virtual Maybe container/box.
When we want to use it, we have to unwrap it using `obj and obj.method()` syntax.
Then `obj.method()` is ordinary "unwrapped" call.

Just to remind you. Here's how "ergonomic" Maybe variant from the article look like:

# Type hint here is optional, it only helps the reader here:
discount_program: Maybe['DiscountProgram'] = Maybe.from_optional(
user,
).bind_optional( # This won't be called if `user is None`
lambda real_user: real_user.get_balance(),
).bind_optional( # This won't be called if `real_user.get_balance()` is None
lambda balance: balance.credit_amount(),
).bind_optional( # And so on!
lambda credit: choose_discount(credit) if credit > 0 else None,
)

https://github.com/dry-python/returns#maybe-container

You can decide for yourself what is more readable: all these lambdas or the `None and f()` code.
Cloud Data Warehouse for Engineers – Firebolt
Tldr; use frequent iteration / feedback loop as enterprise-advantage alternative to build trust. Ahh, people really do like fashion though, peer testimonial, network effect etc involving kinda semi-real value construct just like the enterprise does (just spend more money because they can afford to)
Ripple Energy (https://rippleenergy.com/) in the UK are offering exactly that, but with Wind Farms. You buy into a cooperative that builds and owns the wind farm. The generated energy is sold back to your utility and taken off you energy bill. It's very much like having local renewable generation, but can be used by those like me who live in an apartment and have no way to install solar.
My thinking is much the same, though living in a higher and winder latitude I'm participating in a wind turbine co-operative (UK only though) [0]

It's not classed as an investment for tax reasons and limits you to 120% of your estimated residential consumption. It will essentially remove the wholesale cost of electricity from my bill for 25 years - so protects me from price spikes like the past 12 months.

My town has a river running through it and would love to invest in a similar hydro scheme. The LCOE for wind/solar/hydro would seemingly always beat fossil fuels, given how finite the latter is.

[0] rippleenergy.com
Tried this many times, never got it to work properly.

I’m not sure if it’s because my teams are too small, or I’m bad at communicating.

When discussing technical specifications the most efficient way in my experience is to throw people into a room with a whiteboard and a few laptops and don’t let them come out until they’ve ironed out each other’s concerns; while this is uncomfortable, the alignment is unmatched by anything else I’ve tried.

In my current role we write detailed technical specifications in google docs; but the end result is similar, an ocean of tech specs that may be defunct or relevant or in draft status, dense reading and/or infinite questions once the document is produced (or worse: no questions at all! Which means either people didn’t understand it or they think it’s fine).
There's elements of this also represented in GNU Parallel, a really nifty utility that lets you create a fork-join pool out of one or many systems. IMO it is severely underused these days.
As a counterpoint, I know someone who went back to academia after getting disillusioned with tech (academia > tech > academia). The key difference may be that they live in Europe, have no student loans and the pay disparity between a developer in bioscience and in tech is not as large as I imagine it is in the US. They are paid significantly more than the scientists they work alongside but not much less than they were paid in a good tech job. For them the bioscience work is much more interesting than anything they did in tech (they have a maths-based PhD, so were working on quite complex problems but in a relatively boring field).

Software development is important to more and more industries and the pay disparity caused by insanely large funding and little requirement to produce profits means that other sectors are being priced out of in-house development, especially niche use cases. The ongoing rise of no-code development will be increasingly useful across all sectors but will fail to deliver a lot of these niche applications.