skysight-inc/HackerNews huggingface dataset:
@brk Sorry for the superrr late response, but please give it a try!
"Dhall... that you can think of as: JSON + functions + types + imports".
Is this Typescript?
>All of these bikes are designed and made in China.

Jeez, and why is that? Here's a wild idea, instead of offshoring out entire manufacturing sector to sweatshop countries without human rights and environmental regulations, just to drive down cost and increase shareholder value, we instead invest in domestic manufacturing for critical sectors such as transportation (yes bikes are a means of transportation and the best one for cities at that). Or, instead of the government aiding Exxon or BP they aid local E-Bike manufacturing.

Several European countries have E-Bike companies with domestic manufacturing. So it's possible to do in the west.
almost as secret as canyon.mid
I wonder what other languages you have experience with. C++ is obviously not one of them.
Handel became a subject of Britain in 1727 by an act of parliament[1]. The text of the act itself[2] clearly referred to him as "George Frederic Handel" with no umlauts. Considering he spent the rest of his life in Britain as a naturalised British citizen there's little reason on insisting to use the umlaut for his name.

[1] https://archives.parliament.uk/collections/getrecord/GB61_HL...

[2] https://digitalarchive.parliament.uk/HL/PO/PB/1/1726/13G1n3
I too have an idea list - I suppose the idea you choose is the idea that you're thinking about the most
Rust actually supports most OOP features, with the main exception of implementation inheritance. And implementation inheritance is a nasty footgun in large-scale software systems (search around for: "fragile base class problem"), in a way that just doesn't apply to simple composition and pure interfaces (traits). So it's hard to fault Rust for including the latter and not the former.
Wtf? Does intentional feeding mean you’re pretending to be an amateur when you’re not an amateur, or what?
it's in the name zenia is a form of https://en.wiktionary.org/wiki/Jevgenija commonly used around Russia

+ construction work

+ some language style signs

p.s. wonder if Russian is also frowned upon nowadays in west. It's pretty much taboo here in Eastern Europe.
You could add your own quotes to the tanks. My brother and I spent far too long adding one-liners from comic books and action movies to the file.
I’ve always wondered why Rust creates a unique id per atom and keeps track of type information in a hashmap using that unique id as key (instead of storing the type information within the atoms themselves). I guess it is to keep things flat, or reuse the same structure for different passes.

Other approaches like the nanopass approach creates different structs for each pass: https://legacy.cs.indiana.edu/~dyb/pubs/nano-jfp.pdf
Pile Driver!

Years of my life sunk into Scorched Tanks. As an Amiga child, I have no MS DOS nostalgia. But I am pretty sure Scorched Tanks was a decent alternative.
Worms is just a mod of Scorched Earth.
He himself recognized when circumstances changed such that speed was less important.

http://www.grandroundsjournal.com/articles/gr049006
> However, I don't know anyone at T-Mobile or similar, so I've been carrying the idea around for a long time.

You could always try and get a job at one of these business for a year, with the primary goal of building connections.
The consensus strategy you need to follow or get flamed for being bad.
A new dominant Omicron strain in the U.S. is driving up Cases – and Reinfections
This sounds to me like the journey into functional programming. I've experienced the same thing myself.
Ok, unflagged!
Walk away
That’s only tangentially similar to Inferno, and completely unlike Plan9.

Even for Inferno the idea was to make the system flexible, Android is everything but.
I don’t think there would be any cause for Slack to complain for at least paid accounts. I glanced through the relevant terms, and there’s really only one even vaguely relevant topic, largely around competing with Slack.

In their App Developer Policy <https://api.slack.com/developer-policy>:

> As part of good business practices, Applications and developers are prohibited from: Circumventing Slack’s intended limitations (including pricing, features and access structures). You may not use the Slack API to replicate or compete with core products or services offered by Slack

And in their API Terms of Service <https://slack.com/intl/en-au/terms-of-service/api>, which cites the app developer policy and then adds:

> Further, you will not: … (C) access our APIs or documentation in order to replicate or compete with the Services

If Slack spell out that there being no public mirror is an intended limitation, or if they offer a direct equivalent, then they could complain. And they could do for free accounts, which have a history limit that this would incidentally circumvent. But for paid accounts I don’t believe either of these are true, so if it were limited to working with paid accounts I’d say you’d be in the clear with Slack for now. Of course, you’re still subject to their caprice in changing their rules, implementing new features, or just booting you off their platform even without cause at their whim, and that’s a significant existential risk for building such a business.

But I don’t think Slack would be particularly likely to boot them off, given that any hostile action on their part would be akin to claiming some degree of ownership of the data. The data belongs to the customer, and they should be able to do whatever they want with it without hindrance. Of course, such reasoning as this is only reasoning. If they did cut off such API access, they’d hardly be the first large company to shut the portcullis to support their own interests against their customers’; Twitter, for example.
You have to remember that's pretty much par for the course for that age. One classic example is the "care" that was administered to George Washington, which likely also hastened his demise:

"Doctors then arrived and bled him four more times over the next eight hours, with a total blood loss of 40 percent. Washington also gargled with a mixture of molasses, vinegar and butter; he inhaled a steam of vinegar and hot water; and his throat also was swabbed with a salve and a preparation of dried beetles. An enema was also used."

(from https://constitutioncenter.org/blog/the-mysterious-death-of-...)
Do everything yourself to show them how things should be done.
IIUC, Dhall is pure and have no side effects
OCaml really messes with you if you try to prototype as you can’t have two modules that depend on one another. Rust is def. much better.
Me too!

It had a cheat code, so if you set the power to a certain amount it would shoot through the grass
If anyone would like to play a somewhat updated version of it right now then I highly recommend Atomic Tanks.

This can be installed on debian/ubuntu with a quick "sudo apt-get install atanks", but is available on windows and other platforms too.

(https://atanks.sourceforge.io/)
Wow, that's a really dark one! Never thought it could reproduce a piece of history, you made my day.
Just use Arc
You can write a custom stemming algorithm and load it as an extension library into Postgres, then use that with `CREATE TEXT SEARCH DICTIONARY` to create a custom dictionary. It's not as difficult as it sounds - you can use the default Snowball stemmer as a sample, and tweak it.
I think you have to set a good example of what you expect from everyone to do or assign some tasks to them and regularly do meetings to assess every progress that the team makes.
Oh god. I'm afraid to say this sounds kind of...hopeless. I don't think it's a lack of management ability on your end. It's that it sounds like they don't even have good intentions. If they had good intentions, you could at least work with them to improve their skills. But if they don't or have some ego issues, what can you do? That's not really in your power to fix.

Can you find new team members? And in the meantime, perhaps do more coding yourself?
Ha! That's funny. I hadn't thought of that.

I may be mistaken, but I think to be correct in that context, it would need a comma:

"I went about, learning Rust"
Separating children from parents is just horrible. The US should have made sure they were kept together when deported. I don't understand why Democrats didn't push for that, instead of using it as a wedge in a false open-borders-or-child-separation dichotomy.
The Alma Linux guys seemed happy to engage with the community, for example by coming on the Linux Unplugged podcast and discussing the (at the time) future governance structure of Alma. Rocky Linux rather agressively declined to come onto that same podcast iirc.
I really like Golang’s inference which is much dumber than Rust (left type = right type)
> Creating a new language and repeating the "billion dollar mistake" by including null (sailing under the brand name "nil" in Go) is just crazy.

You forgot pointers used to represent nullables.
Also a good D-lock with 18mm steel will help. Because e-bikes can carry more weight, a heavier lock is not a burden to carry around. Bolt cutters won't work on 18mm of steel, and a portable grinder will take too long.
I'd rather have cash in my bank account and work for a company that will suffer structural damage than see my hypothetical net worth go down 60%.
If it's an UI framework i do tic tac toe with the UI implemented as a 3x3 button grid with changing labels.

If it's server i usually do something related to the actual project though.
That would have been useful to point out in a comennt.

After determining what the inteview date was, I'd assumed that there was no further information.

HN doesn't permit editorialising titles, but you can submit a comment with your link submission. It won't be privileged (that is, has no special priority), but as the first comment on the post will tend to influence subsequent discussion.

The refusal to address monopoly status or mergers, and the interruption of the PR flak is notable. Thanks for pointing that out.
Your own what? Your own query? Sure; it's just a SPARQL query over the Wikidata data model. The documentation portal for the query service is at https://www.wikidata.org/wiki/Wikidata:SPARQL_query_service/... though you'd need some familiarity with Wikidata, its properties, etc. E.g. the "wdt:P856" in my query is the "official website" property on Wikidata: https://m.wikidata.org/wiki/Property:P856
I think it boils down to a vicious cycle. Institutions are worried about a loss of credibility and are as a result very unwilling to acknowledge where they have been wrong, changed their minds or about any uncertainties that still exist. As a result people get the wrong impression and highly overestimate the competence of those institutions, and the confidence that their solutions warrant. Which makes those institutions even more afraid of loosing credibility. Which lead to some very comical parallel realities, like the WHO not aknowleding that COVID was airborne till 2022
https://news.ycombinator.com/item?id=30939200

Or differently put, if you have absolutely unrealistic expectations and deferred any critical thinking to another party, you are putting said party in a very very difficult situation. And if they not just lack the backbone to tell you this, but start pretending to be that competent and certain to match your expectations, it can become very dangerous.
> The language has memory-safe concurrency (except for maps, which is weird)...

My understanding is you should operate the other way around. Things aren't safe for concurrent mutation unless it's explicitly documented as safe.

> So you can have parallelism without worrying too much about race conditions or leaks.

You might not worry, but I find these the two easiest classes of Go bug to find when entering new codebases ;).

Still, I agree Go is easier to get a web service up and running with.
Since you don't own the business but are an employee yourself you don't have to shoulder all responsibility for the business' bad decision.

If you can't fix things on your own, escalate the problem. Document and share with the team and upwards the consequences of your vacation:

1. You are not reachable during vacation
2. If they choose to deploy and break production, they need to firefight themselves
3. The team is not resilient since you're obviously the single point of failure.
I know it's cynical but having lived in rough areas I get a chuckle out of sheltered engineers designing these and not expecting teenagers to absolutely destroy them in the wild. The poor Estonians can't grok what it's like in East Palo Alto.
You can fiddle this option on your homeserver: https://matrix-org.github.io/synapse/latest/usage/configurat...

Or if you don’t have a homeserver, invite all your users to a space so you can see them there.

Identity servers are generally just for looking up user by email or phone number (although mxisd did intercept some endpoints to add a user directory before synapse exposed the option above).
Oh nice! I had no idea, I'll try it, thanks :)
https://en.m.wikipedia.org/wiki/Properties_of_water#Triple_p...
Tell your boss what everyone knows: This team sucks and it's the boss's fault for building a shitty team. This is a classic pattern, where you have a team in full dysfunction with a lead who is not empowered and a boss who is not aware.

It is not acceptable to divide the leadership that way. You either need the ability to hire/fire and fix that team, or you have to quit.
>I would say these versions did exceed their training data

Well, this is obviously incorrect because the training data included all the games it played against itself (good luck replicating that in the domain of programming though).

We were not talking about "exceeding human abilities in at least some domains", we were talking about whether ML (DL really) systems were able to "go beyond" their training data - but your deflection and going off point is noted.
How does task assignment work in the team. Does your manager assign tasks to individuals in the team, do you assign tasks or are you running a more agile style where the developers choose which task they'll work on next?

If it's either of the first two then you could always find them some tasks that they're more likely to get right and make sure they're the ones worked on while you're away.
Compromise a bit, give more detailed guidance than usual for a reduced number of tasks while you're away, accept that the result won't be up to your usual standards and might need to be revisited later. Can anyone else pop their head in to offer guidance while you're away even informally. While you're on vacation use the headspace to plan how to make things better for next year.
You should be transparent about what you do not appreciate (e.g. randomly copying code from unknown sources). About back and forth PR comments, just sit next to them (or call, if remote). I rarely leave a lot comments on pull requests, if the issues is not simple.

Also you should be upfront with the management about the quality of the developers.

In the end I suppose it's more about being afraid yourself of confrontation. There is absolutely no reasons to dread your work (pull request or anything else)
Cryptocurrency flowing into “mixers” hits an all-time high
Share your evidance-based expectations with your director/manager. If you surprise them with failure or delays that you knew were likely, it'll be your fault. On the other hand, if you deliver ahead of a previously-broadcast delay because you manage to improve on this situation, you'll be (rightly) recognized for effective leadership.

As for strategies to do that: consider (provisionally) lowering the overall code quality standard, as your team is clearly not up to yours. This is an important practical concession when working with average engineers -- otherwise you'll have an effective bus number of 1.
As an example, imagine you have $200k of crypto, held in custody at an exchange that has frozen withdrawals.
This seems pretty straight forward, reject the PR's with detailed responses until they are of acceptable quality. Doing so might slow momentum with the project in the short term but should overall make everything faster. Just be clear about WHY you are rejecting the PR's and the quality you expect.
what does that have to do with the restrictions? the logical corollary to your statement seems to be, if the body IS capable of natural immunity, then it is likely that it will work on the attenuated virus (provided it's not too attenuated, maybe)
An attacker dedicated enough to pull off such an attack will absolutely be dedicated enough to spend 15 minutes screen-scraping the portal.
"If you're the smartest person in the room, you're in the wrong room."
I'm doing as much coding as I can but the project management stuff takes time. I'm keeping the critical system coding for myself.

Can't find a new team, manager says this is it and no time/budget to get others.

You're right there is nothing I can do. I'm thinking of keeping the project locked down until I come back. They can still make feature branches in the mean time.
The Maverick is a bad actor. The copy-paster is a bad actor. The boss is a bad actor. Is it easier to turn this tide or get a better job?
Which also isn't "green" in any shape or form.
If I was in that situation I would take the time to plan out in as fine detail as possible a task list for each day for each person. There are several benefits to doing this:

- They know exactly what needs to be done and are expected to do, so even the Maverick is placed on a leash.

- You are probably going to return to a mess anyway, but this way you (and your boss) have the task lists to point to as evidence when reprimanding or even removing people from the team down the line.

- You're covering yourself if the project does get delayed. You did everything you could to help the team while you weren't there.

Your boss may not be technical, but if he has these task lists for each person and you sit down and go through them with him before you leave, he can do daily checks to keep them on track.

Finally, switch off and enjoy your vacation. There is nothing you can do while you are away and probably a lot you will have to do when you return, so throw yourself into the break and enjoy it as much as possible.
That's why I wrote "pressured" and not "succeeded". They tried heavily.

Gas isn't a transition to anything.
Give your subordinates clear and specific written instructions, eg: "Don't use x technique here, it is unnecessary.". You are the lead, part of your job is to overrule people sometimes.

If they ignore you, or fight with you, that is a different problem.

What this could be is a teaching moment, or series of them, depending on how cooperative or not the team members are.
It's almost always that I'm behind them at the checkout/cashier.

If they're struggling, card declined etc, they're probably already frustrated, they might turn to me to apologise, that's my cue; I'll just say, "hey, can I get that for you?“. I remember the first time, a guy about my age just buying food, his card was declined, he had a little bit of cash so the cashier was having him figure out what to leave behind so he had enough to cover it. I just asked if I could get it all for him and he just asked, "why?", looking puzzled, I just said "why not?", and something along the lines of "you can pass on the favour one day", he accepted.

Other times its that the place doesn't take cards and they need to get cash, I'll just say, they can add it to my bill and I'll get it, if they don't mind.

Sometimes people decline, but usually I'm pretty good at judging when people would appreciate it so it's rarely awkward.
I never played or properly followed Overwatch, but didn't it start with some type of on the fly changing team composition? And then from there it went to what I can understand a very rigid meta? Or am I thinking of some other Blizzard game was it HoTS?
So not that kind of tonal: <https://en.wikipedia.org/wiki/Tonal_system>
If you're looking for a new language in order to get a job, then I wouldn't be looking for either of these languages and look into something much more common like C++ given your background.

I see Rust as more for people in systems programming who want improvements over C, rather than a desktop developer looking to learn something new. There's a lot of hurdles that you only really appreciate if you've come from an unsafe/low-level background
> I am only lead on the project, I don't manage people.

responsibility without power

>My boss trusts my judgement

looks like classic "delegation", ie. the boss delegated responsibility while kept the power (you only fall for such "delegation" the first 5-10 years in the industry).

One can guess who is going to get ultimately blame assigned :)

>Is there a possible solution to this without adversely affecting the project?

With only 2 people it is actually much simpler to do their job for them. Just send them on a long trip - like some very important future architectural R&D without any need to commit anything in the near term. Doing very important architectural thing they also may get promoted so you wouldn't have to deal with their code :) Best course of action though - just leave this project or this company.
I can't (but I will) tell you how much Scorched Earth rocked in the early 1990's at uni. It was a winnable game for people who sucked at xpilot :) Thanks for the mammaries people ;)
Normally I'd start with the PR comments, since this can be improved the quickest (a month or so) with strong coaching, and will give your team better velocity.

But since your team consists solely of a maverick and a copy-paster, you're in trouble. Normally you'd fire the copy-paster and mentor the maverick (or fire him too if his ego is too big to handle).

Getting into a situation where you have to be the one to approve all PRs is a bad sign, because it shows that you have no trust in the team members. Regardless of the validity of your reasons, this is not good because you become a bottleneck.

Another option would be to look elsewhere.
Make a tag where code is before you go out of office, for emergency restore.

I'd make it clear that everyone is responsible that their own changes work, regardless of what came into the system before it, there are no excuses.

Forbid merge commits (because that's more complex than they can handle).

When a dev wants to submit their code, they have to rebase it first, tough luck, and they have to get it to work again, if anything breaks, their own stuff or what came before, it's their problem, they fix it before submitting.

All tests must pass before code is submitted.

If someone must drive standups while you're away, pick the least technically competent person for that job, because they will then spend some time not doing damage and you don't want the hotshot maverick setting the direction.

Go enjoy your holiday.

Go figure why I'm not in management ;)
Any ideas on how to add a type system so one can do julia style multiple dispatch

(define abs (Complex n) (* n (bar n)))

(define abs (Int n) (max n (- n)))
Hot Garbage
Is there a reason you can’t use EAP with unique usernames & passwords?
My hot take on this is that the colleges / universities want a certain share of their students to hail from wealthy and elite backgrounds. It just makes the schools more desirable, for people that want to make connections / break into that social circle. And they've probably calculated that these legacy admits donate back to the school, along with becoming more involved as they get adults - and start to plan for their own children.

Not saying that it's right - but power and prestige has always been informal selling point of attending elite colleges.

Also, I know this is just undergrad...but elite MBA programs are far worse. Basically just a 2-year social club for rich kids to travel, connect, and party around the world, while getting some education on the side.