skysight-inc/HackerNews huggingface dataset:
It is vital to have someone close enough to the project that the team trusts them to see their honest opinions about progress and blockers, including non-bullshit pointing of tasks, who is the point person for communicating progress to management, and who is capable of producing reports that are technically bullshit in an is-this-quantifiable-this-way sense but actually do reflect reality usefully to managers. Someone who does that well is worth All The Money.

They're useless if you're giving management direct access to team planning & communication tools, of course.
Any movement that gains traction will be corrupted. The moment companies want to hire people who tick a box, they pull on a supply chain of certification authorities (which includes, most perniciously in my opinion, grad schools) that codify and dumb down any set of good ideas and practices so that it's teachable at industrial scale to mediocrities.

Back in the late Aughties I worked with someone who'd recently graduated from a design program and was interested in becoming a UX expert, the new-hotness of the moment. The person wanted to go nearly straight from undergrad to a Master's program at CMU. I -- being a HCI/UI person myself (and rolling my eyes at the term "UX") -- counseled doing freelance work for a couple years to get some practical experience that would provide grist for the grad school mill. No interest.

I can't say I blame the person too much; big companies want to show their seriousness by hiring people with credentials, the value of the credentials be damned.
It's a competitive advantage vs legit hosting companies that can be leveraged for profit.

Simple as that. If it pays well someone will do it, slimy or not.
This is absolutely correct. For example, what is the point of a sprint in Agile ? Do what one can finish in a sprint but try and finish "modules" while maintaining quality and carry over rest to next sprint. What does management read? Finish ... modules ... current sprint?
A lot of commercial software focuses on building cool GUIs because selling the software is the whole point. The point of community maintained software is to solve some problem some people have and so that’s what gets focused on.

I don’t think tacking “cool stuff” onto free software is the answer, I would argue education is.

Much like how we educate kids on the dangers of false advertising we should educate them on the dangers of non-free software.
Their privacy means they get to farm your data first.
The first point is that for many, being vegan isn't a "dietary restriction", but a lifestyle based on a moral philosophy that we shouldn't harm sentient beings more than necessary. Eg, the Vegan Society's definition is (in part): "A philosophy and way of living which seeks to exclude—as far as is possible and practicable—all forms of exploitation of, and cruelty to, animals for food, clothing or any other purpose."

There are vegans who really get into being VEGAN as an identity. Then there are the other ones who just do what we do and don't see a need to volunteer it or announce it at every possible chance. Some just live their lives, some participate in various aspects of animal rights activism. Either way, the VEGAN identity folks tend to be the ones that you will notice and remember. The rest, you pass by every day and probably never even know. (It's also worth mentioning that there are also a lot of people who are "vegan" as a fad diet (like "keto" or "paleo") but don't subscribe to the philosophy (vegans will usually try to make the distinction that those folks really just follow a plant-based diet), there are vegans who also get into weird things like raw food, alkaline water, fasting, etc. Like it or not, any large group of people will have fringes like this and they tend to be very vocal and attention seeking.)

Similarly, there are meat eaters who make BACON a huge part of their identity and like to remind you every chance they get how much they like it and "carnivore" dieters, etc.
How would the burning of private bondholders to the tune of €140 billion have affected the Euro currency?

> you don't ultimately control your own affairs you share them with the others who use that currency

The currency had nothing to do with it. The only thing which would have absolutely forced them to stand over it would have been existing EU law - which there was none.

The European Central Bank can't legally stop issuing currency to Ireland just because some French or German banks got burnt.
UK announces £220m to design a ‘commercially viable’ fusion power plant
I'm not sure which embedded platform you're using but give AngelScript [0] a look.

I've been using it to extend some C++ code (bsnes emulator) and it's been fantastic. It's so nice to have a C++-like scripting language with natural script-host bindings that I don't have to think hard about creating or spend a lot of time writing marshalling code or worrying about memory layouts. On top of that nice script-host interface you get an actual usable scripting language without silly things like 1-based array indices.

That said, it does not come with any sort of standard packages like luasocket but there is support for defining your own modules.

Depending on the embedded platform you're using, there may not be support for the native calling convention and you may have to fall back to the generic calling convention, or you could roll your own code to accommodate your platform's calling convention.

[0] https://www.angelcode.com/angelscript/
A product marketing team named the app, not the programmers.

Do you think Facebook is just a company made up of programmers?
No need to imagine, its quite common on youtube. There is no ourage... so far.
Here is the thing though (8+ year vegetarian here, with vegan periods): we have been grown up eating shit like that. Eating sausages, salami, all that jazz.

There is nothing wrong with going back to the spices and texture of that. A certified bio soy sausage gives me everything that I want to get that is familiar and similar to me eating hot-dogs in my childhood - and without any ethical concerns. So please, do understand that not everyone wants to replicate food, but rather just want something with a shape of familiarity to insert into their everyday staples.
I'd be willing to bet big money that the programmers did not name this app. In a company the size of Facebook, that'd be a miracle.
Race conditions create meta-stable states. Fixing them always increases predictability of the code. It can also result in fixing formerly "cosmic ray" type bugs that occurred once or twice and were never seen again.

This is because one of the sources of very hard to reproduce bugs is a set of race conditions aligning just right.
I remember a time I worked with a team not using the agile process. We were agile.

When I worked in teams following the agile process, we were rigid.

"The Agile that can be named is not the true Agile."[0]

I'm not being entirely facetious.

[0]https://en.wikiquote.org/wiki/Tao
Which is why there are twelve more specific principles to give more details.
...a list of new business models zero of which have shown an iota (pardon the pun) of traction in a decade. I feel the list of crazy startup ideas circulating on r/wallstreetbets is as valuable.

The technical and scaling problems are all self imposed due to leveraging a woefully inadequate storage mechanism. It’s basically coal-powered banking.
I think the point was they swapped out one problematic solution for another
Nothing.

Around 5 years you should start getting 3 weeks of vacation.
Shooting a bear that's charging at you isn't non-vegan, and by the same token, pest control isn't necessarily non-vegan either. This is the de facto definition of veganism:

> Veganism is a way of living which seeks to exclude, as far as is possible and practicable, all forms of exploitation of, and cruelty to, animals for food, clothing or any other purpose.

And of course, what's possible and practicable is subjective.
I think EdDSA desperately needs to be allowed in FIPS certified hardware, so that secure hardware will have support for EdDSA so that people who have to store keys in secure hardware will be able to use it. I mean HSMs, smart cards, secure enclaves, TPMs, things with a ATECC508A, etc.
For those using the "password" or "md5" authentication method, this would be a good time to start using SCRAM instead.

First, set

password_encryption = scram-sha-256

in postgresql.conf[1].

If setting up a new server, use auth method "scram-sha-256" in pg_hba.conf[2][3].

If upgrading an existing server, use auth method "md5" in pg_hba.conf, which actually allows either MD5 or SCRAM. Then, start updating the users' passwords to be encrypted with SCRAM by resetting the password (the "password_encryption" setting causes the new password to be encrypted with SCRAM). After there are no more md5 passwords in the system, you can set the pg_hba.conf auth method to "scram-sha-256" and you're done.

Note that this all requires connecting clients to support scram (version 10 or later of libpq).

[1] https://www.postgresql.org/docs/12/runtime-config-connection...
[2] https://www.postgresql.org/docs/12/auth-pg-hba-conf.html
[3] https://www.postgresql.org/docs/12/auth-password.html
i agree with about 98% of what you said, but julius caesar had also heavily mortgaged the future for the present. he had aging legions who had already mutinied a few times and he kept winning them back with more and more promises that he'd not yet fulfilled. i wonder if a force as formidable as the parthian archers would be something that ended up finally breaking the resolve of those experienced legions.
All modern Developers are doing agile, whether they believe it or not.

The agile movement of the 90's was in response to waterfall constraints imposed by the tools of the 70's and 80's.

The majority of projects today are no longer handcuffed by these constraints.

For historical context, I would suggest reading up on the Scrum vs XP war, as one camp pursued a commercialization and certification path to agile and the other remained largely principle-based.

When I see people expressing frustration with agile, the cause is typically a byproduct of the commercialization camp.
I once took over a project from an engineer who'd been let go, and after I saw the mess of a DSL he'd made and used in 100% of his contributions to the project I understood why. We called it our infernal DSL.
> That seriously devalues a Harvard diploma in hiring decisions.

Not even close. It's a brand and it's a good brand ... a very good brand and one of the best and it opens doors. Nobody honestly really cares about what happens behind the scenes the halo is typically that strong.

Look at it this way. If someone gets an Academy Award it's a branding that says 'you are chosen and special for some reason'. Doesn't matter if the film is good or sells the most ticket. Someone has decided it's special (or a production person/director/producer is special) and that's that.

When someone buys a luxury product sure it's most likely a more quality product but that is not what they are paying for or they care about. Not only do they not want to hear it's made in the same factor that makes things for Target but if they did hear they'd probably not care that much either.

> Especially since Harvard is easy once you get in.
Did it occur to you that perhaps people rise to what is expected of them and are perhaps more fearful of failing or take advantage of all sorts of help so they do graduate? Or that they work really hard because they are there and are afraid to flunk more so than at a lesser university? It's also obvious that there are probably 10 people that could 'do the work' for those that are admitted. It has never been about the best and smartest at any upper tier college. And there isn't even a way to measure that anyone who thinks top grades and testing is what matters hasn't dealt with enough people in the world who are productive, have achieved but do not test well.
Half sibling (or uncle/aunt) inbreeding is considerably higher risk than first cousin interbreeding. Only sibling is worse.

I have 2 recessive things that I know I carry, thanks to genetic screening. If I boinked a half sibling, they'd probably be a carrier of 1 of them, and there's a 50-50 chance any resultant offspring would have the conditions.

(Neither would be fatal but both would be severe chronic things-- e.g. hemachromatosis.

There's probably other rarer recessive things that I'm a carrier of and don't even know about.
> but the advantage of Postgres is you can always drop down to SQL.

All the project i've worked on eventually devolved into a weird mess of part orm and part SQL.
"What do you mean we can't read or data-mine their conversations? That's impossible."
Countries who have successfully gained independence have often sacrificed a lot of blood for it. And built strong armed forces to back that independence up with.

Whatever we may think is morally right, HK does not seem to be putting together that hard resistance, nor is it building up its own armed forces to declare and maintain independence with. China thinks HK is legally theirs and nothing we say or do will change their position over it.

That's why I don't see these protests achieving anything.
'It's going to be a revolution': driverless cars in new London trial
Agile was proposed as a way for engineers (or "self-organizing teams") to manage things better. The complaint is that the engineers' better management process has now been hijacked by management and turned into something else.
Are you a member of We Are Donor Conceived on FB?
I think I stumbled upon that a while back. Thank you!
> This applies equally to libraries or DSL. The developer can document them clearly and extensively, or not at all.

This is true, but functions usually don't require as much documentation. With a function, I usually know when the arguments will be evaluated and how, for example: this isn't an assumption I can make with a macro. If you don't change syntax you don't need to document changes in syntax.

> "Incidentally, Lisp (Common Lisp) definitely implements a with-like syntax."

> As a macro, most likely?

Possibly, but a mature Common Lisp implementation has likely taken care to preserve stack traces and make sane decisions about how to expand, is probably thoroughly documented, etc. A macro implemented by your average programmers has little in common with this, and if you're doing all this work, the idea that DSLs are trivial to implement in Lisp begins to erode.

> It can also eliminate a massive amount of incidental complexity, by eliminating lots of repetitive, boiler plate, copy and pasted code, where bugs will inevitably pop up as an error is fixed in one place but not another, or a subtle typo, a programmer forgets to clean up a resource...etc. etc.

That's all true, and I'm not completely against their use. DSLs can be an effective tool. But I think that tool is a double-edged sword which needs to be used much more judiciously than the glib, "Do you have a problem? Write a compiler!".

> Does Racket use macros less aggressively or egregiously than other Lisps?

I don't think so. It's really the programmers, not the language, that uses macros, but I would say that the culture around Racket has a big focus on creating DSLs, so if anything Racket programmers use macros more aggressively and more egregiously. :)

But there are other upsides. Racket is the only language nowadays with a decent, truly cross-platform desktop UI library that ships with the language that I know of. Python and Java were once contenders, but support for Java has dropped quite a bit, and Tk isn't even used by many Python programmers any more (Qt is just so much better--but it doesn't ship with the language).
Rape (and related crimes) and Murder are both crimes which have a large external cost and where there is a reasonable chance at repetition.

The value to society of catching the perps in these cases is large enough to make giving police access on a case-by-case basis worth it.
I work in an environment with projects for many different customers, and almost as many different approaches to coordination with the customer, and I'd say the points from the agile manifesto are quite useful to suggest and evaluate the process for a project. Can we get a proper quick feedback loop? Can I talk directly to people that actually know about the details? How does the change process work? How much overhead is there that's not directly relevant to doing whatever it is were asked to do? What kind of decisions do we need to stick to that have been made without/against technical guidance?

It really depends on the customer if that process is something that can't be influenced. Although of course we're as an external party often have more freedom in that regard than a customers direct employees.

EDIT: added some specific questions
Agile's not the problem. Micromanagement under the guise of agile is the problem. Ideally implemented, Agile sort of allows a development team to micro-manage themselves, but management is usually unwilling to let this happen.
We get an extra week vacation after 9 years!
Enterprise has a lot less pressure to switch, because they have existing capital investments into, for instance, large, expensive IPv4-only firewalls that aren't currently "broken", and large private IPv4 subnets already walled off with enough IP addresses for their device/asset catalogs.

It maybe shouldn't be a surprise that IPv6 has seen much faster consumer adoption comparatively, as consumer ISPs face much less steady/predictable device growth and sometimes much more complex routing scenarios (cell towers have much more complicated internet traffic routing needs than wired ethernet in an office park somewhere).
The Disciplined Agile Manifesto
I spent the last few years building up an immunity to iocaine powder.
The main advantage for Star Trek though was that this kind of device is really easy on the prop department. It’s just a plane of smoke glass with lights shining through a cutout, easy to add the button of the week.
A while ago, Microsoft deprecated Windows System Image backups[0], and, on some Microsoft page I can't find now, they recommend third-party software for OS backups. (Although, weirdly, the option is still present in Windows 10, and, AFAIK still functions???) How astounding when, in Linux, you can just `dd` the Windows drive to another and the clone works perfectly (didn't even trigger any Windows activation DRM for me)! This resonates with your anecdote.

However, the average person probably isn't comfortable (dare I say should be trusted?) with block-level utilities that can wipe the wrong drive at the drop of a typo. To propose that they should be comfortable with a terminal at all is, to put it kindly, delusional, and it's a great example of the post's mythical excellence.

This is the current meta I see:

- Linux only offers "excellence" to A.) EXTREMELY SIMPLE users who never stray from compatible use cases (which is a surprisingly unsafe assumption) and B.) EXTREMELY ADVANCED users who aren't sufficiently advanced for BSD and can overcome any Linux software compatibility issues or elide them by forcing themselves to use possibly suboptimal alternatives.

- Windows only offers "excellence" to AVERAGE users technical enough to debug in vague, indirect, salt-over-the-shoulder ways (like practicing neuromedicine), but not technical enough to feel comfortable with terminals or desire stuff like more comfortable programming workflow. (Also, bonus: it covers virtually all prospective user software and hardware.)

[0]: https://www.digitalcare.org/system-image-backup-windows-10/
The language a program is written in has no bearing on whether or not the program is susceptible to race conditions. You can have data races in Python, Javascript and Rust as easily as you can in C.
Most (80%, nobody knows how many) "sperm donor kids" don't know they were conceived that way. It's often a family secret and many parents were advised by doctors never to tell.
"I'm not sure what you mean by X; did you mean X1 or X2?" is a perfectly reasonable thing to say during a conversion (modulo formality)
Developers don't like:

* Committing to dates and then being accountable for the results

* Spending time planning, rather than "doing"

* Admitting to business leaders that much of their work time is not spent writing lines of code, but dallying in all the interesting byways of the field, favorite websites, pet projects, and random semi-related technology interests

* Sitting in meetings of any sort (sprint planner and retrospective)

* Having spoken, out-loud disagreements and negotiations in order to arrive at a consensus (sprint point estimations)

* Having their mistakes, miscalculations, lack of planning visible to everyone on a big monitor (sprint board / retro)

* Getting out of their chairs to go talk to someone else in order to remove a blocker or understand a dependency (task estimation and completion by end-of-sprint)

* Anyone involved in the process that isn't a coder (Scrum Master, Project Manager)
Unfortunately, actual usability seems to be getting ignored in the rush for a "standard". In the meantime, you might want to consider using RAML. It compiles to OpenAPI and is far more optimized for use by humans instead of machines.
Made me exhale out my nose:

"Whenever I gave even a moment's thought to whether I needed to learn compilers, I'd think: I would need to know how compilers work in one of two scenarios. The first scenario is that I go work at Microsoft and somehow wind up in the Visual C++ group. Then I'd need to know how compilers work. The second scenario is that the urge suddenly comes upon me to grow a long beard and stop showering and make a pilgrimage to MIT where I beg Richard Stallman to let me live in a cot in some hallway and work on GCC with him like some sort of Jesuit vagabond."

"Both scenarios seemed pretty unlikely to me at the time, although if push came to shove, a cot and beard didn't seem all that bad compared to working at Microsoft."
> Mass market internet capable consumer devices, with significant compute hardware used to run a wide range of software. That’s a rather narrow list of device categories.

I am not sure what you're trying to say. I asked you to elaborate on your claim:

> Consoles are a fairly direct comparison so the link is obvious.

Also

> But, also things like driver compatibility, it’s simpler to develop software for well defined ecosystems which consoles provide. Many non exclusive ports don’t happen because it’s surprisingly expensive to port triple A games the PC. If you want to nitpick that then fine, Red Dead Redemption is on PS4 and XBox box, but never made the PC jump. Porting AAA games to PC is surprisingly expensive, even if getting it to almost work is cheap. But, it’s vastly more widespread than that. Just try to load some of that realtime software running inside your car on a desktop it’s simply not designed for it.

Yes I agree that it can be expensive to port games to different platforms. Not sure how that goes to support your assertion that closed ecosystems are better. Platform makers want people to write stuff for their platform. It's the prerogative of the game/app makers to support the platforms based on their target demographic.

All I am saying is that:

> Limit what software can run and you vastly improve most people’s experience. Freedom is not just about letting people do anything, it’s also a question of what contracts they can enter.

This doesn't make sense, and nothing you have thus far stated helps to further your argument. Apple has incentives outside the user experience to have a tight hold on the iPhone ecosystem. Were they to do the same thing to the Mac, they'd face a strong backlash. No platform maker wants to deny people access to their platform willy nilly.
Their country their business. They don't need to apologize to anyone for ousting a dictator no matter who they chose to replace him with.
You've hit the nail squarely on the head. The problem with Agile isn't Agile itself, but the fact that humans can't keep themselves from using the data it produces to their own non-Agile ends.