mfukar

Anything - even traversal. Basically, whatever combination of functions you can feed to the EP/LR/GR to achieve whatever task.

Yup, that's the one! High quality stuff.

I didn't serve in other countries than my own, but I sort of accidentally came across a Croatian Armed Forces 24-hour MR. 2 packs of orange drink powder, a 50g chocolate bar, 50g of hardtack biscuits, 3x75g (not sure if it was 75) packs of biscuits, 400g of beef goulash, liver patee (which tasted really wonderful, very fresh and smooth), peach- or citrus-flavoured tea, 2x20g packs of good quality, not crystallized, honey which naturally go in the tea, some coffee bonbons, 50g of pineapple & papaya dried bits, a 20g pack of chicken soup, and of course 3 wet napkins.

Absolutely fantastic. Neatly packed and easy to handle and carry around in a cardboard box.

I think you mean medical care in the USA. The schemes health providers resort to over there are world-renowned.

My favourite is the one that pretends pseudo-random binary sequences are only generated by LFSRs: https://en.wikipedia.org/wiki/PRBS

> StackOverflow mods are appointed to police content. The more content they remove, the more it looks like they're doing their jobs.

I can safely say you're wrong in this regard. Content removal is a big fraction of what the mods do because the contributors filter editing, closing, pointing out duplicates, migrating, etc. so that mods have to deal with only important stuff.

As a member of both, no, they're really not. The information on SE is very useful but highly transient (and redundant, but at least we constantly try to rectify that). It'd be extremely more valuable if it could be condensed into a guide or textbook or what have you to teach idioms to beginners.

As for Wikipedia, I'm almost convinced most information on it is erroneous, unverifiable, or useless in the forms it is presented. I've stopped making contributions and try not to ever reference it at all.

But there can't be, because mathematics is abstract and most of its fields have no intuitive physical analogies to back them up.

This is possibly the most useless piece of code I've ever ran across, in any language or context.

Right now my team are trying out only doing standups if there's important stuff to share. This leads to 1-2 standups per week for the past month.

Tidbits of info which can be shared at a glance, and probably don't affect anybody's workflow, go on a whiteboard. That way we know everybody's status, and seems like we can share important info when it matters.

> I commend him for being able to reinvent himself by learning how to create an effective brand and sell his name.

Which is quite an achievement on a personal level, but is a completely useless thing in every other aspect of society.

That article is a post-mortem with an awful lot of hindsight. Not everybody would able to ask the questions Yossi identifies in the post-mortem while the requirements are presented.

Would somebody then, instead, be able to become 10x more effective by thinking 10x more about their work, before they do it?

Not to exclude the X factor, but presentation matters. I think vomiting exceptions, stack traces, or error codes in text makes people not care. Not just a layman, but an expert, too.

What is the difference?

This is a recommendation I've seen in most coding guidelines I've read.

I doubt it. Expressions like this raise all sorts of red flags in code review.

> it's useful not to rely on a filesystem to handle this

In what way?

> There are many reasons to not work on something immediately beyond "nobody cares"...[snip]

I agree. That is not what I said.

> Issue trackers are good for long treatment and allowing people to prioritize and schedule fixes for technical debt. They're also somewhere that issues might go to die - in many orgs, it's common to basically ignore anything in the backlog that isn't being actively championed by a team member or customer. The nice thing about putting todos in the code is, somebody will see that the next time they're working on that chunk of code. The bad thing is that they're highly localized, and frequently give little space to give a full explanation of the problem.

I used to think the same; however the reality is if nobody cares about a given issue it's not an issue worth working on. Same with TODO or other notes in comments.

The only way an issue about technical debt becomes irrelevant is the debt is not there any more. I don't know how others treat an issue tracker; on my team, we go through issues at the start of every sprint and possibly re-prioritise. Issue became irrelevant? Close. Move on.

In no codebase or organisation I've ever worked in were comments actionable information.

Some technical debt spans multiple lines, or across files, modules, etc.

Issue trackers are everywhere nowadays. You've found something that needs doing? File an issue. Treat it like any other, it's not special.

I see you're not exactly clear on the reason a SWAT team would be deemed necessary, so I guess we can stop here.

Fine, 10. Your $20 order just became $200.

> You can't exactly have a bloke ringing in at the door and asking if there's really an active shooter/hostage situation, that would render the concept worthless.

"can't" by virtue of "didn't"? That's not sound logic. It makes no sense to even send in a SWAT team when a situation is not first assessed. And for that, you have to communicate.

I was scanning the article while, sure enough, I saw it:

> ...refused to obey...

Zero tolerance, zero patience.

I agree, but it's not a shortcoming of the tool (no tool can fix it, anyway) as much as a shortcoming of the process.

I must've missed the memo which says any conversation around the globe is waiting for my input before it proceeds.

Surely, it would probably be "Titan XB 1"

You have the option of not logging in to iCloud at all.

Not _shell_ processes, no.