For the longest time, some of the wiseacres in here have told me I need to live closer to where I work.

work work closer to where you live, as I recall.

There is no task management software that is more accurate, more efficient, more effective than yellow sticky notes attached to one's monitor.

And there is little that is more satisfying than snatching a note that represents a task completed, crumbling it up and tossing it in the trash.

Hmmm... less effective for me.

Monday:

* create sticky note reminding me to create widget for old tool

Tuesday:

* work from home, see no sticky note, figure it's a day off.

Wednesday:

* WTF!? I missed my deadline!

You need to work closer to home.

Time to move into the office. I suppose I can shower with the men's room sinks with a little creative plumbing and a complete disregard for company property.

The complete disregard for company property should be embedded by now. Most companies have complete disregard for their employees.

In this case, the 'company' isn't so much the one I work for as it is the one that leased this building to the one I work for, heh.

Somehow, less satisfying an idea.

Hey, code-monkey, how long will it take you to do that thing you haven't had a chance to design, or even get specifications for yet?

My videoconference problem has been solved. Mrs. IG got me a roll-around whiteboard for my birthday. I can place it directly behind me when on a conference call, making the background indistinguishable from any other location with a whiteboard.

I suppose this means I can also use my webcam to do webcasts where I explain things to people using whiteboard drawings.

Hmm..

Next time I interview anyone for hire as a software engineer, I should ask if they know what "resource acquisition is instantiation" is. I mean, *really* get it.

These days, that ought to be old hat, so if they can't work that out, we probably shouldn't hire them.

Having some problems with code written by someone who, I don't think, really understood the benefits of using constructors and destructors to manage resources.
Really, *really* painful stuff in a long running process that doesn't seem to want to quit when we ask it to.

I'm not sure using ctors/dtors is always the right answer. Sometimes you need to separate resource lifecycles or service lifecycles from the object lifecycle.

*my bias here comes from Java, where there are no dtors and the closest equivalent, finalization, has problems that are serious enough that it should be avoided.

Well, sure, RAII isn't applicable for all situations, even in C++ (my bias).
But, at least in C/C++, it sure as hell works for over 90% of them, and probably hints to design problems for the rest of the situations.

But I can see where, in Java, it might be problematic. I get the impression Java doesn't necessarily get rid of objects when they fall out of scope right away. Such things linger for a while until the garbage collector decides it's time to let it go. If an object doesn't really have a good sense of when it's out of scope, how can it be used well for other resources, like, I dunno, a handle to an API call within the operating system that might require another API call to 'close' it (like maybe a file pointer, but it doesn't have to be that... could be anything... syslog, a custom database handle, proprietary hardware...)?

I'm guessing you have to explicitely call the functions to deallocate resources yourself, rather than relying upon something going out of scope. Which makes it really easy to miss a detail, compared to relying upon the scope of an object.

I just got a list of requirements operational requirements from our developers.....



Docker, Kubernetes, Terraform, Ansible and Openshit.

Straight out of the DevOps playbook.

terraform AND ansible? do they know what they're doing :-P

kubernetes competes with cloud-vendor-supplied solutions such as ECS, not much reason for it

Well, Openshift is based on Kubernetes and both were listed.

terraform's OK. we use it here.

Sounds more like straight out of the "what's cool to have on your
resume this year" playbook.

I hope you've been given enough power to tell them "fuck your resume
enhancement strategy, we're going to use the tools that make sense".

I'm gearing up for a fight with the head of development.

We farmed out this product to a foreign developer and said
"it needs to be easy to install in the cloud and on prem".

That was it.

That was our requirements.

Fuck me.