skysight-inc/HackerNews huggingface dataset:
> P.S. I am tired of the YADIW excuse. Let's have a nice honest discussion about how it can be fixed.

If somebody complains that Scrum is bad because e.g. every day you have to update management at stand-up (as mentioned in TFA), but the Scrum Guide, every book ever written on scrum, the websites of the Scrum Alliance and scrum.org, and more or less every advocate of scrum great and small, states explicitly that this is not the purpose of the stand-up but instead to highlight obstructions and opportunities for collaboration, then I don't see what more there is to say than "you're doing it wrong" - because you are doing it wrong, in letter and in spirit. It may not be your fault that you're doing it wrong (it's my guess that the widespread perception that scrum is management-heavy is a function of scrum's market penetration combined with the inherently dicatorial culture of corporate governance). But doing it wrong you most certainly are.

This is not one of your complaints of course, but you do complain about estimation, which - as a sibling comment mentions - is simply 'out of scope' for Scrum, which is a smaller package than people think. (Plenty of scrum thought-leadery types are part of the 'No Estimates' thing, for example.) It does, however, mandate that you occasionally meet for the explicit purpose of working out how to improve processes that are not working properly (such as estimation) - in other words, that the team takes seriously as a collective all the things that scrum does not talk about in itself.
>Corporations as a rule, and there have been exceptions, but as a rule have none of those powers. Theoretically the worst crimes they’re going to commit are fraudulent in nature and crimes of negligence.

Not that clear cut.
https://en.wikipedia.org/wiki/Banana_Wars
Why should he not use a password manager?
My trick is to only have a £200 net worth
> I'm still wondering why there is no electronic SEPA mandate.

There is! Nothing forces vendors to collect a paper form and signature. I know some countries still love paper trails (hello Germany) but even there, you'll find some businesses that don't do it. When I lived in Berlin and signed up for my broadband with 1&1, I just had to copy/paste my IBAN into their online form.

> physically mail you a SEPA mandate which you have to sign and mail to your bank.

Nope. The bank is not involved at this stage. Banks authorize direct debits by default, they don't need to know about the mandate beforehand.

> revoking the SEPA mandate requires you to contact the vendor first which is kind of silly.

It's not. It leaves the responsibility with the contracting parties, and keep banks as a neutral medium. That said, as a customer, you can revert a direct debit with a single click, and permanently reject further direct debits. It doesn't have any effect on your contract (and the vendor will send it to debt collection if it believes you're in the wrong), but you keep full control.

By the way, you can build a fully digitized billing system on top of that (there's SEPAmail in France for instance), and more and more banks support instant payments, which I assume can be used to improve the scheme.
Facebook’s Custom IPv6 Range
Of course it is, along with a lot of other front page subs that are more or less the same thing (bestof is another obviously example.)

The fact that people will look at you seriously and tell you The_donald is this highly biased fake news sub yet not mention all the propaganda subs for the left... Well this is why it's such a big deal how reddit is controlling speech of its users.
They are still publishing in other venues, like this pretty recent CVPR repo and paper.

https://github.com/apple/ml-quant
I'm left astonished at the amount of work that went into this article! Not simply its length (which is padded with large amounts of quotes) but the number of sections. I had assumed there would be an enormous comments section at the end, instead section after section after section. Oh look a randomized study he ran. Oh an enormous table of anecdotes.

Incredible.
I fail to see what this article brings to the conversation appart from an unpleasant metaphor.
1) They were disputing scrums, not necessarily communication. 2) It's hard to not think of something as failure, if it's treated as failure, which is often the case. This is like telling someone who's being mistreated in a relationship to not think of it as abuse, just think of it as your way of life.
3) Time boxing may be important if a number of different types of schedule conflicts may arise, but I think it can place an undue importance on the measurability of how something gets done, often at the cost of it actually getting done well.
Agreed. It's really about benefits vs features. Features are what. Benefits are why; why you should care. Addressing why is essential.
Sorry, I know "power alliances" wasn't too clear, but it was just a way to stress that these are in effect temporary, shifting alliances between powerful organisations (such as nation states are).

> For my part, I think the relationship is based on a general understanding that their people are alike in custom, beliefs, traditions, geopolitical place, etc

Yes, and this is what I was sceptical about. Just to give a few examples, the UK society is extremely secularised, with more than 50% of the population declaring itself non religious; nobody thinks it's a right to carry firearms; police itself is mostly unarmed; politically, there's a strong labour party that is way to the left than the US political mainstream, a welfare state and universal social security and health care. The demographic composition is much more homogeneous than that of the US, with a large indigenous population and relatively recent immigration. There is a lot of value put on tradition, social classes and social order. There is a hereditary aristocracy that holds reserved seats in a branch of the parliament. Etc.

> After all, America is the troubled child of the UK

Yes, and they share a language. But the US is an entirely different place: a whole continent with deserts, mountain ranges, tropical beaches and freezing wilderness. A huge amount of space that for centuries has attracted immigrants from all over Europe and the world; the US culture is a mix of many conflicting cultures released in a colonial setting where conquering and settling was for centuries the way forward.

Imo, the relationship of the US with the UK is mostly sentimental, while that of the UK with the US is one of subalternity.
You initial confusion and nice summary made me thought of camlistore which I looked at 4 or 5 years ago. And here it is, renamed!

This is sad because the project looks interesting, it is not the usual quick kludge or vaporware, but the bad or inexistent documentation is a terrible disservice to the project.
These satellites don't have the on-board clock capability to do very high precision, high stability timing which is one foundational bedrock positional accuracy is based on.

Just as important though is that they don't have the world-wide network of ground tracking stations monitoring their orbit. The orbital positions and velocity need to be known to within a meter or so, and not only are these not being tracked at that level, which is a very expensive undertaking, but they are also in LEO which means their orbits are much more affected by atmosphere and are less stable.
Agreed. We should just be allowed to run native apps. Yes, yes, I know that I can jailbreak my phone even today...

But store apps didn't solve the malware problem, it just handed large companies a near monopoly for software distribution. That is far worse than the threat of malware. That MS tried to release an OS where only store apps are allowed wasn't really due to security concerns. They wanted to push their ecosystem.
> I'd like to see some cutted version of html

gopher!
Well, I can certainly login, navigate to this comment, and then reply with Lynx.

It's not a great experience, mind, but it does work.
Control what to work, on for example.

These days I sometimes decide not to work on the top priority issue right now, because I suspect it'll take a few hours of uninterrupted log file reading / debugging / thinking to fix, but the day already has three different meetings scheduled.

If that's the last issue in the open sprint, choosing to add another issue to the sprint while there's still an open one tends to be a no-go, or at least causes some discussion, especially if the sprint closes without the issue being closed.

Or sometimes I simply I don't feel like working on a particular issue right now. Maybe there's no rational reason for that. I have no problem overriding that impulse if I know somebody else (either a colleague or a customer) is blocked by the issue, but if it's a case of "we have happened to include issue A in the sprint, but not issue B", having to work on A instead of B against my preference causes unnecessary resentment.
This seems like a win for the trolls. I've cut Reddit out of my diet and I'm sure those communities were deserving of the ban, but targeting specific subreddits rather than properly enforcing whatever rule they were breaking to create a toxic atmosphere seems like the less good answer of the two.
A lot of software developers spend their days basically stitching together packages and creating UI abstractions over data models, rather than writing actual logic.

Why write fizzbuzz yourself when you can just import it? https://www.npmjs.com/package/fizzbuzzify

My old job was a bit like that, I spent most of my time just creating new models and building API endpoints, or finding gems/packages/AWS services that did what we wanted to do (it did make for a nice looking resume though, with a laundry list of AWS skills). In the two years I worked there, there were only a handful of times I had to write any code that was more complex than fizzbuzz. It was an interesting product, but you could've taught a smart 17 year old kid how to do everything I did.

I'm happy that these days I'm working at a much more mentally stimulating job. I regularly have to use what I learned from my compsci degree (especially operating systems and networking), and solve complex problems that require me to actually think. It's the kind of work that validates why I went to university.
The edges of the footprint won't be bearing full pressure because they will be in tension (in fact, load distribution profiles of tires tend to look like a rounded trapezoid).

Additionally, the grooves are rather stiff and will help hold the treads - the air pressure on the inside of the grooves will be helping push the treads onto the road. Likewise, tire sidewalls have some stiffness and will also be helping hold the car up beyond just the air pressure, as you've noted in your addendum.

This is a good heuristic for approximating the weight of a car but you won't be getting particularly accurate weight measurements out of it.
> If your intention is to build a meaningful income, there are much better options out there than Patreon.

Naming at least one in the article wouldn't been helpful.
Digital Ad Formats vs. Covid-19: Where to Advertise During the Pandemic
Maybe I've been lucky up to this point myself, a kind of survival bias or something, but a "lightened" version of Scrum has always made so much sense to me when it comes to developing software.

Our requirements change, they often change daily, from forces outside of our control. Fickle clients are one thing, but even things as predictable as implementing protocols can be uncertain. Many times you'll design and implement the perfect solution to the problem at hand, and then hit a nasty bug mid way of some tool / lib you're relying on that would make you rethink your whole approach. This can drive you into a rabbit whole in itself. Its always nice to consult with your team at that point to see if its actually worth it.

As far as I understand "Scrum" is just a collection of practices that helps us actually ship something in a reasonable amount of time. Each standup can be a "battle plan meets the enemy" kind of moment. And as we know, "no battle plan survives first contact with the enemy". Yes its uncomfortable sometimes, but it should force us to deal with reality a bit more often and I think that's a good thing.

And scrum and it mutations has survived to this day for a reason. Teams that employ it are much faster to adopt to changing conditions, and thus "outevlove" the competition. I really hope that we can codify a more humane way of dealing with those problems, but at its heart, I think scrum is better suited for software development than its predecessors. We need time (and willingness) to "evolve" it as well.
"first job out of undergrad at NoName" is like 150k all-in I think. So I'm surprised if it's 10x.
On the other hand, even reputable pharmacies have fallen victim to fake drugs. For a layman customer, it is hard to impossible to judge anything here. Most still go by the "reliable pharmacy", but there are intentional availability hurdles in the pharmacy system.
In Poland AFAIK when you sign up for a card terminal the company that lends it to you usually gets a cut from the transactions (besides the bank and card companies).

And there is a lower % for normal/popular cards (Visa/Mastercard) and higher (even 4%) for Amex, so most stores just ignore it and remove the Amex symbol from their terminal.

And yet, my company provides Amex corporate card for bussiness travel, but we usually go to US, so Amex is more accepted there.
> True free speech is valued because it fosters debate, and allows bad speech to be rebutted by more speech. A marketplace of ideas, and maybe more importantly, the counterspeech doctrine, are incredibly important principals in justifying the existence of free speech.

No, you're missing the phenomenon of gish galloping[1]. Toxicity will overwhelm the community because it takes no effort to spew disgusting nonsense and spam while it takes significant effort to rebut it. The mythical "marketplace of ideas" only exists in presence of moderation, whether somewhat decentralized like HN or like the iron fist of places like r/AskHistorians. A literal free marketplace of ideas is a cesspool.

"A Lie Can Travel Halfway Around the World While the Truth Is Putting On Its Shoes"

[1]. https://en.wikipedia.org/wiki/Gish_gallop
However, I see a big risk in how this could cause a trend of less qualified (cheaper) lifeguards

A lifeguard is currently already a minimum-wage job. Also there's a ton of seasonal workers who aren't exactly that qualified to begin with.
Django test runner plugin for Kiwi TCMS – open-source test management
I agree with this point of view.
In my opinion, one of the greatest fallacy of Scrum and some agile methods is:

"Another note on breaking down tasks into chunks"

This is the management trick of "divide and conquer".

But for real good dev, that is not a good development process.

Imagine you are an experienced dev and you need to refactor a 20 files low level code to change the way errors are returned:

If you were in an agile/scrum setup, it would be asked to do that file by file, function by function, problem/code change type by type code change. And possibly not break the rest so that there is something 'runnable' at least every week or some other people can work on another file/function.

But that does not make any sense for a great dev. What you would do if you were experienced is to know the overall direction but rework the code line by line progressively, fixing side things on the way and maybe regularly fixing in other files/functions pattern that are similars. And maybe at some point decide to change again something you did until the point where you achieve your goal.

In my mind, it works more like a path searching algorithm in action.

The scrum concept is probably good for the devops/web script kiddy devs, where you just change hundreds of individual small items without too much interdependance. For example, change the style of button, reorder blocks on a page, change the icons, increase the font size.

Also, something that makes great dev become average is this concept that every dev should be exchangeable and a commodity. Dev become workers on a factory production line where they have no value than to follow process and apply patterns.

They say "what if something happen to your autonomous great dev?" but this argument is not used for the rest of the intellectual society: you don't see 2 doctors at a time, 2 lawyers for your case, 2 CEO in the company, 2 main architects. This thinking is just applied to low level replaceable workers.

Normally, if you lose a great dev and you find another great dev, the new one should be able to understand the problem and the code in a short time and be operational quite fast.

One example we can easily see of efficient dev are the great open source projects. Most of them were not created and led by an army of dev clones but by a few efficient ones: linux, python, php ... In these cases, most of the time we don't consider people to be interchangeable. Some people are keys to topics/code/features and that leads to great dev. But in case of problem, there is almost always someone smart capable to take over after a short time.
Agile builds on the premise that developers like to build. That we self organize our teams and don't like slackers. Bring transparency for business so it can trust us. Give estimates and accept priorities. Ship from time to time so all can see that process works.

It is really easy to screw. I've seen far to many broken versions. Community building is harder than management. And for management there is no benefit beside budge. So they say SCRUM and change nothing but cosmetics. It sells.
This rings very true. I'm a night owl and in the beginning of my career I worked in mostly 13-21 bracket, with strong preference for hours after 17 when office got quiet. It was great, but at some point it started to impact my life very negatively(days just pass and you do not do much beside work). Early mornings are the next best thing. You get quiet, you can easily focus, you're rested and when the day really starts you have something done already, which significantly reduces stress for me. Definitely recommend to everybody.
I've also seen it fail the other way where the Skunkworks becomes the preserve of "high achievers" not producing a lot that's useful. Almost every 'Office of the CTO' I've seen has suffered that failure mode. Lot's of things get built but none are more than fluffy experiments and there's no path to actually putting any of those things into production. Once in a while they'll be forced through and the production team has to spend a lot of effort fixing and making the project actually work.
On the other hand, having a single abstraction / entry point makes it easier to implement generic sanity checks. If you add a check for that kind of problem at the right layer, it will cover other / future interfaces. On the other hand, if you use ad-hoc system calls, any mitigation or fix will typically only cover that one specific call.
Any legacy system - but your skillset then becomes tied to domain knowledge. This can be both good and bad - the good is your valued as long as the system exists, the bad is once the system is replaced you can be on a rocky path
+1 to this. Chapo wasn't bad at all, in terms of breaking actual rules. I saw people on the announcement thread claiming it was full of tankies, and that was reason enough to ban it, but it really wasn't. You wouldn't get very far on Chapo by unironically talking about what a great man Stalin or Mao was -- though, guillotine jokes, including applying them to the necks of landlords, would certainly get you upvotes.

I never saw any actual brigading on the sub itself. Others talk about "organizing brigades through Twitter," and I think it's kind of BS to punish people for that. Reddit doesn't get to police Twitter, and vice versa.

Never saw any actual advocacy of violence against any specific person, either. Sure, there were "kill the landlords" type jokes and memes, but the closest I think I ever saw it get to actual incitement of violence was stuff like "Kissinger needs to fucking die already," or "I would prefer that Trump exit the White House feet first, in a box." You can call that whatever you like, but it's certainly not advocating violence against anyone.

Meanwhile, there's literally a Stalin meme on the front page of r/fullcommunism that says "death to capitalism." Then, there's r/latestagecapitalism, which is a toxic shithole of a sub where you literally can't say "that idea is crazy and will never work because $REASONS," because they have a blacklist of words that are "slurs" of one sort of another that they don't publish, and which will get your post removed if you try and use them.
Thank you so much. Going to try this one, very useful tool.
Die with Me App
Robert's Rules of Order (1876)
apple fanboys will accept anything from apple. No headphone jack? it's an improvement! w3 spec not implemented? they are working on more important features! antenna stops working if you hold the phone wrong? I like it that way!
Agree. I'm getting tired of everyone saying that everything in the 90's was super duper fast and now everything is sluggish with RAM-hoarding tendencies
I've recently being using the web version of sketchup having used the desktop version several years ago. I was not hopeful when starting but after a few hours I'm impressed. I've found the performance good and didn't notice any slowdown. It's the first webapp I've seen that I've though this might actually work.
I’d be interested to see if the author will get as much exposure to new potential subscribers without a platform like Substack of Medium promoting it. IMO, it’s always been the community aspect of these platforms that keep the authors locked in rather than the technical difficulties of setting up your own website.
Depends on the model. E.g. image enhancement or super resolution models are sensitive to the camera model and can be trained to fix artifacts introduced by specific cameras.
I am not arguing that unit tests are not valuable for the reasons that you have given, just that they seem to be used in place of decent abstractions these days. I have worked on well abstracted code without unit test and badly abstracted code with unit tests. The former is far easier to work with and bugs take a lot less effort to fix - that translates to costs in developer time.

> This is about cost optimization to some extent.

Is all the complexity and developer time that is required with Kubernetes really cost effective? We added it at my work and it took around 6 months of developer time from what I could tell (it wasn't me who set it up). Now we have to debug it and none of our team is an expert, so lots of guesswork and googling. Using number of small pods has given us a lot more problems than one big machine. If you are running out of memory because of a large upload, restarting a pod when it crashes doesn't help you.

Kubernetes has lowered our cloud costs and given us high availability, but it has increased development time in a number of ways. Maybe as we get more experience it will get better, but so far I would not say costs have been optimized as a result.
In my experience writing (at least writing fiction) consists of two different activities: the writing proper, in which you produce text, and the editing, in which you mostly get rid of text. Think of the editing phase as liberating the statue from the marble, and the writing phase as producing the marble.

These activities, since they are so different in nature, are best separated in time and space and tooling.

I produce in the early morning, sitting at my dining table in the living room, using a pen and paper. In the early morning your dreams still linger and your critical faculties are not yet fully awake. This makes it an ideal time for just producing stuff. I take this seriously in that I do not even allow myself to cross out words. Just keep on writing, and sort it out later. Later on the day I edit, sitting in my study and using a text processor.

As a side note, I would not recommend this practice for writing code.