skysight-inc/HackerNews huggingface dataset:
Just yesterday, my team officially agreed to discard the last vestiges of our ailing Scrum practice. (Corporate requires us to use JIRA, and JIRA forces us to organize things into sprints, so there's that, but, even there, we've agreed to just do what we're going to do and pencil whip things to make JIRA happy.) I'm optimistic. The new plan is a loose high-level structure and a lot more room to experiment with our process and find what feels good. And a renewed commitment to do so. And a fresh morale boost. The transition will be difficult, but we will learn much and be better for it.

I personally tend to defend Scrum as being overly maligned and often blamed for the consequences of misapplications. But that last sentence is a double edged blade. The truth is, the model is brittle and internally unstable, and it's difficult to get good results without constant vigilance to ensure the rituals are being performed correctly.

(There's even an entire role just for doing that. It's the one with Scrum in the name.)

And that's getting tricky in an increasingly distributed world. Online ticketing systems, for example, practically beg you to overload the tickets with extraneous clutter and paperwork that bogs you down. But you can't use the (greatly preferable, for Scrum purposes) sticky notes on a wall if you're not co-located. Story points don't work with distributed teams, either. They need planning poker (or similar) to function properly. But planning poker is exhausting, and videoconferencing is exhausting, and so nobody has much appetite or endurance for the exercise in self flagellation that is Zoom planning poker. So we all mentally and emotionally check out, which completely undercuts the effectiveness of the practice.

Also, Scrum is just too meeting-heavy. We're spread across six time zones. We have precious few hours in the day when we can all meet with each other, and we simply can't afford to continue spending them all on so many synchronous rituals.
oops didn't realize until it was too late to edit that the layout got messed up...

Bowline Knot

Truckers hitch Knot

Half Hitch Knot

Uni-Knot (fishing)
I've noticed a related effect, where every problem discussed in a retro has a "process" solution, because the team's own processes are the only thing the team can fully control.

This can lead to both a constant churn in processes and a piling on of additional processes, which bog the team down with an explosion of on-call-like rolls that get rotated through team members.
Just soup money.

I ain’t betting on cake.

Making do is in my control.

Life is short.
…kiiiiiind of?

The thing is, I’ve made a lot of things that didn’t jack crap. I launched four apps before I made one that mattered. I wrote on my blog for nearly a decade before I could launch a book that I sold.

But on the other hand, I know several indies who hit it right out of the park. It’s so hard to say. It’s part marketing, knowing where your audience is, making something actually good and then luck. I think that there is an art to all of this, but having been on both side of the fence, I think dumb luck does factor in.

Also, quick story - an app I made in 2012ish, I thought for sure was gonna do great! It was a Christmas list app, and I launched it in November. I woke up the next day and I saw…one sale. Later that day, I found out it was my boss’ daughter who bought it. Haha, so, you never know!
> They create the headache in the first place

Only if the console wouldn't completely sell out every time without the scalper. But it would.

So the scalper provides a service to consumers with more money by allowing them to avoid the hassle of competing with lower classes for popular goods.
I frequently use long options when available, and continue long lines using \. You’re usually only writing a script once, and being as descriptive as possible is usually a benefit. It’s not like most of the time is spent on programming is typing.
AWS network firewall loaded with suricata rules?
Very interesting idea to use GPT3 as a starting point for rewording text. I can see it being an effective way to break writer’s block.
Ban outgoing encrypted traffic. Terminate TLS at the load balancer.
I started skimming for the term "animation" and my first deep dive ended with a Greensock wrapper:

> I use GreenSock for most of my animation because it makes sequencing animations a breeze and when working with SVG, I know I can rely on the transforms working consistently cross browser.

I mean, caniuse[1] shows SMIL support across all modern browsers. So if an SVG guru is using a wrapper lib I'm guessing it's yet another case of the web having an API that is "off-by-one" in the usability dept.

So what transform dragons lurk in SMIL (or any dragons for that matter)?

1: https://caniuse.com/svg-smil
I agree about the major first dotcom bringing people who didn’t care for the values and culture of the city but disagree about the roughness. The mission and the part of soma near the old trans bay terminal were pretty rough. People got mugged in broad daylight kinda rough
We've solved that as a society.

People can affix fake sirens to their cars and if they blare them at you you should pull over... after the incident society then throws an incredibly harsh penalty at the offender.

To make sure things run smoothly it benefits society to never doubt or question whether people who say they're police officers actually them - they might have something incredibly important to say (Like, hey, there's an active shootout ahead - please don't keep driving and get yourself injured).

If you as an individual create some funny gag to fake out autonomous vehicles into thinking that you're a cop whether you cheekily do it with "TOTALLY NOT A COP CAR" written on the side to get a laugh or not... you're almost certainly going to be charged with a felony crime.
Completely agree. It's the mindless nature that's the red flag here.

I met a guy who came across as quite fluent in these meetings but quickly you would realise he didn't know what any of it meant - it was like the Chinese Room.

With that little connection with anything it was impossible for people to pick up basic errors, it was just rote learning and soon it spread to others; no one was equipped to make sensible suggestions as they couldn't see the big picture and didn't really know what the things they did were actually for let alone the "why" ("Oh, so we're building a ship... to float on the water? Thanks!", turns back to keyboard, resumes vacant look)
I worked for JPL/NASA on contract for a few months, the place is packed with Caltech grads, but most of them performed much like any science-y person in a big bureaucracy. This probably says more about what you're trained for vs what you do -- I mean, how many working programmers need to know what Bessel functions are? The answer is 0 because those analytical jobs are inevitably farmed out to experts anyway. My own interpretation is that there's a certain (middling-high) amount of capability you have to demonstrate, and once you've done that the extra doesn't matter.
Ebook: https://archive.org/details/TheAshleyBookOfKnots

The ABoK was something I always wanted to see, but never bothered to buy... until I found that PDF. Scrolling through it finally convinced me to buy a hardcopy. It's one of my favorite books to just flip through. There's more than just the knots: the history and the anecdotes are a fascinating window into the past.
It stopped because it recognized that it needed to stop to let an emergency vehicle get past it. Unfortunately, it stopped right next to a double-parked garbage truck in the next lane. No one had programmed in a set of contingencies for "stopped to let something pass, no room for it to pass". This is one of who knows how many contingencies it doesn't have a solution for which is why, in my opinion, this kind of thing will be quite common for a long time until enough events like these are found and software is changed to handle them. I'm hoping that none of these kinds of unanticipated events will cause fatalities, but I'm skeptical that will be the case.
That's just what garbage trucks do, pick up garbage. Typically, they need to stop in order to achieve that. Thankfully, there are two lanes, so with some negotiation, humans can work around that fact...
Don’t see Paramiko in the list of GNU packages.

https://www.gnu.org/software/software.en.html#allgnupkgs
How to build your own “DoorDash” app
It is not very reddit like to charge money to post.
Yup. That's considered an acceptable trade-off in the circles I'm talking about.
I see this argument constantly, that the streets run brown with human feces. I worked in SOMA for a decade, I would commute every day on BART and would walk from Montgomery Street Station or Embarcadero or Civic Center or 16th Street to wherever my office was at the time (different companies, different offices).

SOMA was always pretty clean, Civic Center a bit more hit or miss, 16th Street was generally a bit dirtier and rougher.

The number of times I encountered human feces though was very low, like not even a monthly occurrence. Now I'm sure there's parts of San Francisco that are worse than others, and the walk from 16th Street BART to Potrero Hill would take me past plenty of homeless people camped out on the sidewalks, but I rarely if ever encountered human feces.

But every. single. time. San Francisco comes up, it's the same tired line, "Oh I couldn't deal with the absolute deluge of human feces" which like cool, neither could I and it was fine because what the heck is everyone talking about. I'm not going to claim that every sidewalk and roadway is completely free of poo, but as someone that managed a team of people and would frequently go for walking meetings all around San Francisco, it was never my experience.
I have Ubuntu running in Parallels on an iMac, retina display, and the Ubuntu fonts seem noticeably less "nice" to look at than the Mac. Now, I didn't take the Pepsi Challenge here, i.e. a blind test, so it might just be internal bias -- but to me, the Mac fonts are noticeably better.
I agree with a lot of what you are saying here.

> why are we reviewing code in the first place?

It being part of engineering culture is spot on. I think of it as two things: (1) quality gate and (2) knowledge sharing. Because of (1), by default reviews can feel a bit like submitting homework - not all contributions are of the same risk level but they follow the same process.

The idea behind Codeball is unassuming - identify and approve the bulk of easy contributions so that devs can focus their energy reviewing the trickier ones. This is can be especially nice in a trustful environment, keeping the momentum for devs to ship small & often.

Another thing is - models can incorporate a surprising amount of indicators, for example, not just the outcome of the PR but also what happens to contribution after merging (was the code retained as-is or was it hot fixed a day later etc).
If you were determined, you could probably produce a gas that would kill 19 students in a minute with the things you could find in a high school chem lab.
Oh, how could I forget about the fall of Hong Kong?

"An unarmed people are slaves, or are subject to slavery at any given moment." —Huey P Newton
The definition I found of sarcasm is the following:

"a sharp and often satirical or ironic utterance designed to cut or give pain"

I think the response I'm complaining about is satirical, so I think it matches sarcasm by this definition.

Anyway, even if hadn't been sarcasm, technically, it seems mocking and unkind. And it's not a big deal, but I think my response of "I don't appreciate that" was pretty tit for tat.
I imagine that if civilization reaches a developmental limit in access to natural fresh water, migration will happen to somewhat developed coastal areas rather than the Mojave Desert.
5 seconds is a very short amount of time. Humans are pretty bad at quickly solving for and safely executing an unusual response to a scenario they’ve never encountered.

I would hope that after coming up with the strategy to reverse that you’d take most or all of 5 seconds to confirm there were no obstacles behind you. It may take you 2 seconds to realize the fire truck is stuck unless you move, 2 seconds to conclude you can only help by reversing, 3 seconds to check your mirrors, 0.5 seconds to shift to reverse, a couple seconds to look at the backup camera to check the spot not visible to the mirrors, 2 seconds to move the car 40 feet, longer if you have to check for cross traffic in the intersection.

Aviation research points to the effect of startling to have a negative effect on decision making quality and speed for up to 30 seconds. That’s for trained, generally fit aircrews.

Quibble with the times, but I doubt you get to a “most people would complete the task safely in under 5000ms” conclusion.
You would think but just in 2019 I’ve run into places where pay is by app only, restaurants where you order/pay by scanning QR code, etc. honestly my thought on the way home is that China is way ahead of us in terms of convenience technology on phones (for better or worse)

With the pandemic US has caught up a lot though
Rather than becoming this over time, Scrum slotted into existing teams and practices that were already heavily into rigid project management. The same teams that adopted Scrum were previously using Waterfall or 6-Sigma or some other such prescriptive framework. Agile showed up, got a lot of buzz, and then Scrum came along to sell the buzz to big institutions with entire departments of professional project managers.

Were the creators of Scrum hopefully trying to introduce flexibility in the guise of process, or cynically cashing in on a trend? I don't know; all I do know is that Big Software switched from $old_process to Scrum around 2010-2012, and medium-sized companies seemed to follow in the middle of the decade.
And now we’re abused by velocity chart, retrospective about our failings, continuous change because we’re agile, under pressure all the time because of the two weeks « sprint » which end being a disguised death march…

So how is it any better?
On top of that, they’ll be able to do sub 4s 0-60, silently
AWS is a totally different beast and you'll have other useful tools in the stack there. Cloud trail, guard duty, VPCs, proper least privilege and IAM rules, etc. What are you looking for in a snort alternative? It is the open source standard; though you might also look at suricata. Perhaps a whole security stack like security onion which incorporates snort and a lot of other tools. Might be overkill for what you want though.
I followed your twitter username and found your website... the availability page is a work of art.

I especially resonate with your feelings on front-end / backend and I really like the way you make it sound vs my usual spiel about "I like backend because I hate CSS"
That's a fine micro-comparison to consider, alone!

But also, what if this is a rare situation where the autonomous car completely fails compared to a human-in-seat? But, even this failure still resolves in under-a-minute. Or, worst-case, approximates the (quite-common) case of a breakdown or human-accident blocking traffic, in a manner that takes tens-of-minutes to resolve.

In that case, who cares that we've found one narrow failure? Humans show impatience, poor-judgement, bad exception handling, recklessness, and so forth at ample rates across many road interactions. It's the net total of blockages by autonomous cars, in count & duration & severity, that matters, and specifically whether overall they do better or worse than human drivers.

That net comparison is the most important consideration.
Thanks for the first-hand insight into Aptera. Sounds like vapor-ware. For the Nissan Leaf, looks like the depreciation is still the worst, at least according to:

https://caredge.com/ranks/depreciation/popular/5-year/worst#...

...would you say the depreciation was justified? Maybe mostly because of the battery range reduction? Did it start to need repairs or were other things generally wearing out? Other maintenance higher than expected? Do you think the $7,500 tax credit for new Leafs (Leaves?) is/was playing a part in suppressing costs for used Leafs? (as in, why by a used one, when you can get a new one with a $7,500 discount). I guess probably not, since that list isn't dominated by the other EV's eligible for the tax incentive. What was the range when it was new? I see this site says it was ~100 miles:

https://www.cars.com/research/nissan-leaf-2011/
> There are not uncountably many

OP was obviously not using that term mathematically (i.e. the cardinality of the power set of natural numbers), and obviously meant something in the neighborhood of "effectively not countable". And, again, in all but the formal mathematical meaning of the word "countable", many things are not countable (e.g. no one will live long enough to count all the natural numbers).

In the real world, assigning an ordinal number to an object/event/thing has a nonzero time cost. And accounting for every situation in software has a much greater cost.

> If the rate for autonomous vehicles is already below that of humans, or rapidly headed there, that's far more important to note than to theorize about other corner-cases.

Okay, but dangerous human drivers get systematically removed from the streets. Are we doing the same for self-driving cars? In this context, does every Tesla count as the same "driver"?

Maybe all Teslas should have their autonomous driving centrally disabled every time one causes an accident, or breaks a law, until that specific issue is fixed. But it would be impossible to run a car company that way, so of course that takes priority over, say, keeping innocents alive, right? /S
Netherlands, 300 down 30 up, €53/mo (internet only).
Taxation as a service?
I’ll take “nothing” over scrum anyday.
I will communicate with my colleagues and stakeholders and deal with what needs to be dealt with, vs more meetings with religious fundamentalists who don’t actually appear to code much.
I remember getting a new computer with 320 gigabytes of storage when I went to college. Someone asked me what I could ever use that much space for.

Still, 30TB seems like an ocean.
I think it is as simple as an algorithm that rates how frequently new updates show up vs how many people visit a site.

If you rarely make updates to your site, Google crawls it infrequently and new things won't show up very quickly.

But if you do have frequent updates and lots of traffic, like any popular forum style site, you will get lots of crawler traffic. And I would bet the algo does the same for all endpoints on a site. So the "about us" page on a popular site probably ends up not being crawled nearly as much as the new threads page.
Usually you don't want your electrical wires to be taking any serious mechanical load, so that disqualifies most knots who's entire purpose is to take some sort of load.

That being said check out the underwriters knot, which is specifically designed for strain relief: https://en.wikipedia.org/wiki/Underwriter%27s_knot
All measurements are estimates, but sometimes the errors look like "we have a machine that spits out 4 all the time" and other times they look like "I saw two people, but I can't rule out the possibility that I spontaneously hallucinated them."
> It does seem like the car "acted reasonably"

I would firmly say that it did not act reasonably. Blocking the other lane of traffic is the second worst action I can think of, only behind ramming into the emergency vehicle. It would have been better to ignore the emergency vehicle and continue driving, which would have at least cleared the jam.

I worked in the space at one point, and I would put the issue down to autonomous vehicles being trained entirely to keep themselves safe. E.g. they know to stay a certain distance from other cars, but they have no concept of "could another get around me?". A similar example would be parking. On a street without lines to mark spaces, I would not be surprised to see an autonomous vehicle park in the middle of a space large enough for 2 cars, preventing someone from using the rest of the space. Another would be opening space for someone to merge. I don't think that's something they ever do on purpose.

We're teaching them to not hit things or get hit by things, rather than teaching them how to drive, which is a far more nuanced skill. The same thing would have happened with 2 autonomous vehicles, because neither even attempts to understand what the other is trying to do. They would just deadlock until the garbage truck moved.
There are services which give you a one time CC number such as privacy.com. I'm unsure how shipping address might also get similarly obsfucated (po boxes?).
Sounds like they came first:

> I settled on adapting one of my more popular [blog posts][2] that I keep updated through each version of iOS into a five book series
That's a good selection :^)

This pandemic I started learning about knots as well but IMHO one end up using a very few selection that works for most cases. I admit sharing small selections may not be that useful because people have different life styles but there are some that are almost always useful.

I'd like to add a few 'quick releases' to your selection like the Painter's Hitch and the Highwayman's Hitch. I personally use the Painter's hitch and the taut line hitch to secure my motorcycle's cover on windy days, pretty fun to use!
This is both the good and bad of living in area like the Bay. I'd find the idea of going in an evening a week with a tedious drive to do work-related stuff tedious at best.
A Face Search Engine That Anyone Can Use Is Alarmingly Accurate
> Funny, i think (but am not arguing i'm correct) it does change probability when the doors change. As i explained[1] in the sister post.

The probability that you have the winning door does not change when the 98 doors are opened. The simple reason for this is that it is always possible to open 98 doors without the prize regardless of which door you initially chose.

So it provides no extra information about your chosen door. But it does provide information about the single remaining door because in most situations, that specific door would need to have been opened.

> To look at it differently. The doors changing probability to me sounds like.. imagine two people, the PersonA has this primary scenario. They had 100 doors, chose one, and are then asked if they'd like to switch. PersonB then is asked the second question, of the 2 doors, which do they want? PersonA and B are standing next to each other. The doors are the same for both of them. Why would PersonA have different odds than PersonB? And how could PersonB's odds be any different than 50/50 with no prior history of the doors?

If PersonB saw everything happen, they have all the information PersonA has and therefore can make the same choice (99% correctly).

If PersonB came in after the door was chosen and the 98 doors were opened, (assuming they can't tell which door PersonA chose) their chance of picking the winning door is indeed 50%.

When thinking about probabilities, it is very important to think about the information that each person knows. The game master knows everything, so if they were playing their own game, they could win 100% of the time. PersonA can only win 99%. And PersonB can only win 50%. It all depends on what information you are given.
In my experience, Scrum is something leadership and project managers never really commit to ("agile with a small 'a'") and never really adhere to its principles. When it inevitably fails, they blame agile and go back to waterfall and wonder why engineers are unhappy.