HNHacker News
TopNewBestAskShowJobs

ohthehugemanate

3,255 karma · joined July 20, 2015

submissionscomments
ohthehugemanate··on Virtualizing development environments in 2023
TFA goes right into the core complexity and misses it.

"Dev environment" depends on what kind of work you are doing. What a web developer needs is worlds apart from what a driver developer needs in terms of capability, resourcing, isolation, and rebuilds. Trying to offer a single environment for anyone who builds anything using a computer, is analogous to a single environment for anyone who uses a screwdriver. An electrician is using the same tool, sure, but they're doing fundamentally different work from a kitchen installer or a plumber and have vastly different needs. The single environment with all the capabilities that any computer developer needs is called a "computer."

IMO this is the genius of VSCode remotes. They built a core capability of running the bulk of the IDE "somewhere else" with just the display layer on your local machine. Then they can allow the developer to choose if container(s), VM(s), and local or remote are right for their case, without having to learn new tooling. They can even let you choose if "owning a computer" is required, or if a web browser is sufficient.

ohthehugemanate··on Oregon decriminalized hard drugs – early results aren’t encouraging
I have heard that Portland is such a mess because three factors hit at once:

1) the police stopped arresting for small possession, but no social services were funded to fill the gap for helping/making people get clean. Churches can only do so much.

2) the war on fentanyl pushed that drug market into homemade from ingredients anyone can get on alibaba... greatly increasing access.

3) the unemployment crisis.

I can vouch personally for the massive number of people who appear high on fentanyl, specifically. Thank goodness it's not an aggressive drug. Can someone with more context and subject expertise comment?

ohthehugemanate··on NASA mistakenly severs communication to Voyager 2
honestly I was just shooting for easy round numbers. "More than 43x the speed of sound" doesn't have the same ring to it. And besides, as we all know "technically correct is the best kind of correct!" :)
ohthehugemanate··on NASA mistakenly severs communication to Voyager 2
It's about 3.5 trillion NFL football fields away. 15km/s is about 33,000 mph - more than 10x the speed of sound, and faster than a bullet. Does that help?

We are talking about distances that are so big, there is no comparison that makes sense. Nothing else IS that big. The numbers are literally "astronomical". If you're struggling to wrap your head around it, you're doing it right.

"Space is big. You just won't believe how vastly, hugely, mind-bogglingly big it is. I mean, you may think it's a long way down the road to the chemist's, but that's just peanuts to space." -- Douglas Adams

ohthehugemanate··on Vscode.dev: Local Development with Cloud Tools
I don't dictate IDE choice on my teams, but projects definitely end up with a very convincing "happy path". 75% of the Dev market uses vscode anyway, so I never got resistance to that level. And once .devcontainer is revisioned people would have to work to AVOID using the convenient, perfectly configured environment so no resistance there, either.

At that point, GH codespaces is a convenience tool, icing on the cake for when you want to make a quick edit during PR review, or when you're away from your desk. I saw devs use it that way (and did so myself) with no resistance.

But I have big caveats to my experience:

1) my only teams since this whole toolchain came into existence were joint microsoft/customer "build with" teams, so they were more positively predisposed to MS tooling than average.

2) I've never seen a team that uses web based codespaces EXCLUSIVELY.

Even though I know the difference between vscode-in-electron-with-remote and vscode-in-browser-with-auto-provisioned-remote is academic (and performance is probably better in the browser!)... I would still struggle with how ephemeral web apps feel to me on a gut level. Plus, as an old person I am uncomfortable when my toolchain isn't 100% local. I have nothing against the children with their cloud-powered toolchains, but it's hard for me.

<Principal Skinner on the playground, the children who are wrong>

ohthehugemanate··on Vscode.dev: Local Development with Cloud Tools
Oh yes I know. But the split VSCode process is where a key part of the value lies for me. Not just that my entire toolchain is there, including tests, etc... we've had that for years with vagrant, for example. But also that the actual IDE is running there, and all contained in the repo, is awesome. I never achieved that level of seamlessness and consistency even with vim.
ohthehugemanate··on Vscode.dev: Local Development with Cloud Tools
My only complaint about vscode remote containers and codespaces is that they ruined me for every other IDE, especially in a team context. I can never go back to managing dependencies for every damn language/version on my local machine, just to be able to run the linters/tests/tools I need to develop well in that language/version.

With a team, I know that everyone has the same versions of everything unless they've specifically created an exception. New team members start up the IDE with all their support tooling already in place, automated tests runnable, etc etc.

Paired with codespaces, when I need to make a quick edit as a part of PR review or just to tweak something, instead of the GH text editor I get MY IDE, already configured the way I like it with an identical run environment.

I've used many IDEs over the years, from tricked out Vim to eclipse and jetbrains... but codespaces killed them all for me. I'm sure it's not for everyone but it is amazing for me.

ohthehugemanate··on What's wrong with enterprise Linux
Oh my sweet summer child. There are plenty of enterprises still on RHEL 6, paying extra to keep patches coming. I bet there are still some on RHEL 5. Large, global companies. And of course there are many environments where software and hardware stay frozen for years. Telecoms, factory floors, automotive, finance, disconnected edge devices of all types... they test the absolute crap out of those systems, and pay for every certification availabl, and then leave them running for a decade.

The ability to stay abreast of major version updates is a wonderful attribute of many environments, but definitely far from all.

ohthehugemanate··on Darmok and Jalad on the Internet-The Importance of Metaphors in Natural Language
I love that episode, too. I don't recall it ever being clear if the references were literal historical, mythical, or what. And anyway, when we make references to history we are necessarily using our mythologized, cultur-dependent version of it. You refer to Napoleon the myth, more than Napoleon the human.

To me, the point is using common cultural stories or referents - historical or fictional is not relevant.

Ron Paul is a real person, and he did raise his arms in a famous historical moment. I think he even said "It's happening". But just like Bismarck with a bloody uniform, the point is not the literal reality but rather what that moment signifies in our common cultural frame of reference.

From another angle: Bismark meant something very different in 1870 Prussia, 1918 USA, and 1937 Germany. In fact even with a historical figure or event, you are stuck referring to the contemporary cultural associations.

I think this is actually wgat we do when we drop gifs into conversation: we pull up a moment from Friends or Seinfeld that all participants are familiar with, to lend their emotional tenor to the conversation. And if you don't get the original reference, you very quickly pick up on the meaning. (I had no idea that it was Drake doing the clever idea meme, but I knew just what that reply meant!)

Bottom line, references to history, to memes, or gifs are fascinating ways to communicate based on shared culture and I enjoy using them.

Thank you for coming to my TED talk.

ohthehugemanate··on Darmok and Jalad on the Internet-The Importance of Metaphors in Natural Language
In the right company, i've taken to Darmok descriptions of the gif or meme I would use. The results have been... Spock on the bridge, his eyebrow raised.

I wonder if this is damaging language or communication. A dog with coffee, its home in flames.

But it is a kind of communication in which the internet generations can all share. Homer and bart patting the couch, their faces shadowed. But this could be it: the way the internet and memers take over how we communicate! Ron paul, his arms wide, background flashing!

ohthehugemanate··on Self-hosted photo and video backups directly from your mobile phone
I have the same need... I use Nextcloud for many things (including photo upload) but I can't stand their photos app. I use photoprism for the photos app and I love it.
ohthehugemanate··on Get a personal teacher
A great conductor once said to me, "I really like your new voice teacher, he really knows what he's doing. Not like your last voice teacher, he didn't know anything. Your first teacher was on the right path, too bad you didn't understand the message yet."

I heartily agreed the whole way through, until he revealed he had no idea who any of my teachers were. It's just that everyone feels that way.

The lesson is: blindly following a series of teachers like oracles is the way of the beginner. The path of the master is accepting that YOU are your own teacher, and everyone else is just providing tools.

ohthehugemanate··on I give up on free software phones (2019)
I can't believe there's no mention here of sailfishos.org, which runs great on Sony xperia devices and even runs android apps. It's Linux (Intel/Nokia Meego, specifically) with a proprietary UI.

Would I prefer an OSS UI? Yes. But for a real, viable duopoly alternative it is worth the sacrifice to me.

ohthehugemanate··on Software effort estimation is mostly fake research (2021)
Not EVERY company. Just the ones that don't understand how estimation works... and unfortunately in software, that's still a very very common case. In more established kinds of engineering it works differently... which gives me hope that eventually our industry will understand too.
ohthehugemanate··on Amazon Backs Out of Climate Pledge, Deletes Shipment Zero Initiative Blogpost
I think microsoft is the only large hyperscaler that seems to take this as more than a shallow PR push. Their goal is carbon zero by 2030 - not net zero, but actually removing as much carbon from the atmosphere as they put in. They pay for actual carbon removal and help develop that tech in order to get there. And their targets are all three classes of emissions (ie including indirect emissions) which no other tech company even talks about. That's recognized within the carbon monitoring industry... I think they're on the CDP A list for carbon for the third year in a row now? (Amzn and goog have never been there)

On the other hand, I don't see people in tech making buying decisions based on this. Why does your company use AWS or GCP, and did the "nothing more than PR" state of their climate commitments even come up in that decision?

Complaining on the internet is fun, but changing buying habits is better.

ohthehugemanate··on Rules of thumb for software development estimations
Sounds like maybe your experience is with places that do this backwards? Velocity is a backwards looking measure. It doesn't commit your team to grind until that's done.

We get as much done as we get done. We take a guess about how much work that will be at sprint start, based on previous average, and make sure that much work is well understood and prioritized. But tasks turn out to be easier or harder than expected, people get sick, shit happens and you end up accomplishing more or less than what you expected. At sprint end you measure what you actually accomplished, to help predict the long run timeline of the project and maybe to get a better guess at how much work to prep for next time.

There should be no time or "amount done" pressure on the engineers. We measure the actual throughput and use that to inform management how long the work as defined will probably take. If management doesn't like that assessment, they can manage the situation by adding engineers or reducing complexity/scope. If you really like playing with fire you could let them ask to lower quality standards, too.

ohthehugemanate··on Rules of thumb for software development estimations
Great response.

Part of the point of estimating difficulty is exactly to reduce the one-sidedness evident in time estimations. Human brains are much more accurate and consistent with effort estimation than time. It's still very likely a beta distribution but for the level of accuracy we're talking about it's just fine.

We should probably clarify the "bar" here: the very best time estimators never beat about +30% delta from actual time. (Note that I'm not using +/- intervals because it's only ever +). So how many points (effort/time ratio values) does it take for convergence to get your effort/time ratio mean within 30% of the peak of the curve?

ohthehugemanate··on Rules of thumb for software development estimations
How many has your team completed on average in the past sprints?

It's not pretense. WTF should an engineer care about time? An engineer has to care about Done Right. It takes as long as it takes. A PM cares about time, and they can looks at the past history of similar tasks to estimate it very accurately. The abstracted "effort" unit is a way to identify "similar tasks".

It's also very well demonstrated that human brains suck at estimating time. Estimating difficulty is way more consistent.

But if you hate thinking in terms of complexity you can do the same thing by making sure your tasks are evenly sized, and averaging task throughput over time. Or if you also hate your pm you could tag similar tasks and have them do the leg work without the math to help.

ohthehugemanate··on Rules of thumb for software development estimations
No, they are not weeks, and the minute "we all know it" you are fucked.

Engineers are not concerned with time. They are concerned with feature completeness and quality. They do not care how long a task takes, only that it is done Right. When the PM asks how hard it is, that's their only consideration.

The PM only cares about time to make accurate predictions for the rest of the business. A given task takes as long as it takes to be done Right. If the business wants it on a different timeline, the business has to redefine the task, or redefine Right (ie skipping tests or doco).

Research bears it out: human brains suck at estimating time, and are much better as soon as you talk in terms of effort.

BUT if you want to insist on brute forcing through our cognitive biases, I have good news: you can do almost as well by tracking the relationship between "developer time" and "real time". You're still dealing in abstracted units, of course, but you can still pretend you aren't, which is the important thing.

ohthehugemanate··on Rules of thumb for software development estimations
The problem in your story is a non technical boss making time estimates/demands. If that's gonna happen, the developers shouldn't bother with estimates at all because no one is listening. They can just go on missing the boss's fantasyland deadlines and save themselves the trouble.

If the boss wants to know how long things will take, they have to ask the engineering teams. And the most accurate way for an engineering team to answer is with a track record of abstracted unit estimations and how long they took, to predict how long the abstracted unit estimation in question will take.

And when the PHB says "make it two", the engineers can only reply "ok, tell us what features or standards to cut." No different than wiring a house: we can finish faster if you choose some rooms to skip, or some safety standards to skip. But those are the boss's decisions, not the engineers.

BTW I agree with the responder who says quit from those environments ASAP. I don't know how engineers can overcome a dysfunctional business lead like that... and that kind of business lead is often an expert at making sure the repercussions land on someone else. Case in point, by asking you to finish faster he is tacitly asking you to skip capabilities or safety checks... and that way you're responsible for the fallout.

ohthehugemanate··on Rules of thumb for software development estimations
> The whole team was really just doing hours/days -> points mapping in their heads during estimation anyway.

This is a common story. But because of the calculation step, your PM was still mapping estimated time units to actual time consumed, and using that mapping for predictions. So you were getting some of the benefits of an abstracted unit (accuracy, averaging in unexpected events) without the stress reduction or focus on quality over time.

But if it worked for your team, I would advocate to keep it. Human groups are hard enough to coordinate as it is, there's no need to hew to a dogma.

ohthehugemanate··on Rules of thumb for software development estimations
Maybe you missed the part where I explain how PMs translate to time for business planning. Yes that is absolutely necessary.

And yes it is an abstraction, which is the whole point.

Human brains are extremely bad and inconsistent at estimating time, and much better at estimating effort. So you abstract and let them estimate in the terms they're better at. Not to mention, the abstraction means you average in unpredictable disruptions like illness, windows updates, and other events. Abstracted unit estimates are demonstrated to be much more accurate than (not-abstracted) time estimates.

ohthehugemanate··on Rules of thumb for software development estimations
I'm so happy to see someone who has actually read some of these studies on here.

There are only 2 reasons to do the translation behind peoples' backs AFAIK:

1) also from kahneman et al we know that humans are bad at estimating time, and much more consistent and accurate about measuring effort. And consistency is required for the law of large numbers to apply. By estimating in consistent non time units you avoid those cognitive biases.

2) humans will very quickly start to unconsciously bias the units if they feel pressure. Speaking in terms of time puts one very close to a lot of pressure points for a lot of people.

Ideally engineers are concerned with doing things Right, and PMs are using past performance to predict how long that will take.

ohthehugemanate··on Rules of thumb for software development estimations
It's not rocket science, but I can't speak for how your teams have been doing it. I know there's a tremendous number of well meaning people who get certified in a rote method and only understand it as dogma. Doing this right only requires understanding the underlying principles and figuring out a method that your team likes.

Principles are:

- humans are much better at estimating relative effort than average time. So estimation sessions are only in terms of effort. The answer to "how many hours is one point?" is "as long as it takes." With developers like you this can be a hard line to keep but it is absolutely full stop required.

- consistency in relative effort unit sizes is a requirement for the math to work. Group estimation does this automatically after a few sessions, and can help expose miscommunications and better architectures along the way... but it's not the only way to do it.

- a consistent yardstick for "done" is required for consistent unit sizes. (Logically)

- project managers track average number of points completed per sprint. Even though this average will become extremely consistent, it is an AVERAGE ONLY and can not predict any individual sprint.

- There is no pressure to burn points "faster". Remember, point sizes are arbitrary and consistency is required. When engineers feel pressure to complete more in the same time, consistency is dropped and the math breaks) if you are using sprints this is an easy trap to fall into. More points per sprint != better. Making tasks easier is OK though, ie with automation or technical improvements. Note that this would impact the estimated point size of your tasks, not the number of points put through in a sprint!

That's it. Do it how you want, but have consistent relative point sizes, don't let engineers talk or think about time, don't treat an average like a single sprint prediction, and don't pressure engineers to increase velocity.

A casino can't predict a single hand, but they can predict with great accuracy their profit margin after 100 hands. Using the same math, you can't predict a single sprint, but you can predict with great accuracy 5, 10, or 20 sprints... as long as you help the developers stay unpressured and therefore consistent.

ALL THAT SAID, when you say "I did this before, it took me 2 weeks," that is also a very effective way to estimate. If your tasks are highly consistent, definitely track time for implementation of similar work (because human memory is very fallable) and estimate this way. Just don't let yourself notice that you defined a consistent unit of effort and used past average time to predict future average time, and you can feel like you've found a great life hack.

ohthehugemanate··on Rules of thumb for software development estimations
> Estimating in something other than hours still needs to be converted for hours in order to be useful

Yes. Did you see the part of my comment where I explained how you do that?

The fact that this is the most accurate estimation method is well established in research. You can get close with some other methods, like tri-partite estimation, but they're more cumbersome.

WHY it helps so much to abstract away from direct time estimation, has a few going theories. One obvious reason is that the abstraction and tracking the relationship to real time brings into play the Law Of Large Numbers, the same mathematical law that allows casinos to profit on games of pure chance. The more sprints you have under your belt, the more your conversion rate averages in unexpected external influences like illness, windows updates, upstream problems, etc, in proportion to their actual occurrence rates.

Another of the most popular theories is that human brains have specialized areas/heuristics for predicting time vs predicting effort, which come with different cognitive biases.

Fundamentally I can't give you a definitive answer to why, only that speaking in terms of difficulty with engineers, and converting to time to talk to business planning, is well demonstrated to greatly improve accuracy in controlled studies. In fact, the best estimators, when predicting time, still predict 130% of the time needed for a complex task. Using abstracted measures it is not unusual to see accuracy within 5% or 10% of actual.

ohthehugemanate··on Rules of thumb for software development estimations
There is lots of good advice here, but I'm always amazed that these articles miss the #1 improvement to estimates recommended and validated by scientific studies: do not estimate in units of time.

Everything else here applies, but don't estimate in time. Estimate in difficulty points, t shirt sizes, cups of coffee, gold stars, anything will do. Then as you track your outcomes (see TFA), measure the average relationship between your units and time. Then use that relationship to project a timeline based on your gold stars or whatever.

Using the law of large numbers to average externalities and developer inaccuracy into your time estimate has been the most accurate method since Kahneman and Tversky's Nobel prize winning studies in the 1970s.

ohthehugemanate··on Red Hat cutting hundreds of jobs, CEO says in letter to employees
Care to elaborate? Why do you blame enshittification instead of the macroeconomic factors that have caused everyone else's revenue growth to slow, too?
ohthehugemanate··on Nintendo Hacker Freed, Now Owes Them 25-30% of Salary for Life
Interesting idea. A fund like the EFF , to take care of the targets of weaponized corporate copyright law? A safe place for the Aaron Schwartzes of the world, even if it's alongside the Bowsers. I'd pitch in.
ohthehugemanate··on Nintendo Hacker Freed, Now Owes Them 25-30% of Salary for Life
Well that definitely makes him an asshole, but not a prison-and-then-life-of-crushing-debt asshole. Is copyright law really this fucked, that someone was extradited and made an example for selling a ransomware chip?
ohthehugemanate··on Nintendo Hacker Freed, Now Owes Them 25-30% of Salary for Life
Anyone have more detail about the case against Bowser? Was it purely a DMCA copyright circumvention case? Did he sell pirated material? On the face of it the damages awarded is ridiculous for a private middle class individual. Reminds me of the old RIAA downloading lawsuits, where they requested outrageous damages in an effort to scare defendants and hopefully set precedent.
← PreviousPage 3 of 17Next →