skysight-inc/HackerNews huggingface dataset:
a few years ago I had a lot of trouble find a "junior" or entry-level programming position anywhere. eventually I found a remote web developer position. then various family circumstances occurred causing me to temporarily leave the position for awhile to deal with things. this was right as the covid stuff was ramping up. when I was once again ready to work, the developer unfortunately instituted a hiring freeze due to covid, so it was back to the job search once again.

I ended up finding work at my local school district. the two programmers who are in charge of our district of some 12,000 students are both over 50, and they were more than happy to hire me to learn how to keep everything running. it's not a glamorous job, and there's no doubt that my salary, even adjusted for cost of living, is not great compared to many other people who post here… but the benefits are great, and being the future of keeping my childhood school district running on the technology side keeps me feeling fulfilled at work. plus, I have incredible job security going forward.

for any "junior devs" looking for work: I recommend seeing if there's any local government positions like this that are available. my district can't be the only one run by programmers who are closing in on retirement, desperately searching for younger people to learn how to take the reins first. I'm mostly self-taught but even a self-taught level of understanding of SQL was sufficient to get hired—I've since learned quite a bit more on the job but a CS grad should have no problem at all.
its better to develop Marshall like plans for the affected areas (MENA + WESTERN AFRICA); them will generate stability,jobs,commerce and returns for investors. the problem is local political leadership which will want "tailored kickbacks" even at their countries stake (or will cry to go on China lap). but Necessities like the "green wall" could create an example on wich plan future project and garner support at alls levels. Btw Europe doesnt need migrants, its mostly overpopulated and economies are more about outputs than unskilled workforce. Paying pensions will be a problem, solvable with bankruptcies that could maybe cure the fetish for welfare socialism of PIGS+France. nations cant absorb generally speaking more than a low percentage of immigrants/settlers before creating problems/attritions.
Requiring a phone number is part of fraud & spam prevention. Maybe you'd make a different tradeoff but that's not "no reason."
Your question is trolling and not worth answering.
A tax on university endowments sends an important message to wealthy schools
Long-term effects after vaccination start early (during the first hours to weeks, rarely month) and are called like that because they last long. From what I recall there are no adverse effects known that started years after administration of a vaccine.
What unit is mm? Millimetres?
he's putting microchips in the vaccines and helping the government put sodium chloride in food
No Erlang can't share memory between cores atomically.

Erlang can only scale 1-to-1 things like phone calls.

Java is the ONLY language that scales many-to-many with stable non-blocking IO and concurrent parallelism that shares memory atomically AND doesn't crash.
OOP is fine. OOP and functional programming written by skilled programmers both end up being basically the same thing -- they are just different techniques to achieve encapsulation, control over dispatch, control over state, etc.
US sanctions Tornado Cash – and crypto shrieks in horror
Two of the top candidates for Satoshi are known to have died as well: Hal Finney and Len Sassaman.
Nothing ... except compliance.

The idea comes from finance -- to require collusion to execute a fraud. It's not perfect, but it's something.
They don't have FX installed. No one does.

The whole idea of using Java is to support something other than Windows. I use a Mac and all companies I worked with had all common OS's on desktops. The edge cases are the problem. This isn't a product for other engineers. At least not engineers who have experience with JVM conflict issues.

For end users and to get a smooth installer experience there's a huge distance. Customizing the installer in the packager is a nightmarish problem... Or at least it was the last time I did it.
I'm not sure what you mean by "ahistorical special privileges". Intellectual property rights have been around for centuries. Patents and copyright are specifically mentioned in the Constitution.
>Being the weekend exerciser means that I'm able to keep up with the athletes when they want to walk to the next restaurant / location...

Do you have that problem a lot? Because a whole lot more common problem is cardiovascular problems, obesity, and sedetary life.

And what I mean with "health as a goal" is "No need to try to be an endurance runner, or build serious muscle, or whatever, just do enough say cardio for heart health, lifting to be generally fit" and so on.

And it's not vague, as for those there are recommended guidelines and suggestions of the exercize amount - but one can do even better to get personalized ones from your doctor.
I don't disagree with what you are saying. It's just that everything is already free and as friction-less as possible. I made a point to remove any lock-in. My goal is to make Windmill fully-featured and available to the widest range of people. On the other hand, we do need to make some money at some point. We could have an "enterprise edition" with features that are proprietary. This is what most open-source companies do, but it would create misaligned incentives to not bake those into the product and make the product worse. If I am being honest I will probably bake SSO into the team-tier as soon as we have some healthy financials :)
> with each pass doing only its own thing without a context

That's exactly how people working in organizations deny any wrongdoing. "I'm just following orders in my cubbyhole and that's it; I have no idea where this stuff comes from or what happens with it after I'm done."

C89's "permissible" word does appear to prohibit situations in which some optimization is performed on the assumption of "no UB", where that assumption is obviously unreasonable.

It is permissible to allow unpredictable behavior to take place if the situation is "ignored completely".

If it's obvious that UB must be happening, but we ignore that, then we are perhaps "ignoring completely". Turning a blind eye is ignorance, but it's not complete ignorance.

For instance, consider an optimization which turns for (int i = 0; i >= 0; i++); into an infinite loop. This is based on 1) knowing that i is initialized to a nonnegative value and 2) examining every update of i in the loop and seeing that i is incremented. But if i is only incremented in the loop, it is inescapable to know that i overflows. Ignoring that situation looks a lot more like "blind eye" ignorance and not passive, complete ignorance.
mens rea. mens is feminine.

https://en.wikipedia.org/wiki/Mens_rea
> Ethereum has addresses just like Bitcoin has addresses.

The point is that Bitcoin actually doesn't have addresses/accounts. I think you are modeling this distinction as whether people clump all their money together into a single address/account or use a "wallet" of them (maybe all derived from a single key), but Bitcoin is way more abstract than that: there is no concept of an "address" at the level of Bitcoin itself... that is just a fiction created by an extremely popular way people protect money on Bitcoin. You might also note that Bitcoin tends to talk about different address formats (such as p2pkh), which often come from not merely different ways to serialize the keys but from different ways accounts have been protected with different scripts. In Bitcoin, you can have money that is owned by "anyone who can answer my math riddle" and that's that: unlike in Ethereum, it isn't that the money is owned by an account with an address which has code to restrict access, but the money is a little pile and the most universal "address" you can talk about is the script itself.
Ethereum is designed as blockchain based computation and not as a commodity first, so it doesn't make much sense to use a different address per transaction. You would need a single address/wallet to fund whatever program you're running on the blockchain.
Ah so baseless ad hominem is fine now?
Help Scientists Find Clouds on Mars
>Find a mechanic you trust, the car dealership will rip you off time and time again.

Car dealerships are mechanics, nothing special about them, and I've had incidents with small paces as well.

>I had to bring my car in for a recall previously, and they said right away that the brakes also needed replacing immediately.

So what? Say no if you don't want the work. Done. Do you get mad at every salesman who pushes their product on you?

>Ended up replacing the back after a year and a half

You can ride bad brakes pretty much forever if you want, nothing stopping you (pun). As he says, depends on "how you drive".

I'm still trying to wrap my head around why you're so upset about your dealer suggesting you get your brakes done...
I noticed that your only comments are 4 that are almost identical to the above. Is this because you are truly single-minded, or perhaps this is an AI/ML bot account?
congrats team on 1.0!!! huge milestone!

inevitable question that always can use answering - what can you share about Astro's company business plan/business model at this time?
The initial question was about "single point of failure". The answer is, don't create such a single point of failure in your life. And you regard someone doing that as "you must be either old or a hick". Maybe they're just someone who doesn't want a single point of failure for everything in their life.

For myself, I have a cell phone, but I don't have anything on it. No banking. No work apps. Nothing. When work asked me to put an authentication app on my phone so I could sign in using their new authentication scheme, I said, "No, I'm not putting any work app on my private phone. Hard no. Give me something else." So they gave me a little USB thingy to use instead.

If I lose my phone, I lose my contacts (but my carrier has a copy of those), my text history (but maybe my carrier has those too?), and any photos that I haven't copied off. That's it.
Lz_xor
here is the bug report...

https://hackerone.com/reports/1439026
Not that it matters much. Given how widespread Omicron was, even the most reluctant anti-vax got a natural vaccine by getting infected by this mild variant.
We use Swift on the server at Steamship. Our Swift project is a federated database for NLP data (query, training, inference, embeddings — the whole bit)

I assume folks are familiar with the downsides of Swift on Linux so I’ll focus on what we like about it:

- Fantastic type system

- Good language extensibility (we use Swift to build ourselves a framework to develop Steamship more easily)

- Good LLVM extensibility

- Mostly performant

- Compiled

All in all, we're very happy with the choice. My biggest gripe is slow build & test times in GitHub actions.

If Swift developers are out there and wanting to dig into more systems-style development, I'm happy to chat.
Labor. And the chance to "find" a lot more problems.
Me personally: no.

Before Covid, I had an excellent setup to train developers using pair programming and working closely together for months.

Now, training is impossible. I cannot train a junior dev remotely, and the job is remote.
Is it Sally Struthers? You can become a Back End or Front End developer! Or, earn your degree! You can major in safe cracking or gun repair!
My previous team had zero problem onboarding people remotely. The steps are extremely simple:

1. Have a collaborative culture. This is difficult at some places. But an environment where people are free to spin up zoom meetings and ask questions goes a long way. RTFM culture is the worst. Yes there are devs who don't bother reading the docs, but I find they often don't know how or where to look.

2. We had watercoolers in the afternoon. People could just chat. It may seem like a hugely ineffective process BUT... about 30%-40% of the time it would be about work. Knowledge would be distributed to multiple people, social bonds would form, and blockers would often be resolved. This led to high trust teams with multiple SMEs some of whom were "JR" devs.

3. README or wiki. Currently working at a FAANG company and several repos have no README. Wiki's are out of date. Knowledge is fragmented. I don't blame other devs, but it's kind of insane how much technical debt there is.
Even in a senior only org, it is a constant hamster wheel of training people with the current rates of turnover. One of the few long haulers is rapidly burning out supporting everyone else on the team who is green.
Social momentum. As correctly identified elsewhere, the simmering, proximal tech hate for Gates transmuted into a wide array of distal manifestations. Hate towards Gates gets re-legitimized to fit the needs of new interests.
This. I hated flash sites, but it gave non-technical people a chance to be creative. Designers especially loved it, though they often used it for wrong purposes (web pages) too.

But good luck teaching them how to make that tetris clone in React nowadays...
What’s the difference between ignoring bitcoin sent to you vs never letting the balance in an ethereum address get below coins you refuse?

Also if you wanted couldn’t you create a transaction that burns an amount equal to the tainted coins, that includes a message stating your intention?

This seems like a non issue to me.
Thanks so much.

And short answer - Yes.

My guess is it's a matter of 'when' I have to deal with this. I've had the domain for a while, and this is something I've wanted to build for such a long time. Things fell into place when I was able to build a Swift SDK for Fastly's platform back in January this year. The stubborn engineer in me went ahead and used the domain anyway and launched what you see today.
> I travel by bicycle or motorcycle, so space and weight come at a huge premium.

sure, but being protected from losing your digital prowess comes at a high utility per weight ratio.

> And of course my bank only lets me pair one phone per account.

that's a bummer. I can pair several. just need to scan some qr code.
The state of South Africa, 28ish years post-apartheid
The version number increments by 1 every 6 months. What is so nightmarish about that?
I was not making an argument in front of courts, I was stating why many Americans may find this action distasteful.

As far as I can tell, the executive branch was not mandated to delete anyone who contribted to/was a "member" of the github tornado dev group.
The beauty is in the simplicity. `http.Handler` is all about what is needed to handle HTTP and nothing else. It doesn't intend to make things pretty, or safe, or anything really, except to express the minimum surface area required to interact with HTTP while abstracting the commonalities. Beyond that, as the article mentions, it's quite easy to abstract and implement your own sugar layer.
Yeah, I know a lot of people who have no interest in tech besides the salary. And it is so obvious in their resumes.
So the problem with these "good" examples is that they expose the end user to Errors, messages likely not written by you or your team and moreso not intended for general consumption - you need to be really careful about doing so because an unexpected error could expose lots of troubling things like credentials and general information about your system you'd rather not expose.

We've got a general rule of thumb never to expose the message of an Error to the end user.
You contradict yourself here.

> (A) Modern computers run on electricity [not ones and zeroes]

> (B) one could build a computer out almost anything that lends itself to both being on and off

You got it right in B, which is exactly the point when people say computers are just 1s and 0s. Computers are a mathematical concept, not just some electrical device, as you seem to claim in A. The fact that you can build a computer out of water or air pressure or Minecraft Redstone is exactly the point people are making when they say they're built up from 1s and 0s (not electricity, not silicon and copper, not Redstone).
This was true until 2017 when I became a C programmer.

They are fine until they need to scale and iterate quickly without downtime.
Huh, the Dribble thing is a good idea, I'll pass that suggestion on
St Helena changed to 5 digits nearly 7 years ago.
The choice is almost always there, but the overwhelming majority of people choose the cheap option. Seriously, for pretty much anything there's a cheap version and a more expensive, (usually) better quality version.
What is the benefit of hiring them? Mentorship takes time away from seniors and code needs a thorough review if not full refactoring.
In my old employer, "Ops" and "Security" still had role for managing fundamental components of the system. In AWS terms, that means deploying AWS accounts in the organization, automation for best practices and compliance detection, IAM roles, VPCs, etc.

Security and network teams also built custom terraform modules which the deve teams were forced to use that were guardrails. You didn't use aws_s3_bucket, you used custom_aws_s3_bucket that mandated certain fields and prerequisites. This was the compromise struck to allow devs otherwise to go ham in their own AWS accounts and self-manage their deploys, databases, and so on.
Well said.

Giving yourself the junior dev label just makes it easier for them to place you in an unwanted pile.
Trouble with java is that it does not scale up or down in terms of ram.

Minimum RAM for a sever doing something normal over tcp is measured in gigabytes.

Big servers > 16gb get difficult to manage at runtime.

You have to scale with more VMs.

You can write useful C servers that are very small, especially if you compile with musl. And run the same code for 1000kcc (not a typo)

When you have big arrays of memory storing everything as Objects/pointers gets messy and inefficient. But any big heap is hard to manage and keep response times consistently low.

My other gripe os that "write once run anyway" is no longer close to true, since Oracle.
Mac, Linux x64 and Windows 64 are your only sane options. If you look at the compile targets list for c or rust you can see write once run anywhere working on a lot more cpus. True, you might have Arch specific code but it works, and most Java does not port from Linux container to Windows for example.

A statically compiled Binary is often easier to move across systems, because a java app is rarely a single jar. It's usually >5gb of app specific jvm and libs and config files.
The Seven Pillars of Statistical Wisdom – Visualized
> If you don't like the comments, maybe you shouldn't post on HN.

Anyone can submit a blog post to HN, not just the blog author.
>my take on dealerships is that you just have to know the maintenance schedule for your vehicle

The schedule on my leased vehicle is stretched out further per oil change than a local garage suggests (15,000km vs 5,000km).
> In Ethereum you can't refuse the funds that someone sends you.

And in a Mimblewimble blockchain, you can stop someone from sending you coins in the first place, since the receiver needs to sign along with the sender (elaborated on in my other comment).
All the non-bot active user accounts
Yes, but there’s related prior art.

Firstly, Java requires the compiler can prove variables are initialized before first use, and there’s a precisely described, fairly restricted algorithm that must be able to do that.

Similarly, Rust can’t correctly accept all code without ownership issues, so it supports only a subset of such code (in this case, AFAIK, that set is defined by the compiler, and growing over time)

In both cases the language designers on purpose limited what programs are valid so that the compiler can enforce certain constraints, eradicating a class of bugs.

I wonder whether there’s a language that works similar for this kind of constraints.

C++ destructors can do it for simple things such as “you must close this file before returning”, but that’s because the compiler will insert the call where needed.

Enforcing “you must call f before you ever call g” also is doable in simple cases: have f return a value of a type that must be passed to g or an object foo on which one g is implemented as a member: foo.g().

I’m not aware of any language that allows for more complex state transitions, though.

Edit: I think Rust can do (¿most of?) this by having a function take ownership of an object passed in, thus preventing further calls to it, and returning a new object on which only the then permissible calls can be made. I’m not sure one can require that to end with a ‘stopping state’ object, though.
Would be interesting to know the "moving away from Swift to Rust / Zig" story. My impression is that Swift not even in consideration in most projects with Rust / Zig.
And to sweeten wine, which survived into the Middle Ages as people soaking lumps in cheap wine to improve the flavor.

There’s a plausible theory that tomatoes were mistaken for poisonous due to lead dinner plates of that era.

With the possible exception of the counterfeit wine example, that’s all very ethically different from pumping it into the air.
So what you’re saying is that you discovered a vulnerability that leaked the private information of your users, said absolutely nothing for 6 months, then finally came clean, but only because you were forced to because people were selling data on the deep web.

Please take your “sorry” and shove it where the sun doesn’t shine. You don’t “take our privacy seriously”. This is utterly ridiculous and unacceptable, and in a fair world you would be punished heavily for it.

Edit: an earlier version of this comment criticised Twitter for not doing an investigation earlier to uncover the fact that a leak occurred. This accusation was based on me misreading the press report - see one of the child comments for details. I’ve removed that part of the comment.
I think the paper is more about the "big data problem" and the fact that there was very narrow confidence intervals on data that was off by a lot. So the survey technique itself was flawed and shouldn't be relied upon in the future.
Tracphone is the company you want for this sort of thing. A SIM costs $0.99 (requires unlocked phone of course) and you add $15 to the account to get 500 texts. (I think you can do this with cash at a place like Walmart.)

It is expensive if you need to keep the plan around, but Twitter doesn't seem to regularly send SMSes to the phone number, so you probably don't need to pay beyond the first month.
Speaking for myself, I am always open to hiring non-entry level juniors that demonstrate they can punch above their weight a bit. I have a philosophy of keeping the front end of our hiring funnel as wide as possible, my recruiting staff will screen almost anyone thats had at least one professional gig or an active github. And the folks that don't meet the experience expectations we have often still get a chance to show us what they can do if they check other boxes.

But the frank reality is that the definition of "junior" has changed significantly compared to 5-10 years ago. The education options for becoming a software engineer have broadened dramatically. As a result, the barrier to entry for simply submitting a resume to any given req is much lower. And while this is manifestly a great thing for inclusivity outcomes, it has disproportionately worse impact on the signal-to-noise ratio in the hiring funnel.

I think many orgs are still in the process of evaluating their risk tolerance for bringing on unproven talent. I do think _some_ risk is warranted, but its very easy over time to accidentally index too far in either direction.