ldx1024

Would it be against Japanese etiquette to simply write "Please Don't Reposition" on these work shoes? Seems like that would reduce the number of times this happens.

Congratulations and count yourself among the lucky. But if you cannot appreciate that things will not be that way for many employment situations then you don't know how lucky you are.

You dislike engineers because they are acting like engineers instead of artists? The typical engineer is a paid mercenary, working to get widget 2.0 out the door. They are not robots, but are paid to play nice with others to advance their employer's interests. To act like a temperamental artiste in that environment would be immature and unprofessional.

I was about to say something similar. It may be true that the ideal image of the entrepreneur is the exception rather than the typical for the self-employed, but I would say the same for the image the author paints of the career employee. For every self-actualized employee with an enriching network, meaningful work, and supportive surroundings there are many more who are just trying to make ends meet in a meaningless, toxic, soul-sucking environment. The grass is very much greener on the other side...

"Although the standard is a little more complicated..."

If you have ever read the software control category definitions in MIL-STD-882E you know that the definitions that this blog author gives are very much his interpretation. The actual definitions in 882E are a god awful mess. Multiple contradictory definitions provided for the same category. Additional parenthetical statements that are intended to clarify, but just muddy the picture further. Yikes...

"Haunted house" themed halloween amusement area, I assume from skimming the article

I was just thinking about this. Exposure from a short is theoretically limitless. Some sort of derivative would be a better approach? Asking for a financially clueless friend.

NDAIPF

Check out the University of Massachusetts Dartmouth campus, too, about 60 miles south of Boston

Software is only subject to entropy when you touch it. In most practical cases these days not being able to "improve" the software is a feature, not a bug.

I have a hard time identifying with this. The premise seems to be that the worker is just a passive participant in the system, literally a ping pong ball on a galton board. If the end state isn't what is desired the problem is with the board not the balls. This in fact may be true in the large, but that is the same as saying that management systems and processes are for people that need management systems and processes, reliably producing mediocre results. There is definite tension in accepting that this mediocrity is practically inevitable if anything is going to be done at scale.

I know next to nothing on the subject, but I won't let that stop me :) If this has been sitting here for three hours with no response I might as well pipe in...

Reddit link discussing topic:

https://www.reddit.com/r/androiddev/comments/17w3pgz/google_...

If you think the app might make some real money you might want to think about registering an account with a business name and virtual mailbox address. I didn't read the whole thread above, but that comes up early in the thread as one option.

Makes one think that the Ada programming language will be involved...

That would mean the software would work well. I run that explanation against what I see in practice and in general it is not a good fit.

Along with procrastination (which might have noble motivations) an additional much simpler answer is that people just want to do the minimum they can get away with.

Trout Mask Replica is the ultimate "it grows on you" record. A masterpiece.

Another feature of tar (the 7-zip implementation, anyway, I haven't checked others) is that it will properly archive files whose path length exceeds the path length limit, and then also restore the files properly. Conversely, trying to zip up a group of files with paths too long appears to work but then results in a corrupt zip file that will not unzip. I'm no expert in this area, but that is my recollection. So if you have any doubts about whether your files to archive have paths too long it is better to tar them then zip the tar file rather than just zip the files.

I'd be happy with File Explorer not giving the circle of death and the green bar of despair on a regular basis. Microsoft, can you fix these basic usability problems first before shoving more bloat into the tool?

This article trips my BS meter for a made up story to illustrate a point. Of course that says nothing about whether the point it is making is valid or not.

Some truth to this. But if it wasn't for that mindset you'd be having your cocktail party in a cave.

Wordpad is usually my go to when opening a unix text file (without carriage returns) that Notepad renders into a unintelligible mess. Word renders it properly, but then typically requires a bunch of subsequent formatting adjustments (font size, etc.) for good readability.

The article is painting a picture that equates improvement rate of software to that of hardware, where in reality it is not even close in any reasonable view. And saying that software is getting better overall is a highly dubious claim.

"For the last seventy years, we have lived in an era of improving computer hardware and software."

True for hardware, definitely not true for software. See Wirth's Law.

https://en.m.wikipedia.org/wiki/Wirth%27s_law

As others have pointed out, the article also ignores the obvious impact that AI is going to have on software. By themselves these two errors void the validity of this article without even looking at any of its other claims.

Charles Holland Duell, United States Commissioner of Patents from 1898 to 1901, was famously purported to say "everything that can be invented has been invented."

That is apocryphal, though. A thing he actually did say was:

"In my opinion, all previous advances in the various lines of invention will appear totally insignificant when compared with those which the present century will witness. I almost wish that I might live my life over again to see the wonders which are at the threshold."

I think if Kagi was the established leader and Google was the challenger you would be saying the opposite.

Sounds familiar. If you are a developer and quietly forsee a future problem with the code base and fix it, are you rewarded for that? Nope, the code will quietly continue working, and that's what it's supposed to do. Rarely do people recognize the ability to avoid problems. In most cases you would benefit more personally by letting things get screwed up (but not too bad) and then be the hero fixing the mess.

Sounds like better PR might be in order. If you're quietly averting disaster that's not enough, you have to make sure people are aware of that. Easier said than done, I know.

I would say a big reason for the U-bend in many cases is that as you get deeper into middle age you can actually see retirement on the horizon, and then eventually you get there and aren't shackled by a job.

Looks like it was under temperament:

"Some people are able to remain rational and continue to follow their process even under great duress or during periods of external upheaval. Others get swept up in the emotion that typically runs amok during such circumstances, and abandon their discipline."

"Prevented from working longer hours"

Can this really be prevented anywhere? That would be appalling. Reminds me of "Harrison Bergeron" (Vonnegut short story).

The conversation has changed since I first read it (with the original conversation still there underneath it). Getting more interesting...

I find it charming actually that they are so kind and supportive of each other. Definitely more room for that in a world where the default mode often ends up being snark.