Is this the one part of the night qualifies as merely mildly interesting?

DATA: I am puzzled, captain. This joke did not receive a single humorous reaction. However, I calculated with 99.987625% certainty that -

PICARD: Well, Data, there’s more to humor than, well, data.

This is a very personal question, and it’s really just whatever you are comfortable with. I personally:

• Try to be open about it and my experiences with friends, if only because I’m sure people had suspected I had it and I so wish someone had mentioned it. I’m willing to cut friendships if I’m judged negatively, but ADHD is common in my social circles so it hasn’t been a huge issue.
• Have been debating with my ADHD siblings how to broach the subject with my definitely ADHD parents. It’s definitely common among my extended relatives, but I just feel it’s not worth the fight.
• Would be very guarded in a workplace. Accommodations for ADHD are hilariously trivial asks, but I’m skeptical I’ll ever work somewhere I can (safely) get them.
• Try to avoid the subject with older generations.

Look a flagpole

Standard Form 86
Revised June 2024

Section 30 - Video Gaming Product Record
23.1 In the last seven (7) years have you participated in any video gaming product?
[ ] YES [ ] NO

Entry #1
Video gaming product name:
Dates of use:
Provide nature of participation in this video gaming product:

Was your participation while possessing a security clearance?
Do intend to participate in this video gaming product in the future?
Provide an explanation why you intend or do not intend to participate with this video gaming product in the future:

This seems highly unlikely in the age of increased polarization. The number of independents has steadily decreased and there’s a reason why “making her the first Independent to win a three-way statewide race in American history” would be groundbreaking. It’s not like she endearing herself to either side.

Anyone have any analysis why this would be feasible? I just can’t believe someone would look at, say, the republican primary polls and think there’s 25-35% of them looking for a ‘centrist’ independent.

This is already said, but it cannot be too emphasized: This is not your fault. This is entirely on them. Three months is far too short to evaluate someone even if they were secretly unhappy with your performance. It might be worth talking to an employment lawyer, but likely you’ll have to take this on the chin. In the immortal words of the great Captain Picard: “It is possible to commit no mistakes and still lose. That is not a weakness; that is life.”

As everyone has said, you can expect to get questions about it, and I would definitely have a prepared, rehearsed statement. Some recruiters and hiring managers make a big deal about these sort of things, some won’t even care. Again: this is not your fault and do not be apologetic about it.

Five weeks is not a lot of time to get a new software job, even in a hot market. This is the unfortunate reality and I would start making contingency plans. If living in NYC remains a goal, then this is a setback but a far smaller one than it may seem right now. You don’t have a mortgage or a family hanging over your head. Moving back to NYC will be in play, likely sooner than you think.

Spending time on career development is a good idea. Something with a firm outcome like AWS Solutions Architect is also good. I have the associate certification which I started working on while at Amazon. It hasn’t really done much for me, but I’m not seeking positions where it would hold much weight.

If you haven’t I recommend reading a few books on management even if you have zero interest in going down that path. It will give you more perspective on what you should be expecting from your manager, which in turn should in turn be what you talk about during 1-on-1s. I like The Manager’s Path by Camille Fournier, though it could use more focus on the ‘why’ instead of the ‘how’.

The best manager I had used a shared private document, where he would dump important points and expected you to add bullets as things came up during the week. This “you drive the conversation” is a good approach and one I intend to use in the future.

• What’s really going on. A good manager should be aware people are inclined to present things as rosier than they are.

• Anything you are unhappy with. They should be fighting to keep you around, and how happy you are is a key piece. The sooner they know something is wrong, the easier they can (potentially) deal with it.

  • I’m planning a career shift into an EM role, and plan on simply being upfront about the Gallup 12 points (actually 13+4). They shouldn’t confine themselves to them, but if a report is ever unhappy about any of them then I absolutely want to talk about it.

• What resources you don’t have that you need to succeed.

• What ideas you have for initiatives. New projects, tweaks to reduce pain points, so on.

• Things from Above that you should be aware of.

I’m not going to watch the video, but what’s the procedure for switching between Linux and Windows? Usually you dedicate a GPU entirely to VFIO, with a 2nd GPU for the host OS (or run headless).

Anyway, will it work? Yes, minus some anti-cheat software. Will it be a simple solution? Well, once you get things stable, yes. The tech behind this is mature, but it can be a rabbit hole.

I would look into a non-Nvidia GPU for your 2nd PCIe x16 slot (x4, shared with the 2nd M.2 slot FYI). Good idea to check IOMMU groups before buying anything, but modern AMD motherboards are usually fine. Blacklist the Nvidia drivers and dedicate the 3070 to VFIO to make your life easier, and run Linux off the secondary GPU. Intel A380 might be a good choice. Do gaming stuff on Windows and stream via Parsec/Looking Glass/Moonlight+Sunshine; everything else on Linux.

If you talk to people about homelessness, they will readily admit they just don’t want to see it. If go to any cheaper grocery store you definitely are rubbing shoulders with people who use foodbanks. Food insecurity doesn’t go away just because you have a roof over your head.

The rub is a foodbank in a grocery store will attract the more visible “unreliable access to showers” type of user, which would be unacceptable.

Keep working on those evil KPIs*, you’ll get there.

*Not to be confused with regular KPIs, which are not required to be evil just usually are.

deleted by creator

Mostly just as a wrapper for Docker. The main issue I’ve run into is Docker’s union file system functionality doesn’t work when backed by ZFS, so disk usage can balloon out of control. I wouldn’t use this in production but don’t tell me how to live my life mom.

Beyond various Docker stacks I also have a Certbot container that uses Snap (sigh), and Hashicorp Vault container which runs as a vanilla SystemD service. I run Wireguard as part of my OPNSense VM. That’s something I would run in a VM since it’s exposed to the internet. I have an older MinIO and Concourse CI Docker Compose config that I’d love to run in LXC but I suspect that isn’t realistic.

Note on Vault, I haven’t been able to get mlock to work (used to prevent sensitive memory from being swapped). By all accounts it should just work in LXC, but since it isn’t and there’s no swap on the host I just turned it off. I may migrate Vault to a VM at some point.

I’m personally just interested in lightweight environments with good enough isolation and don’t break all the time over nothing. Docker mostly accomplishes that for me. LXC + Docker also mostly accomplishes that.

(My heart yearns for FreeBSD Jails but with decent tooling)

I originally excited by Podman, but ultimately migrated away from it. Friendship ended with Ubuntu and Docker -> CentOS and Podman -> Proxmox + Debian LXC (which has its own irritations but anyway). Off the top of my head:

• Can’t attach a containers to multiple networks. Most of my Docker Compose stacks have an Nginx reverse proxy and a network for each service.
• But you can use pods. However since they share the same network interface if you have multiple legacy services that both insist on, say, port 80 they can’t be in the same pod. They also don’t isolate services, nor can you assert a specific pod is the one listening on a forwarded port.
• Pods also have DNS issues with Nginx. It kept crashing since it couldn’t resolve the hostnames of the other containers in the pod, even if they were already running. If you launch a shell inside an Nginx container the other container hostnames resolve fine. I suspect the problem is the container is launched before its behind-the-scenes DNS infrastructure is ready.
• Podman lets you use secrets on normal containers (yay) but if the secret changes you have to recreate the container. Amazing synergy with rotating TLS certificates.
• Endless issues with SELinux and bind mounts. My Nginx container kept crashing because SELinux didn’t like the TLS certificate bind mount. This is where I reflected on the endless parade of random issues that I had no interest in solving and finally threw in the towel.

I brought all this up in another community and was told the problem was [paraphrased] “people keep trying to use Podman like they use Docker” - whatever that means. I do like a number of design choices in it, like including the command used to create containers in the metadata, and how it’s easy to integrate into SystemD for things like scheduled updates.

Cockpit is pretty slick though, need to install it on my bare metal Debian host.

Honestly, I’d be more curious what topics where the media does nail the nuances of. Are there any at all?

Could be. Anonymize your resume and post it on programming.dev’s cscareerquestions or something if you want someone to review it. Assuming you are US based, the market is still cool so you might have to keep treading water or find something that just keeps the lights on for now.

However, I would never assume things make any sense on the hiring side. There’s a lot of bad recruiters but there are even more bad hiring managers. Years ago as I sat on the other side of the table for the first time for a presentation and Q&A for intern candidates. When I followed up asking if any had been any offers, I was told none of them performed well enough but it was okay because turns out there wasn’t room in the budget for an intern anyway. What a colossal waste of everyone’s time.

I’m a similar boat. Diagnosed with ADHD recently but later in life, and it’s likely why I never settled into a single domain. I consider myself a strong software engineer but tend to fall apart in interviews, particularly with unstructured things like being asked to “tell me about yourself.” I am also planning a shift into a management role.

My main regret in life is spending a lot of time trying to apply advice that seemed reasonable and how Other People did things. Only adopt things that work for you.

• I highly recommend at least trying stimulants. I inadvertently self medicated with caffeine for years, which might work in a pinch. My secret sauce is frankly 90% Concerta and 10% behavior modification things like carrying a notebook around.

• I would not mention that you have ADHD to interviewers since you can’t count on anyone to properly understand it. Showing weakness is just blood in the water. Hopefully this won’t be an issue for future generations. Yes, I am extremely bitter about this.

• Approach this as doing whatever you have to do to get yourself over the finish line, and know that trying harder at a failed strategy never works. Don’t limit yourself to how things are supposed to be done.

• Security requires a flexible mindset and attracts square pegs. Data centers are where all the real weirdos hang out so devops might be worth considering. I’m confident most scientists I’ve worked with have ADHD, and prototype R&D work is definitely more ADHD friendly.

• Insist on knowing the structure and expectations of each round of an interview. I pitch this as “I need to know how I’m being evaluated so I can properly prepare and demonstrate my abilities.”

• I’ll be honest: the interview process is mostly nonsense and should be treated as such. Anything that puts a thumb on the scale in your favor is fair game, short of unethical behavior like lying. Telling people what they want to hear is a great way to counter dumb questions.

• I’ve built up an Obsidian ‘database’ of bullets to help during interviews, including a prepared statement of why I have it and need to have it available.

  • “Tell me about yourself”, “what type of role are you looking for”, “why do you want to shift into management” open ended questions. The key thing is respond in a coherent, organized way without showing any negativity or weakness. Yes this is ridiculous, but it’s how it is.

    • Turn your generalist background into the strength it is. I use: software engineering is a problem solving role, everything else is a means to that end. Solving problems is what I do; I’ve done so in a wide range of fields and domains and always drive them to completion. What I’m looking for is a great team to join, which is independent of industry or tech stack.

  • “Tell me about a time” behavior questions. I like the STAR format. I do well on these but need an outline to work with. Make sure it’s polished into a coherent narrative. Put an emphasis on what you did, but also how you enabled your team. Numerical data points are great if you have them

    • If the company posts their values or principles then that’s likely want they want to see out of these. Match your scenarios to the values beforehand. The idea is previous behaviors indicate future ones.

  • System design questions. I have my own checklist of questions I go through since I don’t like the popular format. I expect this is where you shine, maybe just need a bit of scaffolding to help organize your thoughts.

  • Leetcode programming tests. Like it or not, it’s part of the game.

• If you are serious about going into management, you’ll need a prepared philosophy of how you see the role and will approach it.

  • This is also a great question to ask hiring managers. The best indicator of what the job will actually be like and you can’t wiggle out without raising red flags.
  • The two books I like are The Manager’s Path by Camille Fournier and the classic First, Break All the Rules by the Gallop folks. Again, not all advice is good so only take away what you think will work for you. Worth reading if only to understand what you should expect out of a manager.
  • Do not make the mistake of feeling like you need to go into a people management position. Shifting into project management is perfectly fine. Topping out at a senior or staff software engineer role is also perfectly fine. Frankly, topping out at a mid level engineer is fine, just watch out for ageism.

• I also have check lists for all sorts of random things. Even dumb things like how to respond to a question I didn’t prepare for: repeat the question, write it down, jot down what I think they want to hear, write down points, and give them an order.

I disagree with that as a rule of thumb. I’ll take writing 1000 lines of code from scratch every time over deciphering 1000 lines of bad code.

However, I do you think are right if limited to the ~100ish lines that fit into an hour sized block of interview time. I suspect the other half of the answer is (good) job postings have largely gotten away from hard language requirements. It’s perfectly reasonable to hire someone that will need to familiarize themselves with Go or Python or Typescript or whatever. It’s not fair to expect someone to analyze code in a language they haven’t used on the spot.

I see them as a flawed indicator of the ceiling of someone’s theoretical computer science abilities. Having worked with some brilliant people that career shifted via bootcamps, I will contend there’s value in having that foundation. I also prefer Leetcode problems over having to memorize search algorithms. But yeah, it’s not very reflective of day to day tasks even in R&D heavy projects. The most algorithm heavy thing I’ve ever done was implement Ramer–Douglas–Peucker to convert points from mouse polling into a simplified line.

(There’s clearly a “it’s what everyone else is doing” aspect to Leetcode, on top of being very practical to run, hence I why don’t see them going anywhere. They’re also as objective as anything in an interview will ever be, so as I always say: it can be so much worse.)

I intend to make the hacker “dive into an icky codebase armed with a stack trace and fix a bug” aspect of software development a part of my interview process; plus lean more heavily on system design questions which is where non-entry level engineers really ought to shine. The parts that worry me are the ability to create new tests as they inevitably leak, plus whether I can truly objectively evaluate someone’s performance.

I’m curious what you include and how well it works.

Yeah, they kinda suck and they are brutal to go into cold. Having to grind a bunch of leetcode problems is a burden, particularly if you currently have a job and god forbid a family.

I would still take them over the puzzle questions that used to be popular, or the personality test nonsense that dominates most fields. At least Leetcode problems are reasonably reflective of programming skill. I’ll also take them over vague open ended questions - ain’t nothing more fun than trying to ramble my way into whatever answer the interviewer is secretly looking for.

Personally, when the day comes when I’m In Charge, I plan on experimenting with more day to day type evaluations. I think there’s potential for things like performing a mock code review or having someone plan out a sprint based on a very detailed design document. “Here’s an icky piece of code, tell me what it does and what you would do to improve it” seems to have fallen out of style, though it’s not clear to me why.

That said, like it or not it’s how the game is played and not changing anytime soon. Get on the Grind75 train, or don’t and keep failing tech screens.