shortoncash

It took me 15+ years in the business to realize this. If someone gave you a time machine to go into the past and give me your exact comment AND punch me in the face, it still wouldn't have dawned on me because I was in pursuit of some weird perfection that doesn't exist.

Thanks for spreading sanity and insight -- I hope someone else digests your message sooner than I did.

I hope so. I used to crush whiteboards but I really dislike these modern quiz platforms. I suppose I just need practice, but I'm like this old guy now with less time to practice on modern quiz platforms.

Bring back pure whiteboard and I will be almost as good at this stuff as I was when I was 22. Little slower on the recall, but still good.

I worked at home for 9 years and then I had kids. (They are great kids but they make working at home hard.) That was enough for me to not want to work at home anymore. I then got a new job, and then covid-19 hit and I am working at home again. Argh!

I'm speaking strictly technical here, but there have been features that have been removed. Trigraphs (I think), and the register keyword. Moreover, there are objects that are very clearly marked deprecated, like auto_ptr. (Oh, and there is even talk of removing 'volatile' as a keyword.)

The register keyword issue crops up because legacy code included and linked to modern C++ will occasionally have the word "register" affixed to a loop variable. Generally speaking, once you change standards, there is room to drop the old stuff. It's just gradual. Static analyzers do a lot to modernize code now too, so the situation is not as painful as it used to be.

Calendars and to-do lists matter, but the unpleasant aspect of these things is that I become a human scheduler, similar to an operating system scheduler. The scheduling function consumes so much time on its own, and it's psychologically uncomfortable.

Dare I say it: I don't like context switches and would prefer first come first serve, until completion. The real world, however, is unforgiving on which scheduler I can choose.

Your design above with the private type being returned could possibly be useful. Perhaps outsiders to the class will be prevented from instantiating the nested-type without using the class itself to generate the nested type. This could be contextually useful and certain (interface) functionality could be grouped in a manner that is more convenient to use than by calling methods on the original class.

I like that C++ allows us to express this situation, even if it's a bit of an unusual design pattern.

I was able to get rid of multiple computers and convert from physical to virtual and save on power bills. Once your build is complete you will be incredibly happy. AMD is killing it with these processors. I've never been happier with a tech product line. It just blows me away how much I'm able to accomplish on a shoestring budget now.

Worker pool for compile jobs and simulations. The cost to run this locally and with local storage (over 10g) is cheaper than to do it in the cloud.

I bought a 3900X also. I, too, would like a 3950X, but the 3900X is so fantastic it's hard to be too upset. I also have 4 Threadripper systems and I just could not get work done without them. My build times for compiling software would be atrocious without them.

gcc

So true. The rent forces you to be on the hamster wheel.

I'm in the same boat (but vegan). I supplement B12 and iron out of caution, but I am not sure they are even necessary. Just copy what the Indians do; they get by without meat and their diets and classic recipes seem to have evolved recipes that compensate for lack of meat.

So true. Always takes a bit of a spark to free your mind from the way the educational system makes you do things. Once you get away from the comfort of routine and embrace the danger of thinking in ways that the machine likes to discourage, the sky's the limit.

I believe in the code dictator model also. However, the code dictator takes a lot of heat over style opinions. What I see is that, when the dictator emerges, he still has to build coalitions out of people with different skills and different backgrounds. If there's a pool of mediocre or average developers, that is very hard to work around. Only the new people being added can really come pre-loaded with the right code-culture attributes. With non-new people, everyone has to be convinced about the code dictator's approach. This is just not a frictionless process.

I work at a place where the culture is definitely "everybody should tidy this up" and it never changes, or it changes very slowly. What I'm finding though is that there's no real defense against this kind of culture other than to be really tight about hiring. So, to your point, if you came to my company asking to look at source, it'd be a good thing -- particularly since so few people actually do it.