skysight-inc/HackerNews huggingface dataset:
The "lottery" is just a method to have the aligned incentives and secure the network. Without the miners, there would be no Blockchain. Every user of the blockchain benefits from the work from the miners. So if you have a problem with miners, you have a problem with all those that depend on them. But if you want to complain about the consumption patterns of this group, you open yourself for criticism for your consumption patterns as well. As long as you are actually paying for the electricity and energy you are consuming, I am not going to be judging you if you prefer to use with gaming, or by driving an huge SUV or flying every weekend to Las Vegas.

Still, I am glad that we are moving away from it and adopting PoS. Not only the system is more efficient, it also removes from the perma-bears one more talking point.
My personal opinion of this is that you can have high and low level code written in the same language at the expense of requiring more skill from the programmer.

You can write a pure-functional RPN calculator in a handful of lines of D, you can also write D's entire implementation in D including the "low-level" aspects.

I also think the distinction between low and high level code in languages that are not built around some theoretically abstract model of execution (e.g. the lambda calculus) to be rather pointless and mostly useful only for making poor arguments.

I'm also sceptical of simplicity as an unqualified idea. I have read "simple" code with no abstractions that makes it extremely hard to read, I have read "simple" code that can be considered as such because the abstractions are actually abstractions: "Abstraction is the removal of irrelevant detail".
It feels heavy to me, because you're asking for a process gate to be put in front of something that is so trivial. It feels utterly unnecessary and demotivating. If I see a minor problem in the documentation and decide to correct it, now I have to go through an extra step of creating a JIRA ticket describing the minor problem I'm trying to solve, doing the correction, updating the JIRA ticket status, and possibly monitoring the ticket for future issues. It's. all. so. bureaucratic. And sadly it will probably lead me to thinking the fix is not worth my time.

Instead of trying to convince everyone that they should feel the way you do, maybe try to understand why others feel the way they do.
I never said that it wasn't corrupt, only asserted that it was very effective. Just like Israeli airport security - clearly ethnically discriminatory, but also very effective.
Hearing about this case, I'd say it's either prions (which is very scary), or major companies there don't really care about pollution effects...
I don't think 1password does either? Anyone know for sure? I think they give you a separate attachments folder, but any item loses its association to any attachment.
Right, but I feel we're having a miscommunication about the level of effort one should expend to recover the payloads; your mental model is that this:

sqlite3 -noheader -newline '' export.db "select data from files where filename = 'my-file.bin'" > my-file.bin

is more user friendly than:

unzip 1PasswordExport-ILESALYKVFDNJH3K24FEO3QRHM-20220611-100457.1pux files/my-file.bin
I meant it more in that "first-class" tends to mean "this is a thing that is represented in the language / type system".

Go has first-class functions, because you can make a `var fn func() string` field/variable/argument/etc that holds a reference to a func that returns a string.

Go does not have first-class types, because you can't reference or store a type directly. You can use reflection to pass a reflected thing representing a type, but not the type itself. Generics muddies this somewhat, but I'll argue that falls under "generics", not "first-class types". In contrast, Java has both generics and first-class types, because you can pass `SomeClass` itself as an argument.

---

Node.js arguably has first-class concurrency. It has async/await: you do not have concurrency without those keywords. If they exist, you have potential concurrency. If they do not, you do not. (there may be exceptions here for true thread use, and JS runtimes vary, but you get the idea)

Rust has async/await now, and also has Send/Sync, which gives it a very strong claim to "first-class concurrency".

Go's concurrency constructs have no representation in the type system. They're totally invisible. Channels and select are mostly used with concurrency, but they do not define concurrency, and can be (and are) used synchronously as well.

`go` is a keyword, but I don't see how that's any different than `new Thread(fn)`... except that the Thread has a better claim to first-class-ness, because it returns a value that represents the concurrently-executing thread. If you have a thread reference, you know that concurrency exists. The reverse is not true though.
With respect to "strut," they're part of the EWMH: https://specifications.freedesktop.org/wm-spec/wm-spec-1.3.h...
I do wonder if the real purpose of the 'ridiculous and demeaning puzzles' is more psychological assessment than skill testing in many or most cases.

Granted, there is the problem of academic cheating in CS so for people coming right out of college into the job market, so it's likely an acceptable filter for screening out people who haven't ever really written their own code from scratch, but otherwise. for people with proven track records in the industry?

Maybe the thinking is: "We've got this mess of a codebase, it's poorly documented, if it ever got out how bad it is we'd be very embarrassed, and we want compliant team players who won't shake up the boat or demand we overhaul the whole thing, as we care a lot more about revenue than code quality, and this thing does work, sort of, most of the time, and we sure don't want anyone writing memos about massive security holes to upper management... now, will you jump through these degrading hoops like a good little poodle or not?"
This sucks. While traveling across Europe McDonald's and Starbucks's bathrooms have been such a boon to us when we needed one in a pinch and there wasn't a paid for one near by. We've always bought something to thank them for the services but that they're there to use even if we didn't pay them is really, really nice. I can imagine they'd be a horror to clean if abused. I used to clean bathrooms, golf carts, and pick range balls in in high school for a local mid-priced golf range and it was the bathrooms that I always dreaded. They were always disgusting -- and you couldn't use them unless you paid to play nine holes or bought golf balls to hit. Imagine how bad a free toilet might be -- then again, every time I've had to use a Starbucks bathroom they've been immaculate -- likely because some poor employee had to keep them so.
Malls are generally dependent on anchor stores drawing traffic. And a lot of the historic anchor stores--in many cases department stores--have gone out of business or downsized. One pretty dead mall near me had a Penney's, a Sears, and a Macy's.
Can you explain why it’s necessary I need to write a ticket to update documentation?
I agree the best teams have been more “keep it simple and focus on making cool stuff” than being focused on trying random new frameworks. But Scrum is not a popular choice for keeping it simple because it comes with a lot of baggage.
On youtube there's an American guy called Hinkle dishing out pro Russian viewpoint, I mean even Trump was a Putin apologist and under the veneer he's probably still got a grudge against Zelensky for his 2nd impeachment so I expect a lot of his believers hold similar twisted views... I mean even if on the surface people agree Putler is evil, many probably view the inflation of oil prices and their diminishing buying power (and their economy...whatever that means) as being caused by the said WAR rather than too much money being printed in 2020-21 to prop up all those poor airlines etc etc
Renewables are the only way that Europe will be somewhat independent in terms of energy in the forseeable future (though hardly emissions free). The technology is already there, we've just been sitting on our asses for two decades instead of pursuing it aggressively.

The number of installed wind turbines in Germany has stagnated, for example. Output has increased, but that's because of repowering old installations. NIMBY rules and incredibly complex approval procedures prevent growth.

You'd think this would be all the motivation required to rapidly expand renewables. Evidently not, we'll just keep having the same conversation. Whatever.
In the area where I live, the schools are in easy walking distance. I never see kids walk or bike to school.
Thanks, you make a good point about folks who claim a lot of experience.

For me, "demeaning" does not have an emotional component in that I don't take this personally and that I don't feel much of an emotional "charge" around this... definitely nothing that is "directed" towards an organization like this.

And I made no claims about what tasks are "too lowly" for me to do, that's an orthogonal issue to the question at hand. I'll happily do simple, repetitive, potentially grueling tasks if necessary.

I'm thinking about our limited time and how this industry seems to have a unique approach to hiring. It's very challenging to apply to multiple jobs that all come with some form of code challenge and lengthy interviews, while also working full-time and taking care of a family. How do we increase the signal about where we are thinking of working?

Other folks in this thread have offered some great suggestions to this question that don't necessarily involve signing an NDA.
That is a fantastic analogy, it captures exactly the pros and cons and the context dependency of methodologies.
Japan is an ethnostate where people die in quiet desperation. You don’t see society’s ills because they’re deeply stigmatized and brutally repressed by law enforcement.

We can desire a better world than these two opposite poles.
> They seem good at predicting many important social outcomes, so they must be capturing something.

Is that 'something' a satisfactory control for genetic determinism? That seems to be what the comment was arguing, not 'nothing at all'
Zig Zag and Hiring
Nice blendshift cycling on the waterfall. Very cool to see that technique used in practice.
Scientists uncover new population of black holes
DNS servers _usually_ reply with information about a queried domain name or a host name. dig is a command-line tool that queries a given name server (or a preset one) for that information. For example `dig news.ycombinator.com` returns the IP address of HN, and `dig news.ycombinator.com @example.com` queries the example.com nameserver for that domain.

dns.toys runs a DNS server that dynamically returns answers such as times, currency information, etc (instead of domain name information) if you format your query right.

So for example, `dig mumbai.time @dns.toys` returns the time in Mumbai in a DNS TXT record instead of an IP address (or an NXDOMAIN response, saying the domain does not exists).

Play around with the `dig` command, it is an intuitive tool that you will eventually use if you are a CS or a related Freshman.
My reading of comments if that people seem to see two options:

* Scrum/Agile/Current-hot-buzzword

* PMs micromanaging via jira/whatever bug management

My experience in corp engineering has PM as facilitators between teams that are for various reasons not directly interacting at a planning level. I’m not actually if they create bug reports unless they’re filing actual bugs they’ve found.

Generally bug tracking for feature development is essentially umbrellas so you can see where things might be getting held up, and so you can (as an IC) prioritise.

Many of my assigned bugs are my own personal task bugs, again the bug tracker is helping me manage my own tasks. I’m fairly sure this is how the majority operate.

ICs have plenty of freedom for their own prioritization, and generally how they get to the end goal, and they’re able to experiment if they believe their current load has the spare time. There’s never really an ability to just randomly go off into some side project without at least arranging task redistribution with your manager.

Another thing to realize is at bigcorp/FAANG many engineers are working to support multiple unrelated projects, which is again a thing the PMs help with - occasional meetings between people from the different teams working on a given project helps find if there are any issues being missed.

The important summary is, I guess:

* no annoying formal processes like daily stand ups, etc that waste time if different people in a team are working on unrelated things

* PMs aren’t driving development, they exist to support communication

* ICs have freedom to choose what they work on, and how they prioritise, but have all the info required to actually do that correctly.

* with said freedom ICs are expected to do prioritise appropriately and effectiveness impacts responsibility (and presumably comp) in the future

* I don’t know how things differ if you’re an IC wanting to go into management/PM land because that all sounds awful so I’ve never investigated :)

The way things like scrum appear structured seems to be based on a lack of trust in ICs, or a sufficient overall lack of experience among people in the org, so maybe this simply represents a valuable tool in early stage companies.
A Passion for Cycads
> A dumb setting that fixes velocity is not the same, in any way, as a sophisticated self-driving mechanism that aims to recognize the world around it and adjust multiple parameters dynamically.

Except plenty of modern cars don't just have fixed velocity cruise control. They have adaptive cruise control that will speed up or slow down to match the velocity of the car ahead of you. They also have lane centering that will keep your car in its lane. That sounds an awful lot like Teslas.
Technical discussions during lunchtime? Rarely ever see this as a normal activity.
I'm sorry, I thought the title was a bit click-baity is all, and was following a rather worn out marketing ploy: "Liberate yourself, you're allowed to [spend money on these products]! Freedom! And here's some personal growth tips to go along with that."
> There's a sense of freedom to the model of computing where only your program is running and the entirety of the machine is your own little playground.

These days, we call that little playground a 'sandbox'. But I think OP's point is that sandboxes can be a lot more efficient that what they see w/ uxn. It's not exactly a secret that the whole FORTH model does not easily scale to larger systems: that's why other languages exist!
Highly talented developers don't need this structure and process, but if given the freedom, they are also more likely to create software that only they understand, using flavor-of-the-month languages or frameworks that they have personally selected.

Micromanagement processes and resume driven development are both problems but they are very different problems. IME good developers aren't going to be the ones pushing for all the shiny new toys all the time and writing inscrutable code. Good developers value stability and simplicity and they choose tools that help to get the job done. Good developers also write code that is relatively easy to understand.

The kind of developer you're talking about above isn't highly talented. In fact they're exactly the kind of dangerous mediocre developer that many of these overly controlled development processes evolved to contain. But the best ways to deal with them still aren't micromanagement. You can either teach them to be better (if they have a positive attitude but don't yet understand why what they're doing is often a bad idea) or fire/not hire them (if they're the mercenary type who only wants to exploit your salary payments until they can boost their resume at your expense and jump to exploiting someone else for bigger salary payments).
I didn't park in illegal spaces, I just refused to pay the meter. So, no high horsing needed. :)
> so the signed integer you're using to count stuff up from zero might be -16 now, which is astonishing

Actually, if it is an int, it is guaranteed to not be any number not explicitly set to (java has no-out-of-thin-air guarantees for 32-bit primitives). In practice on every modern implementation it is true of 64-bit primitives as well.

So the prototypical data race condition of incrementing a primitive counter from n threads can loose counts, but will never have any value outside the 0..TRUE_COUNT range.
Another thing you can invest in besides stocks, is to invest in yourself.

For example, my SO is working hard to get a side business going writing romance novels. To do this, she's spent a few thousand of dollars on seminars and conventions with both a learning and a networking component (which has gotten her into a regular work group of published authors), learning as much as she could about the industry, money on cover artists, copy editors, proofreaders, joining promotional anthologies, buying props and make up and books to show off on her promotional social media videos, not to mention all the time in learning this stuff and writing the books.

It's starting to pay off as she already has quite a few followers and preorders for her first book that will release in a couple months, higher than some other established authors in her group. There's some authors she knows personally that were able to make $200k doing this in their first year, so she may be on a similar trajectory at this point.

And she's still working a full time job as a marketing manager (making almost six figures for that) during all this, which she's hoping by this time next year she can quit and do this full-time (needless to say, I've been the main person keeping our house somewhat in order during all this, she hasn't had the spare energy).

So yeah, that's one way you can "use money to make money".
Both the author and Eric Evans are extremely experienced programmers.

Forking is to be understood conceptually, not as a terminology of any specific version control system. As in a git branch represents a fork in the time-line of the evolution of a code-base. It just happens to be that fork also means something more specific in case of the GitHub/GitLab online services.
Rust can also be used to write business applications that will compile cleanly to mainframe assembler (at least if your mainframe is 64-bit and runs Linux).
> We can desire a better world than these two opposite poles.

I don't disagree, but if you ask me which of these two evils I would prefer, I would always pick the peaceful one.

> people die in quiet desperation

To me this seems a much more dignified way to die than in a fit of mad violence, trying to take what isn't yours.
It's partially teething pains as they reimplement the world in Electron, and partially "sour grapes" since that transition was coscheduled with the "and no more local vaults, too bad"

Their QR code scanner went poof, in favor of "take a screenshot to the clipboard," and it no longer is able to suggest based on the "bundle ID" of the native apps. I dunno if it ever did that for Windows, and of course Linux support is brand new, but annoying for my case nonetheless
I feel like we discuss this once a week/month and it always breaks down to the same things bc of the number 10.

- Yes, some engs write code faster than others. 10x seems really high, so therefore 10x engs don't exist.

- Yes, some engs are more productive / pick better problems to solve / force multiply their teammates, but 10x seems pretty high, so 10x engs don't exist.

If we hadn't anchored on 10, we wouldn't be disputing that some people are more productive or faster, so I find proving or disproving the 10x eng to be pretty tired.

Good article though on the context for why some people are faster or more productive.
The previous tweet is also wild:

"[...] But our culture is to praise in public, and criticize in private."

Like seriously? In a thread where he’s publicly criticizing the actions of his employees, he really has the chutzpah to point to some corporate "value" about expressing grievances privately?
You need tractors if you're farming for tens or hundreds of thousands of people. In which case it's probably not the apocalypse yet.

As the OP says the knowledge of making enough food to keep yourself, your family and your probably decimated community fed and healthy is the number 1 requirement for surviving civilisational breakdown.
This old bit. Look.

Just because it's a centralized point of distribution doesn't mean it is desirable to suddenly plop on a responsibility to police the world's software.

Furthermore, if you're not auditing new versions of dependencies before you let them loose on your systems, that's all on you.

Writing software is a bit like sex. You make one mistake, and you end up supporting it for life. Always practice safe dependency management.

Microsoft has no nor should they have any responsibility, to protect anyone from anyone else. Especially with their propensity for going overboard in that regard.
Still not uncontroversial: https://pubmed.ncbi.nlm.nih.gov/31922622/
Hey Nintendo, I'm never buying anything you make ever again. I'll actively discourage others, too.
> These both may seem outrageous to American SJW

Yes-- for far too long we've been putting up with these insufferable American SJWs and their reflexive defense of the private property rights of megacorporations to refuse service to loiterers?

I unironically love this definition of SJW and vow to use it in all future HN posts where I can shoe-horn it in.

Edit: clarification
I have found the one distinction of 10x engineers is originality. They can write an original solution to a problem and be done. They don’t need a 1000 different tools to do their job for them, which has second and third order consequences.

That also means not having a petrified terror of failure.

Yes, there are 10x developers and this is measurable. It’s a progression of the Pareto Distribution. People scared shitless of originality, most people, cannot see this because their life goal is to crush it with internal processes.
The above comment comes across as frightened and reductive.

Here’s my own reductive take: If your engineers aren’t being productive if given freedom then fire them
Apparently having location services enabled causes all manner of problems with Zoom calls over WiFi as well. Locations services invoke periodic WiFi scans like you get when you click the WiFi drop down.
I dont really think you are grasping what I am saying. I want engineers to make tickets, and prioritize their time themselves. Creating a ticket to update docs is fine because it allows the engineer to set the scope, and define the audience.

That said, I dont want an engineer spending days on a task that will not bring value, nor do I want work done that will fall through the cracks, or have duplicate work done.

Asking an engineer to create a ticket to create documentation is not the hurdle you think it is.
> Highly talented developers don't need this structure and process, but if given the freedom, they are also more likely to create software that only they understand, using flavor-of-the-month languages or frameworks that they have personally selected.

I think you might be using a slightly incomplete definition of “highly talented.” My highly talented colleagues take maintainability and minimizing tech debt into account when making technical contributions.
Ask HN: Career Resources for Marketing Designers?
Someone important to me is in a job search as a marketing designer with experience and interest in e-commerce + tech.

As an engineer, I'm aware of courses, books, methods, and tools for hacking the technical job search and interview process.

Do you have any similar resources for the job hunting designer that I can share? FAANGish-specific welcome but not necessary. Thank you.