skysight-inc/HackerNews huggingface dataset:
Also, if society does not shun bad actors, how would we not degenerate rapidly?

So bringing your park example to extreme: someone murders, is bad, but vilifying him would still be worse?

I'll leave you with a quote from Batman: "criminals thrive on the indulgence of society's understanding".
The "accepted definition of a recession"? Where are you getting this from?

I understand that some government/finance organizations in specific countries might have some sort of "definition" of the term recession, but in general parlance, "recession" is just when the economy is not doing well.

Some organizations do have indicators like "2 consecutive quarters of negative growth", but doesn't mean it's a universal "accepted definition".
Yes, I know (although they promoted it as a "systems language", but it was not really defined what that should mean in the beginning), but it is a restriction, you don't have in Rust. Basically, Rust can do everything Go can do, but not the other way around. That _might_ help to make a decision for a language.
Interesting. This looks like Custom Search Engines evolved into this?

I can't tell whether this is a neglected Google product that they were going to refresh but lost interest in, or something that is undergoing a breath of fresh air.

As you say, I was able to add a list of domains and get some pretty decent results from it. The UI makes me feel like Google are not interested in making it a truly successful product, though.
So the overspending and unmet expectations have finally hit? Not that some don't continue on, but it probably was too much money for too little return. And enough VC to spend for growth and esports being main-stream(like regularly on TV) that just didn't materialise.
I once interviewed for a startup during its "hyperspeed growth" period (can't remember what specific jargon they used but it was something like that). Got a good offer, handed in my notice, then the recruiter called again and said the offer was actually about 10% lower. I was a bit put out but I was relatively inexperienced in this negotiation stuff so accepted it. Then when the first day came, I was put into a team entirely different from the one I applied for - I applied for a Python ML engineering position, got put into a Java data engineering team. Naively I accepted this, hated it, managed to change teams (after ~4 months) to something more like my expertise, but eventually left the company because the management culture was generally toxic.

First impressions may not be everything, but I wish I'd gone with my gut on that one.
See also https://loige.co/where-to-go-to-learn-rust-in-2021/ (books, video courses, newsletters, podcasts, blogs, workshops, etc)
> the immune system [still] works pretty much as we expect from immunology 101

Shocker. Why did we have to learn this again? How were the policies that diverged from the immunology 101-based position justified? This should be our starting point and we should not base policies on the opposite conclusion without good evidence to the contrary.
Bold move, hadn't thought of that, thanks for sharing.
that's as full scale as you can get, I mean if NATO gets involved then it would get nuclear, and in this case there would be no one left to discuss the issue...
This.

Get into the office where you will be eligible for IT-related tasks instead of swinging a hammer.
People would say "I'm going to visit my brother in Federal Republic of Germany", or "I'm going to ... West Germany?". That doesn't sound right
And now the fourth largest economy in the world with a huge and extremely capable engineering base is committed to finding a way. Given that storage and other supporting tech for renewables has so far received hardly any serious funding at all, I think it's quite realistic to expect a success story there. Just consider what the many billions invested into fracking tech did to the US accessible gas reserves, and that wasn't thought to be technologically and economically feasible by most knowledgeable people either.

A fully renewable grid really is terra incognita, no one's done that before, of course there are a lot of open questions. But being a trailblazer might pay off handsomely if it does work out well, as others will want such a grid too.
No you got to have friends and acquaintances who have that problem.
With a side benefit of demotivating both staff so much they'll probably leave as well. Very clever!
Not only that, but crucially (quote from Wikipedia): "Over a period of several days, John Bradmore, the royal physician, treated the wound with honey to act as an antiseptic, crafted a tool to screw into the embedded arrowhead (bodkin point) and thus extract it without doing further damage, and flushed the wound with alcohol."

Despite the clever tool, if the wound had gotten infected, the then-prince would have probably died. So the knowledge of what to use to disinfect wounds already existed, but apparently wasn't undisputed until much later...
Thanks a bunch @hansvm, certainly enlightened by expert's view!
Can only see one ear. Identity confirmed
This is the right answer. Life's too short, especially when it's not your company.
The most important code linting rule: max-params
Let me ask you: What do you think this code does?

resizeImage(imagePath, 300, 200, true, true, 1)

It resizes image... but what exactly does it do? For the most part, we cannot tell without looking up the function definition.

Let's say you are reviewing a PR and it includes this change:

-resizeImage(imagePath, 300, 200, true, true, 1)
+resizeImage(imagePath, 300, 200, false, true, 1)

Can you confidently say what is the impact of this change? For the most part... no. You need to know what each positional argument does.

Let's say you know that the interface is:

function resizeImage(
imagePath: string,
width: number,
height: number,
upscale: boolean,
crop: boolean,
quality: number,
): Promise<Buffer>

But now a PR introduces a change to the parameter order (e.g. to make it consistent with other functions):

function resizeImage(
imagePath: string,
width: number,
height: number,
+ crop: boolean,
upscale: boolean,
- crop: boolean,
quality: number,
): Promise<Buffer>

How do you review this change? Sure, reviewing the interface diff is easy, but what about the dozens or hundreds of diffs that update function invocation?

-resizeImage(imagePath, 300, 200, true, false, 1)
+resizeImage(imagePath, 300, 200, false, true, 1)
resizeImage(imagePath, 300, 200, false, false, 1)
-resizeImage(imagePath, 300, 200, false, true, 1)
+resizeImage(imagePath, 300, 200, false, false, 1)
-resizeImage(imagePath, 300, 200, true, false, 1)
+resizeImage(imagePath, 300, 200, false, true, 1)

Hopefully the problem is self-explanatory: Positional arguments create a breading ground for hard and even impossible bugs to catch/debug/fix, esp. when code needs to be refactored. Fear not though as there is a better way.

Let's start from the start, but this time use a single-object parameter:

resizeImage({
imagePath,
width: 300,
height: 200,
upscale: true,
crop: false,
quality: 1,
})

Can you tell what is the intention behind this code? Yes, you can get a good sense, even if you are not familiar with the implementation.

Can you easily refactor the interface? Yes, linter will warn you if contract is not satisfied.

We end up with positional arguments because they feel the most natural to start with. However, as functions grow in scope, what started as a simple function with 1-2 arguments becomes an unreadable mess.

This is where [`max-params`](https://eslint.org/docs/latest/rules/max-params) comes to the rescue. Simply adding an ESLint rule that restricts having functions with more than X parameters ensures that your code remains legible and easy to refactor as your codebase scales.
German transport companies propose nation wide 69-euro monthly ticket
On Language Models for Creoles [pdf]
You can't fix the team, at least, not in the short term.

You say your boss is aware of the situation. Make sure this is formally documented.

Ultimately, if management are aware that this team doesn't function well but won't do anything about it, find another role.
Rolling out MS patches without a good testing period is a great way to suffer downtime in prod.

They somehow manage to ship catastrophically everything breaking shit extremely regularly.
Why not be the first to add an archive.
Also, apparently he died of entirely different causes (weakened by disentery and possible heatstroke).
"Look upon my works, ye mighty, and despair." - MBS
I thought the same thing. As a Node.js dev, I can quickly create a .mjs file and use a `module.export` to return a JavaScript object who contains the configuration. Thus, i can use template string and/or function to do what I want. I can even load JSON files natively
Great Game - also - how the fuck were they able to run in this weird VGA/SVGA mode? Something bitplanes, etc. - it wasn't your standard 320x200x256 colors. (Sorry, but back then in Bulgaria the literature on CGI/EGA/VGA was zero, and Ralph Brown's interrupt list only did that much)....
But that story with the arrow sounds exactly like the “you needed emergency surgery because you were going to die very soon”. So I don’t see how what you wrote is in disagrement with what GP wrote.
Playable online on archive.org: https://archive.org/details/msdos_Scorched_Earth_1991
Escrow is handled on the blockchain with a smart contract. There are no trusted third parties.

https://academy.particl.io/en/latest/in-depth/indepth_escrow...
Patching a service into a test environment for fast local development
With limited knowledge about the project and the team, here are my two cents: project management.

For example, ask your team to break down the tasks and provide a schedule for each task, and try to help them follow the schedule. If a task is taking way too long, ask them to break down it again. Remember to ask them to explain why they plan it like that.

Make sure you and your team have enough communication so you all know what need to do and what NOT to do. If your teammate is doing thing that is not in the scope, discuss with them and make the decision whether to support them or ask them to follow your request.

Rinse and repeat.
I've encountered this pretty-much every time that I've learned a new language or framework. I start out trying to use it the way I've used things before, and then I slowly learn how the people who wrote it expect me to work, and then things get a lot easier.
Our compiler stack is in Haskell so we initially started with Parsec (parser combinator library) and then eventually switched to Happy (parser generator that Haskell uses itself) since at first we didn't have a formal grammar defined so that made us write a lot of code for every little addition to the language (it's a simple declarative DSL, https://github.com/wasp-lang/wasp).

The problem we're now facing with Happy is that it doesn't really have support for error recovery. We're trying to implement LSP so recovery is important in order to have proper syntax highlighting and error reporting in an IDE.

Wondering how well ANTLR covers this, I was quite surprised to find out that Happy has so little support for it.
I get fought and ignored a lot of the time. Hence the back and forth on the PRs.
They'd rather show off some cool thing they saw on stackoverflow, having no idea what it does, than learn to do it properly.
Their training data is also part of their output. The training games produced last exceed the earlier games. So, yes, obviously the model can exceed its training data.

If you're trying to argue that the model can't be better than it is, i.e. the last training data it produces, then that's true but tautologically so. ML has conquered some domains, like Go or Chess or birdwatching, and is making progress in others - like programming. There is no reason to assume ML systems can't exceed human ability at programming or any other task.
It's always easier to drop everything and find better pastures when shit gets hard and/or bad.

But is it best for your long-term growth? If you're already in a difficult place mentally, it probably is best to leave. But if you're in a good place generally, and up for a challenge, you learn a ton more when you go from hard/bad to easy/good, and those skills are very sought after in the market place.

So if you can gain those skills, I'd go for doing just that. But again, that's not for everyone.
Certainly very ironic. But is this line of argument incorrect?

E.g. if I said "I don't believe in the Holy Book because in verse 7 it says that one cannot trust anything written in any books". Isn't that an analogous reasoning?

I think these examples/arguments are ultimately about exposing a liar-paradox statement, and when you can show such a statement you have proven that something isn't right.
Wouldn't be a huge loss to be honest.
Hardware acceleration in robotics news. EFPGAs bring a 10X advantage in power and cost, Introducing QODA: the platform for hybrid quantum-classical computing, A new programming language for hardware accelerators, AMD expects GPUs to need 600W of power in 2025, Now Comes The Hard Part, AMD: Software
easier than firing them atleast
Every one of the big tech companies have large Rust projects. Even Apple has open job listings for Rust devs.
So hard that literally every jigsaw maker on the planet do exactly this.

https://www.vistaprint.co.uk/photo-gifts/custom-jigsaw-puzzl...

https://www.ravensburger.us/photo-puzzles/index.html
I have to redo my kitchen and I am seriously thinking about replacing the cabinets with Harbor freight rolling tool cabinets
The only solution is to train your team. Put them in workshops and try to find out with what they are struggling the most. You cannot do it yourself at some point, the workload will be too much. There is no 10x developer outside of quick prototyping, especially if you are also managing people or projects and do software maintenance.

Very often work gets slow when goals are not precisely defined and developers have to improvise on the requirements. Micro-managing is bad but maybe their responsibilities need to be a bit stricter at first. With experience the railings can be removed.

Some suggest hire and fire, but if you don't put an effort into training you very likely will not find highly qualified developers or you have to pay extra.
The tldr is that the competitiveness of all pvp games suck all the fun out of it. And I very much agree with him. The games are toxic, not fun, almost like jobs. Currently you want to have fun with friends, coop pve is the way to go
Some people like the challenge of fixing dysfunctional teams like this. It’s the core difference between ‘leadership’ and ‘managing’. If that’s something that interests you, check out stuff like David Marquet’s book, but from personal experience also set some sort of timebox (3 months) on on when to reassess and see where things are at and if you want to continue.
I don’t agree with all these comments saying fire people or quit or whatever. These days I try give people the opportunity to develop, give honest feedback and if the results aren’t happening then reconsider things.

Is there anyone else in the organisation who you trust that could cover code reviews for a week? When you get back your boss will have two voices stating clearly that the team is not up to scratch.

Then your boss needs to start performance reviewing the engineers more closely with your input and make it very clear what behaviours need to change and see those behaviour changes or they need to reconsider their position.

Management is hard and your boss might not be up to the job(I only say this based on where the team is currently at), if your not seeing the results you want, then it’s time to reconsider your own position.
Life's too short: have an honest conversation with your boss about it.
If he's receptive => implement the changes you agree on,
if he's deflective => look for a new job
Thank you, I am being as positive as I can!
Work on building up the skills they are missing, whether its technical or soft skills? Being a lead sometimes means you have to prioritize team growth/output over your own for the medium to long term.

If you're in a startup that needs to produce a product yesterday then you may need to walk away as the company hired wrong, but if you are in charge of just a team in a company then its time to grow them.

When I have been in this situation the first step I take is to articulate where I want my team members to be, then deciding on the plan to get them there. It is an easy trap to fall into, to just complain about the current talent you have, but that will just build resentment and not create any improvement.

You should define what behaviors you want them to exhibit first. Then build a plan on how to get them from where they are, to where you want them to be, then start working with them to implement that plan.

Your 2 major possible impediments are going to be

1) having a boss who wants no change to the situation, in case you have been set up to fail and should look for a new job

2) an employee who accepted the job under certain terms that you are now changing. That is not their fault, but is one of those situations HR likes to describe as needing "managerial courage", where you either need to move the person on to their next role(most places this means shitcanning, but the moral choice is to tap your network and help them find a better suited role) or help them get with the program

The absolute worst choice is to just accept whats going on and let everyone deal with a shitty situation that breeds resentment until someone or everyone blows up and the whole team turns over.

Edit: I wrote that up somehow having glossed over your comment that you don't manage people and your boss isn't technical.

You have been set up to fail

If you have no control over people on a team but are responsible for their output you are the software equivalent of a supervisor at McDonalds. Either don't rock the boat and just collect a paycheck, or find a new job if it bothers you on a deep level. There is no solution to this situation. If your boss is not technical and already realized his deficiencies he would have empowered you. Being responsible for a team without the power to manage them means you are just a meat shield for the first time something goes wrong.
Sharing a list of books for PMs, sorted by categories
This advice can't used by everyone as there will be a smartest person in any room.
Why are you reviewing code that doesn’t work? At least set the basic expectation that the code has to work before you even look at it.

Other possibility since you’re obviously just sharing one side of the story is you yourself don’t understand their code.
So is there a stable torus planet dimension where the hole contains captured atmosphere through which you could fly using a conventional (non spacecraft) aeroplane?
Short term:

- Make sure only you can merge to main

- demand all PRs be small and focused so you can sort thru what they do while you're gone

- also demand descent test coverage

Medium term:

- build evidence proving the teams issues

- present to boss and hope they listen.

Long term:

Look for another job. From your other comments it sounds like their decisions have ensured failure.
Binary size very much depends on your settings. Rust does not optimise for a small 'hello world' by default, but it's very possible to get small binaries from it if that's a priority for you (for example, the default debug build neither optimizes for size nor strips debug information, as well as statically linking the standard library). Compile times are more sticky problem and most ways to improve it basically involve avoiding certain language features and libraries.
They don't lose anything, directly. It's more a reflection of what's going on with the preferred valuation.

https://www.businessinsider.com/fidelity-cuts-payments-finte...

A lot of comments here are not relevant, because Stripe grants RSUs not stock options.
Higher energy expenditure and lower physical activity in underweight adults
Wonder how FedNow's instant bank transfers will impact crypto; isn't "instant transfer" one of the advantages of i.e. bitcoin?

> FedNow payments will operate year-round for businesses and individuals. Since funds will transfer and settle instantly, all payments are final and cannot be reversed.

https://www.moderntreasury.com/learn/what-is-fednow
Over the years, trying to learn different languages/frameworks, failing most of the times and succeeding occasionally, I have found two things that help me:

1. Find an interesting project that suits the language/framework and keep the scope very minimal so I can complete it in 2 days (weekend). I can always learn more doing a second or third project. But I find that I can maintain my motivation when I see results and complete a project.

2. Restrict the number of new technologies for the project to maximum two (best if it is one). When there are many new things, I find that it can be exhausting and I give up after just a couple of hours. So for ex: When I initially learned React, I didn't know GraphQL, so even if I see a case where GraphQL might be the best fit, I will use REST API. This way I'm not stuck on all fronts.

To answer the first question, there is no single project I build to learn every language because that becomes boring for me. I try to build different projects every time.

For ex: When learning React, I built a HN reader, Foreign exchange meme reaction, and an app where I can see the time of all my teammates spread across the globe (all completed and live). When learning ReactNative, I built a small Twitter clone (haven't published it).
So far I’ve not seen any discussion here of the role of “kaizen boxes” in kanban (production card) pull manufacturing.

They’re a simple way to control batch size and hence limit work in progress to just what’s needed.

Rather simplified that is, if you can see the kanban on the factory floor go and get a matching box.

Make exactly the number of parts needed to fill every slot in the box. No more, no less.

Then place the box over the kanban. Don’t make anything of this type again until someone has removed the box and you next see the kanban again.

That can be expanded so that the tools needed to make the part are kept with the empty part container reducing the need to search for them when required.
They gave a very nice keynote on this year's Libre Planet. I'll see if I can find the link to the recorded talk.
> Sounds interesting, would you mind to expand / link some site that goes into details?

I think that the comment was ironic, to show a parallel with how coal waste is "utilized"
I was very confused until I realized you meant the boundary of a circle, not a filled circle.
No, the GGP is making the point that games designed for competitive multiplayer are not fun. Skill was always required. But fun is something the industry has forgotten how to do.
Thanks @njgroene, will try to improve the UI asap! I agree, most users might only need brushes. Great feedback, helps prioritize important aspects!
> erowid

Cool.
A couple of notes from my own history...

When you are expert on a topic, try to convey your comfort with the topic by entertaining questions from others. This is the most honest form of bragging. Some people say "learn how to sell yourself" but I think this is more nuanced.

Start learning SQL. Don't be afraid. Don't wait. It's a seed worth planting early.

Be kind, but also be firm. When someone is in a role that demands way more than their skill/experience, it is crippling. You have to speak up. It is worth learning how to be kind as well as diplomatic when you make your case.

The developers that are hard to replace are the ones who leave a build systems anyone can use/maintain. Cryptic codebases rarely hide a bunch of value; more like a bunch of bugs.
Maybe because the CIFS/SMB clients for Linux are so good, it makes little sense to do it the other way 'round?
That may make recovery much more tractable depending on the glue used. The cardboard itself is likely not going to pose a big challenge.