Pihole is great, little hardware projects are fun (touchscreen calendar in the kitchen). They also make great emulators for old systems if you want to install a gaming oriented OS like retropie or lakka and get a gamepad or two.

I personally wouldn’t use it for a server, but it’s a good learning environment to figure out how to run services.

The beauty of the pi is it is an SD card swap away from doing a different job. You can buy a few fast cheap 16-32gb SD cards and play around with different options and operating systems.

Or you can do what I do: get it all set up, shut it down, and forget it exists until you have some wild idea.

The unprotected device on his hotspot!? Sure if you want to throw caution to the wind.

Yes, if you stay at a dysfunctional company for five years, and everyone more competent left: Steve in sales will address you as the senior engineer at the start of the call.

It won’t feel good, that guy is an idiot.

This is like a landlord painting everything white. It’ll hide / seem to fix some issues, but probably isn’t the fix you’re looking for.

Just when you can’t take any more; donuts in the break room!

Just set up auto renew and be sad when you are charged, then forget about it in a few days.

Same, I think deals on the lifetime pass still show up periodically, but I got it when it was about $40 too. It’s good software I use daily, so I’m happy with it.

Looks like on the last deal it was $120

Currently it is $250, which is too rich for my blood. Then again I just paid $70 for Doom the dark ages

My last interview was for a job I was on the fence about. I decided to go though the process anyways. I did a coding assignment that I aced. Then I had an interview with their recruiter.

Then I met with two developers. They grilled me for an hour. It was a fine conversation, we got along.

Then I had an interview with the boss of the dept. That went well.

Then they wanted me to prepare and give a technical presentation to some directors. At this point I told them no thanks.

He needs at least a decade of industry experience. That helps me find jobs.

Hey Linus did you merge my branch into mommy? I really want to get it out.

Product manager: “I want a new role for users that can only do x,y,z”

Developer: “uh… yeah. About that… Give me a few days.”

If a new project doesn’t come out called rockets impose I’ll be disappointed .

It’s the default for a reason.

Clear concise code that reads like documentation is the ideal. Good function and variable names, formatting, and encapsulation play into this. Tests should document and describe the system.

If it still isn’t clear what the code is doing, and I’m all out of ideas (or time) for refactoring, a well placed, accurate comment is fine. It needs to be kept up to date like any other artifact in the project.

It’s harder to keep comments accurate than code, since code can be executed and tested. I use them sparingly; when I’ve otherwise failed to write clean code, or the code is just so complex that it needs to be described.

Comments are just another tool in the toolbox. If they add clarity to the situation, by all means, use them.

If you can think of an expressive variable name that lets you skip a comment eg “employeeCount”, instead of “e” // number of employees, do that.

More than you’d ever want to know: https://en.m.wikipedia.org/wiki/Let_expression

Hudson, now there is a name I haven’t heard in a very long time.

Recently switched to a new contract, which resulted in me switching from IDEA Ultimate to vscode. This picture is terribly accurate.

In intellij I usually do code reviews by checking out the code and comparing the branch to origin/main to step through the changes. Just a right click menu option to compare branches.

I took for granted that this is just a thing IDEs should do, so I looked in vain for a while before googling it and finding out I need a plugin for that. (If I’m wrong please help me find the button, I still believe it must be in there somewhere. Surely the owners of GitHub can compare branches?)

If you are searching by a primary key or other indexed id you should be fine. Here are a couple of articles to check out:

https://www.atlassian.com/data/databases/how-does-indexing-work

https://www.red-gate.com/simple-talk/featured/postgresql-indexes-what-they-are-and-how-they-help/

The TLDR is a where clause that hits an index doesn’t have to go through all the rows in the table.

It sounds like you need your own API with some sort of persistent store. You may be able to reuse what you’ve done as the view layer?

If this were something I was going to tackle, I’d start by identifying the types of users (authors, admins, users, etc.)

Then I’d think about the kinds of workflows those users are going to need to do. E.g. admins can edit or delete anything, authors can alter their own content, users can only view data, etc.

Now with some loose requirements in mind, start thinking about how to solve the problems for your users. This is when you start evaluating what technology might be a good fit for your problem domain.

You could probably throw together a trivial API that only you can publish to fairly quickly if that is sufficient for what you are trying to do. I dare say chatgpt can spit out a simple rest API in whatever language you like quickly and pretty accurately.

I wouldn’t chase making a static website tool dynamic. That will almost certainly end in heartbreak.