ziggus

I believe the question is less about input latency than (as mentioned,) scheduling latency or the amount of time from when the scheduler marks a process as 'ready to execute' to the time it actually starts executing.

SchedLat (https://tanelpoder.com/posts/schedlat-low-tech-script-for-me...) is one tool/approach to doing this, but it's a bit out of date.

Focusing on the type of work being done is a bit of a bike shed, since the experiment isn't about the work per se, but the measurement of the work as a function of the employee alone - ie, without the context of the systems in which the employee functions.

A good example of the type of mismeasurement done in non-manufacturing contexts is the ridiculously stupid burn-down chart.

These kinds of examples are great illustrations of how damaging stack ranking (and most other performance evaluation systems) really are. Instead of focusing on improving their team's performance by reducing the friction inherent in any corporate bureaucracies, this manager is forced to spend time playing Machiavellian games that only serve to reduce effectiveness and engender an anti-productive spirit.

An illustration of why these performance evaluation systems are always going to produce statistically irrelevant results was the Red Bead experiment[0] designed by the late, great W. Edwards Deming.

[0]: https://maaw.info/DemingsRedbeads.htm

It appears that this is a second home, not their primary residence.

Are you sure you're not just experiencing a bit of Baader–Meinhof?

Isn't Minecraft a plain old polygon renderer?

So it's basically a blog and a forum, but in an app?

Is this the company that re-invented the PCMCIA slot, but completely proprietary?

Try pasting the link into a new browser tab. It's a redirect if you're coming from HN.

"The Giant Pyrosome is a free-floating, colonial tunicate that is made of thousands of identical clones, together forming a hollow cylindrical structure that can be 60 feet (18 m) long and wide enough for a person to enter."

Nope.

IRC is still a thing, and a very popular one at that. I've found that it's a great tool for finding like-minded tech people with relatively less 'noise' than in similar Slack or Discord groups.

Right, that sucks, but he signed up for it by taking VC money.

There's a few commercial versions of this idea that combine some sort of insulation with a vacuum container, which increases the efficiency.

https://www.cabelas.com/shop/en/thermos-cook-and-carry-syste...

Maybe in your experience that conflation makes sense, but a developer is not necessarily a software engineer.

There are distinct educational programs that differ between "computer science" and "software engineering", and a number of professional organizations are lobbying for software engineering licensure, similar to other engineering professions.

Even Dijkstra knew of the differentation: '"A number of these phenomena have been bundled under the name "Software Engineering". As economics is known as "The Miserable Science", software engineering should be known as "The Doomed Discipline", doomed because it cannot even approach its goal since its goal is self-contradictory. Software engineering, of course, presents itself as another worthy cause, but that is eyewash: if you carefully read its literature and analyse what its devotees actually do, you will discover that software engineering has accepted as its charter "How to program if you cannot."'

Not Another Advertisement Disguised As A Blog Post

You don't see a problem with putting wood on a heat exchanger?

Why the conflation of 'engineer' and 'developer'? That's a bit confusing.

Thanks for the explanation. It's obviously been a long time since my machine code CS classes.

Based on your (amazing) write-up, it seems like there was some sort of abstraction layer between a programmer writing in some kind of assembler and the actual CPU registers, is that correct?

I recall seeing a talk given by Jeff Bezos years ago at some university where he described the early versions of the Amazon web site. One of the more interesting bugs was one that allowed a customer to enter a negative quantity of items to order, which meant that Amazon would credit your account and wait for you to send them the books.

I think it's fixed now.

It's a very common complaint amongst EAs; there's a LOT of time management tools, but they're all geared towards an individual managing their own time.

Imagine the work you have to do to manage a busy calendar, then multiply it by 10. Then add in responsibility for booking travel, managing events, managing multiple email accounts, etc. for a number of people, and you can start to imagine how amazing it would be to have better tools to do something like managing an exec's calendar.

I speak from (limited) experience: my wife is an EA and sometimes I show her tools like this and she always asks 'can it handle delegate roles?', and every time I have to concede that, no, they don't.

"Very few people have an assistant these days."

Uh, frankly, you don't know what you're talking about. Just because the people you work with don't, doesn't mean that your experience is universal.

Most execs or C-level employees are going to have at least one exec assistant, if not more.

I've seen a lot of these kinds of tools come and go, and this one looks as good if not better than most of the others. However, they're all missing out on a huge market: people in delegate or what's normally known as "Executive Assistant" roles, who are managing someone else's calendar and need a way to control what calendar items, invitations, responses, etc. their executives are seeing.

I have yet to see any tool that serves that market at all. If there was a tool that could help people in those kinds of roles, particularly if there was functionality to 'automatically' setup meetings a la Doodle (which is garbage), it would sell like hotcakes.

So that means what? My password manager is going to start crypto-mining, and share the profits with me? My password manager is going to report all the sites that I have stored passwords for back to the companies?

Whatever the case may be, I'm sure it's going to turn out to be something completely worthless to me.

Fortunately, there's always Keepass, which keeps plugging away doing exactly what it says on the tin.

I really like this idea, and have thought about doing something similar - glad somebody did it!

However, why on earth do I have to sign in?

Yes, please.

The emphasis away from semantic HTML and towards component-based frameworks with all the associated utility CSS classes has been a disaster for accessibility, and it's good to see projects that have all users in mind.

Before you even ask: yes, there's a port for Wayland: https://github.com/djpohly/dwl

Stack ranking is based on whatever metrics team leaders/supervisors want to use. It often becomes a simple popularity contest, and leads to an 'every person for themselves' culture which can stifle innovation and collaboration. Even in cases where there's a quantitative metric used for ranking, it's often subject to gaming, such as the use of number of commits or ticket closures.

Also, stack ranking doesn't account for any flaws in the systems of the company itself - if you have poor processes that hinder productivity, it's going to artificially diminish the rankings of employees that have to use or are subject to those processes.

There's a reason why companies that use it tend to have much higher turnover than companies that don't - because it makes for a really unpleasant workplace.

Bureaucracies often impose arbitrary measures of success on teams and employees that often have nothing at all to do with merit or productivity or any other measure that a reasonable person would use, and reduce or increase staffing levels based on those measures.

See 'stack ranking' for a perfect example.

"Professional employees whose work is merit-based don't need labor unions."

You're living in a dream world, Neo.