Next month? I got a merry Christmas on Thanksgiving. I was insulted.

I appreciate a simple piece of software that does exactly what it’s supposed to do.

This is the way to do it. If you’re paying for your whole PhD, you’re doing it wrong.

He does know how to get down on his knees.

We need to stop saying “American Dream.” It’s really beating a dead horse at this point. It feels like such a fictional concept to me.

My friends and I talked way back in school about how further engineering education was negatively correlated (not exactly: see comment) with pay after a bachelors and was statistically a terrible deal.

EDIT: That’s not to say it’s worthless! But it ain’t worth what they’re charging. There isn’t actually a negative correlation in the strict sense but rather there isn’t clearly a premium for the degree in all markets. You can be taking a straight up financial loss. The original statement was inaccurate, but that’s historically what we told each other.

It’s how you use it.

This doesn’t look like Arch.

I have a simple pile of Markdown files that I edit with Obsidian. I like the simple text file format because it keeps my documentation forwards-compatible. I use OpenWRT at the heart of my network, so I keep I right there in root’s home. Every long while I back it up to my general Documents which is then synced between my high-storage devices with SyncThing.

It’s the first feature I disabled. It’s like they never considered I might place an item on the backseat.

I remember seeing this article before. Keep in mind that the publisher of the report has a financial interest in promoting their AI’s “agentic” capabilities. In the report they state that AI can replace skilled teams of hackers. For a target taking security even somewhat seriously, that statement is hard to believe and really underlines their financial incentive.

I argue this isn’t novel at all. At the end of the day, you’re still generally scanning the Internet for vulnerable systems. Script kiddies have been using this broad recipe for decades. I think this is more accurately an incremental improvement in automation rather than the paradigm shift that Anthropic would have you believe.

Santa Ragione

An unmanaged switch is a simple, zero-configuration network device that connects multiple Ethernet devices together. This is by far the most common type of switch because they’re cheaper to make and satisfy most needs in the home and small office. There are no settings to configure, and the device generally avoids inspecting the traffic it switches. Unmanaged switches are commodity products that are all pretty much same, varying only in the number of ports and speeds provided. These are made in large volumes.

Managed switches add a central processor (CPU) for device administration. This design enables configuration settings which is usually an important precursor to have features such as VLANs, QoS, IGMP snooping, and port security. Businesses need managed switches to implement security policies. In addition to the added hardware, businesses have deep pockets, and managed switches are no longer simple commodities because comparing the advanced feature set and software is no longer trivial. Professional managed switches can cost thousands.

Only recently have we seen pro-sumer switches occupy the space in between these two options by offering some managed features (VLANs) while reserving necessary enterprise features (port security, DHCP snooping, reporting) to segment the market. I bought one for $25 the other day which is almost the same as an unmanaged switch. I would no longer recommend buying an unmanaged switch to anyone with even a passing interest in home networking.

An intern at work once asked me what a CD was and I had to explain that it was a vinyl for computers.

WOO.

I want a wallpaper.

It’s an excellent case in point for why they don’t care at all about laws. They just want to hurt people.

I hardly have a doctor (Who can afford that?) but I use the insurance website to search for nearby providers because coverage is most important to me. Then, I look at reviews of their offices on Google Maps before calling to see if they’re taking new patience for final selection.

You’re kind! I enjoy reviewing and talking about code. Anytime.

Sr. Software Engineer here!

• Great job initializing your variables. That’s a surprisingly common source of bugs, and with today’s optimizing compilers it’s basically free to define the starting value at the beginning of your function. Don’t worry if you reassign the value later. The compiler will notice and won’t waste any time doing extra setup unless it actually matters.
• Consider providing an error message for invalid inputs. Humans can be boneheaded and not realize they gave an invalid input.
• Your code isn’t commented. I recommend considering adding a few to build good habits early if you think you could comment something helpful for the reader. Code is read far more often than it is written ideally.
• You perform your math operations twice: once in the printf and again later when you assign memory. Consider doing the computation just once to avoid repeating yourself to the computer. This habit tends to produce more efficient programs. Just update memory first and then reference it directly in your call to printf. This also protects against bugs where the value displayed wasn’t really the value written to memory.
• Consider checking for division by zero and provide an error message for the unreasonable request.
• Maybe return a non-zero status if an error occurs.

Nice work!