skysight-inc/HackerNews huggingface dataset:
Yes, developers and managers have to be involved in the full workflow. Why is this so hard?
The list of stuff is here:

https://www.dropbox.com/s/j142n121ezkgsmw/Copy%20of%20Videol...

Items with prefix 70C, 70D, 70R, 70CL are passives. ICs have the prefix 76.
Any analysis of a problem, requires understanding WHAT problem needs solving. The issue in real world is, buisnesses and markets (as well as technology) are changing very fast, and any in-depth analysis done two years ago might not have the same outcome as if done today again. This is a fundamental realization of agile. If you have a problem domain which is not subject to change, waterfall might be the right choice. But you almost never have that. I know it is hard to accept for us devs, often with backgrounds in Math/Physics/CS etc. because the problems we were trained to tackle there are always the same, and the laws of math and physics tend to never change (or change way slower than in modern markets).

Relevant clip perfectly highlighting the problems you have during requirement analysis: https://www.youtube.com/watch?v=BKorP55Aqvg
I wonder what the most common jobs are in a modern city. Probably all bullshit.
Synaptic vesicles are a major source of brain energy consumption at rest
Evidence emerges for dark-matter free galaxies
For someone that's unvaccinated, on the young side that works from home and doesn't (actually can't) go to bars/restaurants/etc the risk is already low. They can only get infected outside or while meeting friends.

How do you know they're nutjobs? Everyone I know that's unvaccinated are normal people. This is just what the media and politicians are saying without providing any proof.
Transport encryption is table stakes. It's really no longer something that can be mentioned as if it were something special. When I browse to a random website I don't think “wow HTTPS, so secure”. The channel client <-> service is encrypted, but the service still gets all of the data in plaintext.

On a technical level, Telegram is are as secure as Facebook Messenger. Both offer transport encryption and optionally E2EE secret chats. Actually, I might trust Facebook more (on a technical level) because they don't have Telegram's disastrous history with home-brewed crypto protocols.
If you fancy living on the edge, there's already an AUR package 'coreutils-hybrid' that uses stable uutils (with unprefixed names) where possible, falling back on GNU coreutils:

https://aur.archlinux.org/packages/coreutils-hybrid
Read the first couple of chapters of “What it Takes” specifically the ones on Dole and then look at the current pool of politicians.
You needn’t wonder why things are in a state of decline.
The greatest hardship a modern politician has been through is losing a Twitter battle.
You are probably not the target clients for those product companies, that's why they can ignore your needs.

I think in general we are going through very strange times. Look at games - most of them are either released under-baked ("early access") or exploit your instincts to make you spend more than expected ("freemium") or are essentially making users pay for the same thing twice ("re-master").
I believe that they would have written the manuscript, probably by hand but possibly aided by a typewriter, and then given it to a typographer (probably one with experience working on mathematical material) who would have typeset it, cutting any new symbols required.

I'm not a historian but this seems like the only plausible process given the technology around at the time.
It's not just the FSF's role to "comment" on software licenses, but also to advocate for the use of free software licenses. That involves convincing developers to use them. To go into a project and dictate to them that you don't find their work notable, while still demanding respect for your own project, isn't likely to spark good-will towards the FSF amongst developers. If I were a director at FSF, I would cringe at this kind of interaction, and lean much more towards the "honey" approach for catching flies.
If you are an actual non-profit, I'll send it all to you.
> they have reproducible builds.

Ah, I see on Android they do. Not iOS according to an open github issue since 2015.

I am suspicious of signal because everyone says "use Signal it is secure" and it is popularly known for this. Because of this reputation for security, users will get comfortable and talk about their illicit activity, which makes it an attractive target for power brokers the world over. Every app could have this problem, but Signal is the one everyone keeps saying is secure, so it's the place people will spill their secrets.

Reproducible builds on android look cool, but I wonder if there are other threat models on Android than dishonest builds of the program itself.
If you have a proprietary program, reimplementing it under a FOSS license is a good thing. If you have a copyleft program, reimplementing it under a license that allows proprietary modifications is a bad thing.
Signal and Matrix aren't ready for grandma adoption.

Out of all the non-whatsapp choises, Telegram is the least bad (yes, no E2EE, relax) and is something you can actually get your boomer-aged parents and their parents to use with very little help.
I just posted the list.
Developers who fail to take responsibility for the full workflow, fail.

Its not "Agiles" fault, although this is often used to justify the failure.

Developers have got to realize that they are responsible for the full workflow from beginning to end, and only poor/low-quality developers will work to change that natural law - with negative effect.
It is very easy actually. We often a business uses Excel for their processes and flow, that is they have excel sheets that they edit, copy, send around and merge back. Now, we all know the problems that exists with this approach, and even the customer knows that. But that doesn't mean they can perfectly describe how any application that gets rid of those excel files should look like.
> Amazon most likely shared a postal address in Amsterdam with Mercedes, Siemens or BMW. Or at least the street

You are talking out of your ass and revealing your xenophobia. The Dutch Sandwich tax dodge works mostly for firms who can pretend that Caribbean post box firm own their "intellectual property" (i.e. tech and pharma firms) and who can then pretend that their actual operating entities are loss making. And no, the German car and industrial companies don't do that.
Ask HN: What do Google search URLs contain?
Google's search URLs get longer and longer, with a substantial ASCII-armored string portion. Is this string encrypted? Does it contain sensitive data, like personal information?
Waterfall creeps in because it's the most rational and linear way to do anything and we do it in all activities is our life without even thinking about it.

When you build a deck, you 'Waterfall' it.

Iterative development is slightly counter intuitive, until you write software for long enough, then it's definitely the intuitive approach.

I suggest the simplest, easiest, best way to combat the urge to overplan is to break the waterfall down into iterations, do those iterations, assign maybe risk to different iterations given unknowns and to expect change.
SAVAGE !!!

I love it :)))
Is this like a parody of the Dropbox thing?

Web3 is beyond the hill of magic vs technology for me currently, it's on the tolearn list. Is that actually the alternative to YouTube?
it's an old and widely accepted truism. I don't know how much formal research had been done into it.
No service outage should ever cause the application itself to be unusable. Which mobile platform are you using? If the browser cannot successfully contact our backend services (for things like update checks, or refreshing its internal list of known-malicious URLs to avoid) then it will simply carry-on and attempt those requests at a later point.

Sampson (Brave Team)
Sorry to hear that you don't enjoy life. I was in the same place for a long time. I would recommend seeking professional help. Not therapy, but just plain antidepressants without some condescending therapy. At least try out what it feels like being happy.

That being said, I am not going to be the one to say that suicide is never an option.

It's a box full of nitrogen. You can build a less polished version from a home improvement store for a few bucks.

Maybe you will enjoy the build process so much that you won't pull the trigger.
It takes substantial effort to build a good dataset, proportionally more if it gets bigger, and people like big datasets because you can train more powerful models from them. So I am not surprised that people tend to gravitate towards datasets made by well-funded institutions.

The alternative is either a small dataset that people heavily overfit (eg the MUC6 corpus that was heavily used for coreference at some point where people cared more about getting high numbers than useful results) or things like the Universal Dependencies corpus which are provided by a large consortium of smaller institutions
a (good) source would've been great :)
MyISAM used to be the default for a long while. I made a bit of extra money when younger tidying up MySQL DBs that were in inconsistent states thanks to MyISAM not enforcing FKs.
Moderation tools are lacking compared to, for example, Discord and Telegram. Also no bots, which is an issue for many communities.
I think a lot changed after 9/11/01.
A high proportion of the booze consumed worldwide is what the bureaucrats call "unrecorded", and poisonings are exceptional.
And Google Lighthouse doesn't like progressive images. You can have a well-optimized progressive JPEG that renders with just 15% of the data, but you get dinged for not using Google WebP, and your LCP is counted only when it fully loads (this is a known bug, and it died a painful death in a bikeshed of what a "contentful" image looks like.)
This seems like a ingenious plan to prevent China selling their tech to other countries:

“There’s no way to read that as something other than a no-China club,” said Graham Webster, editor-in-chief of the DigiChina Project at the Stanford University Cyber Policy Center. “It’s not subtle who they’re talking about.”

Asking governments around the world to root out any internet infrastructure made by Chinese companies like Huawei as a barrier to entry into the alliance struck Pielemeier, Webster and others as unfeasible for less prosperous regions and as a requirement that would limit the pool of participating countries. They also worried that the idea underpinning such a request runs counter to the human rights values that digital rights advocates have been supporting for decades.
..or LBRY/Odysee
So you have two fully-working hands, then?

Good for you. Try to remember that lots of people don't.

Some don't have 2 hands. Some do but one doesn't work. Some do but have difficulty coordinating both. Some do but are using one to hold the device, or using one to support the other hand. Some do but it hurts to use both at the same time, or it hurts to stretch their good hand from shift to some of the letters.

Try to think just slightly outside of your own use case. Try to remember that not everyone is able-bodied.

There are a lot of devices designed and intended for people with disabilities, but which are affordable only because they sell most of their production to non-disabled people, such as the Jarkey. You don't think about it but you benefit from it.

Learn to think about such things, and you will become a better, more pleasant human being, and that means that you will enjoy your life more.
Bad tools for moderating large channels, no bot support.
Irish data watchdog lobbied for business-friendly GDPR
Is your claim that it costs half a billion dollars to setup to sell weed legally in FL? That defies all order-of-magnitude estimation.
They are not treated well, they are treated according to the constitution.
I've worked on all kinds of projects, and every single time the project failed, the tooling and methodology were blamed, not the individuals. This is the #1 cause of failed software projects - the inability for individuals to take responsibility for parts of the workflow, for which they are incompetent, and not subsequently working on improving that competence at an individual level.

But true, breaking larger problems down into smaller units (Agile/Scrum) is an effective way for a "manager" to help their developers - but I argue this is non-optimal for sociological reasons, not technical: Adherence to a cargo-cult is a function of laziness, not competence.
On author's defense I don't think twitter should ask for a phone number for recovery (or for any reason) It is only making things harder for people like OP
> When the client count and the business complexity explode, things start to get hairy fast, but by that time the investment in MySQL is hard to walk away from. You will start to hit all sort of edge cases in other DBs - which MySQL did not exhibit simply because your application grew around its feature set and limitations.

I'd like to point out that this seems to happen whatever db you move from and to.

Sometime over a decade ago I was part of a team moving from an ancient version of Sybase Adaptive Server Anywhere to the newest Microsoft SQL server running on a beefier server.

We ported everything carefully and tested it out. We also felt good since both where dialects of T-SQL.

...and then we ran right into so large performance problems that we had fall back to the old system.

The reason was that at least older models of had Sybase ASA had implicit indexes.

Feels like there is always something.
The problem is that this does not happen often enough to be of any relevance so they simply and literally don't care, even if you are a paying customer. It's a valid reason not to use any Google services anymore, though. That won't harm Google nor will they change anything (the "no relevance" argument) but at least you get to sleep well at nights knowing you'll still have access to your "life" the next morning.
SAFe works just fine when Agile is perfected, i.e. about 5 years after every day practicing of Agile. If you have no Agile to begin with, then you cannot scale it.
Happy to hear that you're enjoying Brave. Regarding your concerns over Sync, we publish details on our Brave Sync works at https://github.com/brave/brave-browser/wiki/Brave-Sync-v2. Good that you're cautious though :)

Sampson (Brave Team)
I think it is, but I can't tell if this is satire.
My technique is very simple. I bought a water filter jug which I can fill and bring to my desk (I work an office job). Turns out that simply having the water available within reach rather than having to get up to refill my glass helps a lot (and the improved taste of the filtered water doesn't hurt - but this may not be necessary depending on the quality of the tap water where you live).
I know :)

But people did take agile to an extreme and they did forego the essence of other processes.

I feel that the line "everything in moderation" applies well to project management. Moderation being the key part.
It had no discussions though. [0]

[0]: https://news.ycombinator.com/item?id=29385491
Just another example of academic conformity.
Intriguing, but I think I lost you a little in the details and really dying to understand your perspective.

1) creating an immutable DAG that processes chunks of immutable data,
2) persisting each chunk (being loose with terms here) for durability,
3) 'modifying' it in the immutable sense
4) and then passing it on to the next edge and so on

Isn't #4 the persisting part, not #2? Maybe I'm confused by what you mean by "persist"? Render the instructions (mutate the data)?

And when you say "'modifying' it in the immutable sense", does this mean that the original data stays untouched, but "instructions" on how to modify the data get "pinned" to the data?

Then every other subsequent step in the DAG is just modifying the "instructions"?

If I understand you correctly, your point about how this is where FP shines is really illustrated in #4. You end up passing instructions around instead of the data. But how FP instructions can be modified and modified again really baffles me. The closest I can get to understanding it in practical terms is by using something like Clojure and thinking about how Clojure is just data, and you can modify, or build upon Clojure by modifying like you modify data. I struggle extending this to another language like Scala or JavaScript.
I think they are highly overestimating how much science advanced pattern matching will provide. Certainly no conceptual understanding will ever come from that.
Can someone explain this better for me and how it would be more useful than a regular transformer?
Actually Japan is a very lucrative market for Asian drug dealers, because the price of drugs is so high there and they're pushing mainly synthetic drugs which are are quite cheap to produce compared to heroin, so they can afford losing some shipments.

https://www.reuters.com/investigates/special-report/meth-syn...

"The wholesale price of a kilo of crystal meth produced in northeastern Myanmar is as little as $1,800, according to a UNODC report citing the China National Narcotics Control Commission. Average retail prices for crystal meth, according to the UN agency, are equivalent to $70,500 per kilo in Thailand, $298,000 per kilo in Australia and $588,000 in Japan. For the Japanese market, that’s more than a three-hundred-fold mark-up."
Thanks. I know that my company's HR had some clearly unenforceable stuff in their various contracts, noncompetes and NDAs, but they banked on folks not having the means to fight it.
Crypto Traders Could Be Denied U.K. Compensation When Firms Fail
Yeah, but POSIX was just codifying the proprietary UNIX standards. UNIX got bootlegged in a era where license enforcement wasn't strict because people didn't even know what licenses where. These days UNIX would have been a strictly proprietary AT&T product, from day 1.

Heck, POSIX stands for Portable Operating System (POS) + IX because X is a cool letter and IX because POSIX is cooler than POSIX plus, you know, UNIX.
I don't think it's strange. There's datura growing all over the countryside
where I live and magic mushrooms too, probably (although I wouldn't recognise
them). I don't go plucking and using it. Neither do most people I know. Why is
that strange?

Can you say where you have heard about the Thracian wine thing? I know the
ancients diluted their wine (not just Thracian wine, also Rhodian wine which was
something like French wines today, the top of the tops), but they also added all
sort of taste enhancers to it.
I remember a few months ago (or maybe a year ago) there was some change to their terms of service which no longer allowed whitehat content. Many people pointed out the obvious flaw in their rule changes but what can we do really?

I hope more people move their variety of content to Odysee, Rumble and other alt tech as that will help YouTube slowly lose their credible users.
What I Learned Analyzing 13 Years of Basecamp Home Pages (2017)
Coders just want to code. Waterfall means you have to wait before you code, and plan, and organize. Agile means you just start coding, and code and code and code until you leave and someone else has to clean up the mess.

This is no different than most other activities in life. See the Stanford marshmallow experiment.
I consider fleshing out customer requirements part of the engineering process. You cannot expect the customer to properly communicate what they want/need. That doesn't mean Scrum, you have many other tools at your disposal, presenting the customer with scenarios to challenge their requirements, use interactive prototypes or even paper ones. All of them far cheaper than implementing the wrong thing.

I agree about the pitfalls of not seeing something usable until it's very late and how to measure progress. The opposite is also true however, you make some easy non-scalable PoC and it looks like a huge progress when it actually can't or shouldn't be used as a foundation for anything.
I agree with that.

But it's worth noting that we need to spend more time on task management with a shorter development cycle.
In waterfall or scrum or whatever, one development cycle often comes with listing tasks, prioritizing, planning, developing, retrospection, or something similar.
If the cycle is long, we can spend more time on each process.
But if the cycle is short, we rush to complete each process and can't spend enough time understanding each process's meaning.
So I focus more on consuming as many stories as possible.
I never think about the product's goal and how I can contribute to it.

So we have to spend more time teaching the purpose of each process.
Or we end up as a failed agile development.
Why? You're allowed to build whatever you want, however you want? Why police people's licenses? Are they misrepresenting something, misleading people?
No matter what process we adopt, we'll always have waterfall as long as the sales side of the house needs predictable features and release dates. There isn't really anyway round that - if we can say with confidence that we'll release features X, Y, and Z in a release 6 months from now, then we don't have room for more than localised iteration.

Agile-ish systems work great when you don't have pre-determined delivery dates, but unless you are an internal-facing team with only a backlog of tech-debt to burn down... who is actually in this position?
Healthcare and retail/restaurant work I would imagine.
But isn't the problem statement itself what you need from customer? My idea is that the customer approached you with the problem statement and their expectations is that you would provide possible solutions to it instead of the customer defining the solution exactly and just asking you to "code" it.
Pis can be made relatively reliable, but it's extra effort (read-only or no SD card, making sure power supply is good, ...). For a business scenario, I'd consider a mini-PC instead: they're not that much more expensive than a Pi once you're done with all the parts, more reliable out of the box and easy to replace if needed in the future.
Agile is just 20-30 small waterfalls instead of big one. How small a waterfall needs to be to fail?
It's the next paragraph after those bullets:

> That is, while there is value in the items on
> the right, we value the items on the left more.

Also keep in mind the manifesto came as a response to a "document-first" software design method, where basically the complete product was documented, planned and contracted before the first code was written.
Sounds like they're smoking high THC strains, and not for medical reasons. Did you miss that part of the comment?

Ss for the dependency, I am aware of no study that shows lingering effects on anything after two weeks off. And it's much easier to break a cannabis dependency than, say, an alcohol dependency or most others.
> what problems Waterfall presented

These are presented in the article.

> Analysis, Specifications, Requirement

These tend to be inadequate, incomplete, or ..

> Qualification

.. at this point the customer discovers that what they asked for does not actually solve their problem.

You cannot do any kind of exploratory or innovative work in waterfall, because you can't specify that upfront. You can't easily co-evolve solutions by discovering what works and what doesn't. You can't even do A/B testing really, because every time you do your GANTT chart bifurcates.

There is a history of big, spectacular IT project failures, often commissioned by the public sector, but not always. The evolution of non-waterfall systems has been driven by trying to prevent or mitigate these failures.
Imo analysis needs domain knowledge, the developer can do it on their own but it won't be as good as when a domain expert does. A developer doing their own QA will have the same blind spots as during development. And of course, if he was also doing the analysis, he'll have the same blind spots as during analysis.
Thanks, I actually hadn't heard of that.

Did you try drinking more water?