skysight-inc/HackerNews huggingface dataset:
Godot is really great, and the GDScript is something you don't really need to "learn". It feels intuitive and easy enough to be productive from day one. The performance, compilation speed, binary build - very quick. If was I writing a "game engine" that probably the system I would've come up with. The GUI feels flawless, responsive, very easy to work with. Online/offline help/documentation
is top notch.

Would I use it if I am serious about gamedev as a job? Probably not. Version 4 is supposed to bring a lot of improvements and this is awesome. I am not sure I would invest into building a product in version 3 (as it will be deprecated if not by its team then by the plugin makers). Version 4 is not ready yet and specifically mentions to have "tons of bugs" once it's out. As a hobby game developer this is an truly great product to work with. I started with a few 2d tutorials and probably after a week felt really productive. Also it feels like 1st class citizen on Linux (tbh Ubuntu also made great progress here).

The only really thing missing for me - in order to use my C++ simulation engine I need to re-compile C++ Godot sources along with my code? A bit too much for me at this stage. But didn't investigate it enough if there is an easier solution (version 4 is supposed to give more options). Using C# is as an option too. But they mention C# in terms of "support" is "secondary" whatever this means - without more experience it is hard to understand the implications.

Unity is too mature and skills are there if you need to hire or outsource. Mobile publishers, for example (from what I've seen) only accept unity games. You can buy great plugins/assets for reasonable amount of money. Obviously with the money they have it is the product you want to base your business on if you develop professionally. If anything Unity should be compared to Unreal engine, not Godot from the perspective of developing professionally.

Anyways it is really great to see an OSS product that is so close to the mature big commercial products that people have these discussions, run benchmarks and seriously consider switching to Godot. The quality of effort and skill I've seen people put into Godot development (and its plugins) is something unreal and too awesome be true. Go Go Godot!!!
Mixers are silly. I explain why.

A good money laundering scheme replaces the source of money with plausible legal source.

Mixing is smurfing in traditional money laundering terminology. Smurfing is illegal.

In the US bitcoin mixers are classified as money transmitters by the Financial Crimes Enforcement Network (FinCEN). Therefore, they must register with FinCEN and apply for a state-by-state license to operate.

Anyone who puts crypto trough mixers, creates cryptocurrency that can be identified as laundered money. Financial crime units in police all over the world can track and follow public ledgers, detect mixing and tag crypto coming out. You may get rid of the source of the money, but you get a label "laundered money" instead.

That makes it harder to use and transfer into the real world business that must follow money laundering rules and regulations and accounting practices, at least in larger sums.

If try to transfer it into currency, the exchange may lock the money and you have to show up with documentation proving the source of money to proceed. Alternatively coins may be confiscated just because evidence of smurfing. All that is needed is a new policy or some interpol/FBI/etc. database that tags suspect flows and dresses.
Infinite loops are a pretty common bug in my experience.

(Same for the recursive equivalent.)
I loved my experience with Dhall from the PureScript community. It prompted me to learn a lot more and I built some small libraries too. My experience was mostly positive. Supporting Unicode is the cherry on top.

Of all my gripes, only two still stick in my mind:
• No JavaScript implementation; I want to be able to use it more places, but I always end up having to convert it to JSON to use it
• the built-in formatter is way too aggressive; I'm fond of the never-contract-only-expand formatters that don't pressure me to collapse things I don't want and the way it is isn’t to optimize Git diffs where conflicts can arise.
>Their training data is also part of their output.

More deflection and going off point.

>is making progress in others - like programming

I already explained that programming is not amenable to the approach that allowed alphago to learn from the games it played against itself.

This is already getting pointless and tedious, should in the future know better than to respond to people that are obviously in the "scale is all you need" nonsense camp, nothing meaningful comes out of it.
this is like setting up a one box kubernetes... like... why?

if you arent a distributed system, why do you even need a multi node messaging system?

there are way better solutions for single node.
Giving the amount of the territory already polluted with unexploded ordinance in Ukraine i imagine in near future Roomba tanks wondering around "cleaning" the fields/etc.
Another comment mentions open source projects, open communities like that. There's some OS projects that use Gitter, which has search engine indexable chat history which ended up being quite useful.

I'm in a big Go Slack community and it's not indexed, which is a shame because there's a lot of really good info there.
> but I am only lead on the project, I don't manage people.

I think thats the main problem. They, the team - and probably you, as you are part of the team - need management.

Clear goals.
Intensive training.
Clear modus operandi.
Clear consequences (pos/neg).

Additional you as a team lead see your real "Handlungsspielraum". As a not manager you might not be able to fire them, but you can define what to do, what not to do and how to do it.

As the old way of doing things did not work, over your vacation try something new. A new way of doing things. And then go on vacation and do t check your work email.
I work at a Big Tech and I’d agree that the development speed is slow. However, I’d disagree with the characterisation that figuring out things like guarantees, capacity etc. are not “actual engineering work”.

My parents are chemical engineers and the work they do seems fundamentally pretty similar to Software Engineering at Big Tech (with different inputs and outputs and constraints), in that it’s less about getting any individual thing done, and more about getting many people to agree to a set of tradeoffs and implementation. Also, the scope for ground up work is pretty much non-existent and it’s a lot more about gluing together existing components with well known tradeoffs and tested characteristics.

Cross-team communication cost and latency can always be improved, but I think some slowness is unavoidable due to the possible impact that changes have.

There are pockets within Big Tech, which work on less critical things and they often have a much more startup mentality and approach to development. However, it’s still difficult for these teams to fully extricate themselves from the overhead imposed by the systems of other teams, since those systems are generally designed for bigger, more important and more critical systems.
> The only thing is needed to run the config-generation process in a sandbox and restrict how long it can run.

That's a very brittle restriction at best, and if implemented strictly on time, it's a very flaky on as well.
No PRs at all while you're away. No new code. Not so much as a spelling tweak.

Get them to make a branch each, and work through the whole thing line-by-line, documenting what they think is going on. Ideally, get them to work on each other's code. Given what you've said about their coding style and techniques, there ought to be plenty for them to figure out.

You sound like you're due a cleaning of the stables that'd give Hercules the fear, and you must play the role of Eurystheus.
Jury finds former CIA programmer guilty of leaking CIA hacking materials
Do you have or know a reference implementation you can share?
For the record, when I was an SRE at Google, most people I talked to hated BCL with a passion.
Cultural change - you need to introduce a engineering culture, which happens to appear when people discuss a projects internal in peaceful code-reviews, contract-first (not into too much depth). You need to encourage a culture of engineering conversations, which also means that you need to kick everyone politicizing those conversation from the conversation. Project leads, scrum masters, etc. are out of the door for this.

They need to loose the fear of talking about the techstack with one another, which also means that somebody has to embarass themselves publicly and repeatetly to take that fear. Code-review your own repository first and talk openly about your mistakes. Remove the "smartest man in the building" dick measuring contest. Make it a habbit, that everyones code repository can be "visited" by the whole team. Make those visits constructive and something people will look forward too and even collect "large scale problems" for.

Actually manage this instead of just managing.

Also if your projects grind, do not expect smart people. Grind turns every great hire into an idiot, which then again turns every project into grind.
How do you keep track of them? Do you have some grading system implemented?
Project Euler !
Over 80% senior job listings are formally contracts around here. It's a popular method of tax optimisation.
It sounds like a tough problem that you are not going to resolve before you leave.

First realise that there won't be a lot to do when you get back. They are not that quick as you say.

Second discuss with the team the problem: If you need to correct all their work when you get back the project will get delayed and hell will be paid/management will be displeased (depending on management culture). So you expect them to do minimale code changes and spend extra time testing. In your absence review each others code changes so you won't have to spend too much time approving when you get back. Empower them.

Third, but long term: If you are the most competent person in the room look for another.
>> In my estimation, esports ultimately resulted in barbaric desecration of formerly-enjoyable multiplayer experiences

> All of that just because my Dota skills are hobbyist level. And apparently, that's not acceptable to the online community anymore.

In my view, the problem here is that somehow the expectation has come to be that you play your multiplayer games with strangers. (This also causes other problems such as invasive anti-cheating software.)

I see very little benefit and quite a lot of damage resulting from this idea. Who cares about playing with strangers?
I was there. Noah wasn’t screwed over.
Why would they? It's just another build target to them, most of the engineering on this is done elsewhere. Worst case new hardware will ship peripherals that aren't supported well.
I'm not really saying COVID caused it. I'm saying in early 2020 institutional trust was already so slow that every newspaper and government department on earth could have said "the sky is blue" and a lot of people would have said "fuck you no it's not" by default.
> Configuration is opaque. Undebuggable. Unmaintainable. By its very nature. No matter what "language" you use for it.

What makes you think so? How do you define configuration?

I mean, in the extreme case you can see Python as a configuration language for the behaviour of the Python interpreter. Does that make Python a configuration language? Where do you draw the line?
> Does intentional feeding mean you’re pretending to be an amateur when you’re not an amateur, or what?

No, but there is a term for that too, "smurfing".
It's an interesting question... In my experience at a number of companies / assignments, Slack made its way into the business through "the back door", so to speak; development teams started using it without prior business approval - in a lot of companies, the use of unmonitored chat services was a no-no, so a lot of people were stuck on e-mail or a Microsoft project. But through "grassroots" movements, Slack was shimmied into these companies and took off, until the management was convinced to start paying for it.

TL;DR I strongly believe Slack became popular through their users bending/breaking some rules.

I also believe that the users have the rights to archive and republish their chat messages as they please. I don't believe a service that archives messages will cause too much overhead to Slack either. They may start charging for API access though, which is fair.
> Despite benevolent anthropomorphism, robots aren't much loved by humans.

That brings to mind the hitchBOT [1] experiment from 2013 to 2015. It did well - helped by media attention - in parts of Europe and Canada, but later came to grief in Philadelphia [2].

[1] https://en.wikipedia.org/wiki/HitchBOT

[2] HN comment thread on HitchBOT destroyed in Philadelphia, ending U.S. tour

https://news.ycombinator.com/item?id=9990881
> I'm sure there are many thoughts going through your mind regarding the team and perhaps my lack of managment skills but I am only lead on the project, I don't manage people.

If you're lead on the project you do manage people. It might not be in your job description but that's part of seniority. And if you want the projects you work on to be delivered you're going to have to step up and be that leader.

I've managed a copy paster successfully before. I set clear tickets with success criteria so it was obvious when their copy & paste didn't work. And as it was their ticket, assigned to them it was their responsibility to make it work. When enough of those built up they got the message and we wrote up a performance improvement plan. I mentored them through solving a couple. Then they started to do it. Enough to keep their job.

I've managed and worked with mavericks before. I have never found a successful strategy. The worst quit within 2 weeks because their new and unasked for contributions (e.g. rewriting a system unrelated to the project because "they could do it better") get called out quickly and stopped. The others burn me out.
> is it better for your long term growth to work with colleagues who can teach you new skills, or to try to wrangle a dysfunctional team?

Good point, although I'd consider "wrangle a dysfunctional team" as a skill, granted the team is only dysfunctional because of good management, not if they are inherently bad programmers, too big egos or whatever.

> IMO it depends on what you want to learn

Yeah, that's a good point. That nuance in my comment was missing to thanks for adding that.
Similarly to others here, I turned down an offer after they reduced it by 10% apropos of nothing, no negotiation, nothing. Red flag, if they’re like that so early on what are they going to be like 6 months into the hire.
@jenthoven respect to the hustlers kapwing.com! Thank you!
> The only rational use for a doctor back then was if you needed emergency surgery because you were going to die very soon. It was a situation that they could only make better.

Didn't you go for a barber for these kinds of problems anyway? Or later on, to a surgeon, who was very much not a doctor.
No, issuing regulation against drugs on their own territory is not a "war".

But deploying Royal Navy to acquire foreign territory for trade is the "war".
One thing I haven’t seen suggested elsewhere, at least from a quick scan through, is that you need to get more help from your boss. Your coworkers need to improve and your manager needs to help you with that by holding your coworkers accountable and dealing with them if they don’t improve. You can help define what “improve” looks like but without the authority to fire someone who doesn’t make it there’s no incentive to improve.

If your boss doesn’t want to help try talking to their boss, and so on. Presumably someone somewhere wants this business to succeed and can be convinced to care.

If that doesn’t work it might be time to find a new job.
Nah, you sort out free spirits and free thinkers and leave behind cooperate bedrock bureacrat coders. But then again, this is the reason why we have startup culture, cause this works so well, the grinders have to pay to get innovation externally.
(article author here)

Zstandard is good, no doubt. I didn't include compressor with entropy compression, except gzip which I added as a reference point for the ratios. After all I know it intimately after porting it to Go.

In overall terms, it does have an unavoidable bigger cost both for compression and decompression. So to have the smallest possible impact we have chosen not to go that direction (yet).

We might add it as a lifecycle option, where it compresses to zstd when the object reaches a certain age.

Furthermore the initial implementation was Snappy, so switching to S2 could be done seamless without requiring different decompressors and keep the implementation simple.

After all, the most effective way would be for the uploaded data to be compressed. The on-server compression is to catch the cases and compress them "reasonably" without taking too many resources.
> Really, you need to be willing to do all the things you hate other people doing...

This is why I am a firm believer that marketeers are a different breed of people altogether. Marketeers, recruiters, managers, sales, etc.

I mean software developers are weird, but THESE people, yikes. (this message is tongue in cheek)
In 3) s/arbitrage/competition, and apparently it is not only the electricity, but also the capital cost of the mining gear that you have to take into account.
Who does manage the people? Have you spoken with them, yet?
> The worst quit within 2 weeks

> The others burn me out

It sounds like "the worst" wasn't actually the worst, "the others" were the worst, as they actually impacted others in a more significant way.
> you need to be willing to do all the things you hate other people doing...

This is worth remembering. Always hated receiving cold emails.

edit: grammar
Next.js Adventures: How Some YouTube Videos Screwed My Performance Scores
This short case study is evidence that Next.Js is an “SEO-friendly” framework but not “SEO-ready.”

We, as web developers, have plenty of room to screw things, so we must be careful...
> So the knowledge of what to use to disinfect wounds already existed, but apparently wasn't undisputed until much later...

Not sure he had the right theory, though? He might have used honey 'by accident'?
And precisely none of those things, even in aggregate, support whatever semblance of a point you're attempting to make. Maybe you ain't in the best of positions to be lecturing others about shitposting, eh bud?
Planning a similar system for the house we'll be completing on in the next few months.

Since we'll be renovating/refreshing the whole house I'll have the opportunity to do stuff I won't be able to do later without much more disruption.
This feels like a good effort at making a jigsaw puzzle which is optimally simple to complete - although I think each piece is identical which may increase complexity.
They're obviously not talking about specific versions, but the heritage of the protocols.
Essentially means to play poorly on purpose, with the intent on making the opposing team stronger, or to give them a strategic advantage against your team. People do this to ruin games for whatever reason, it's a phenomena which persists throughout many multiplayer games online.
Ask HN: How to have an academic career after working in industry?
Let's say I'm a research engineer at a startup doing mostly machine learning for science & engineering applications. I joined right after my PhD in a natural science. I'm not keen on moving around for postdoc positions so this seemed like a good option.

I am satisfied with the work but I'm an idealist and my long-term dream is still a faculty position at a university.

1. Did I throw a wrench into that by choosing an industry gig over a postdoc?
2. Are there any (recent) examples of research engineers transitioning into a tenured position?
3. What should I optimize for in my current position to better my odds of achieving that?

(I'm EU based & working for a US company in case it matters.)
Sure, but at that point you're simply discussing Wikipedia's quality control system, which may be an interesting discussion, but has nothing to do with search engines per se.

Considering that Wikipedia has become a pillar of most scientific work (imagine writing a math or computer science paper without Wikipedia – utterly unthinkable), it's safe to say that knowledgeable people have collectively decided that its quality control mechanisms are "good enough", or at least better than those of any other resource of comparable depth and breadth.

And that puts Wikipedia's link pool leaps and bounds ahead of whatever dark magic current search engines are using, which mostly seems to be "funnel the entire web through some (easily gamed) heuristic".
Loved Scorched Earth. Had this fun bug/feature related to the weapons market. Between rounds you used your earnings to buy more weapons for the next round. There was an option to make it a "free market" which meant that the prices would get jacked on the weapons that you bought most often. But - and I didn't know this at the time - the price of an item was represented as a signed int so if you jacked the price high enough (which didn't take long) the price would flip over to a very high magnitude negative number and they'd literally pay you to take the nukes/MIRVs/dirt-bombs/napalm off their hands. Good times.
I think they came as examples with the BASIC interpreter? I recall having to run them from some sort of editor.
Yes, but nonetheless that's the official rule for German.
Are electric car subsidies based on them being manufactured from the ground up in the US?
Oh cool a vuejs Static Site Generator.
It's still extremely expensive, slow and challenging to sell pre-IPO shares even in a major stock that has a lot of active liquidity.
That video is great. Now I want to setup my own Ceph cluster.
HD has a dual-sided compartment case with transparent lids. One side can be used to store instruments/tools in PE foam (after removing the dividers with flush cutters), leaving the other side for small parts. 10 x 12 x 1.5 inches per side. https://www.homedepot.com/p/Husky-34-Compartment-Plastic-Dou...
… take me through this? Is it evaluating through NSObject keypaths? I’m a noob and just curious.
One game I wasted my school years with was XKobo (http://zkobo.online.fr/xkobo.html). So simple, yet so addictive.
>>Second layers act as a reminder that the original networks cannot scale, and need a second network on top of the network to operate. This is an admission of failure.

That is not argument against cryptocurrency. It is just a recognition that the first implementations had shortcomings that could be improved upon.

The internet did not emerge in the 1970s/80s with the functionality it has now.

>>Nope, I would love for a decentralized system to emerge, I’ve been an advocate of decentralization for 20 years. But crypto ain’t it. It’s highly centralized, and it has a propensity for inequality that makes capitalist economies look like anarchist communes.

I don't buy it. A truly decentralized system cannot be censored. It enables exactly the kind of free-for-all that the author criticized it for back in 2011. [1]

The author wants centralized regulatory gatekeeping and control, without calling it that. This is the case with most of the avowed opponents (as opposed to mere skeptics) of cryptocurrency.

[1] https://twitter.com/technollama/status/83187937738625024
Imagine a NSA Codebase, having to hold a million hacks for a million different moving targets, they would grind to a total halt. Implementation variety is defense by burdening the attacker with maintenance for a million little ecosystems.