<feed xmlns="http://www.w3.org/2005/Atom"> <id>https://kevinpanko.xyz/</id><title>Kevin Panko</title><subtitle>Kevin Panko's personal web site.</subtitle> <updated>2026-05-31T21:54:45-04:00</updated> <author> <name>Kevin Panko</name> <uri>https://kevinpanko.xyz/</uri> </author><link rel="self" type="application/atom+xml" href="https://kevinpanko.xyz/feed.xml"/><link rel="alternate" type="text/html" hreflang="en-US" href="https://kevinpanko.xyz/"/> <generator uri="https://jekyllrb.com/" version="4.4.1">Jekyll</generator> <rights> © 2026 Kevin Panko </rights> <icon>/assets/img/favicons/favicon.ico</icon> <logo>/assets/img/favicons/favicon-96x96.png</logo> <entry><title>The Day FORTRAN Made Sense</title><link href="https://kevinpanko.xyz/posts/the-day-fortran-made-sense/" rel="alternate" type="text/html" title="The Day FORTRAN Made Sense" /><published>2026-05-31T21:46:00-04:00</published> <updated>2026-05-31T21:46:00-04:00</updated> <id>https://kevinpanko.xyz/posts/the-day-fortran-made-sense/</id> <content type="text/html" src="https://kevinpanko.xyz/posts/the-day-fortran-made-sense/" /> <author> <name>Kevin Panko</name> </author> <category term="software" /> <summary>I used to work in physical simulation of jet engines on supercomputers. Fortran was one of the languages of choice due to being very efficient while still being usable by the physics and math people. I always wondered why Fortran was a little loose with its syntax around spaces. Most languages let you use any amount of whitespace between tokens, so x = 1 and x=1 are the same thing. But...</summary> </entry> <entry><title>Stop Reaching for rm -rf</title><link href="https://kevinpanko.xyz/posts/stop-reaching-for-rm-rf/" rel="alternate" type="text/html" title="Stop Reaching for rm -rf" /><published>2026-01-18T14:53:00-05:00</published> <updated>2026-01-18T14:53:00-05:00</updated> <id>https://kevinpanko.xyz/posts/stop-reaching-for-rm-rf/</id> <content type="text/html" src="https://kevinpanko.xyz/posts/stop-reaching-for-rm-rf/" /> <author> <name>Kevin Panko</name> </author> <category term="software" /> <summary>If your muscle memory for deleting a directory is rm -rf, you’re doing what most Unix users do—and you’re taking on risk you don’t need. -f doesn’t mean “force, but safely.” It means disable the guardrails. (See the official documentation: rm(1)) It suppresses prompts, ignores permissions, and hides information that would otherwise tell you you’re about to do something dumb. A safer default...</summary> </entry> <entry><title>Leetcode Is Not Engineering</title><link href="https://kevinpanko.xyz/posts/leetcode-is-not-engineering/" rel="alternate" type="text/html" title="Leetcode Is Not Engineering" /><published>2026-01-13T21:37:00-05:00</published> <updated>2026-01-13T21:37:00-05:00</updated> <id>https://kevinpanko.xyz/posts/leetcode-is-not-engineering/</id> <content type="text/html" src="https://kevinpanko.xyz/posts/leetcode-is-not-engineering/" /> <author> <name>Kevin Panko</name> </author> <category term="software" /> <category term="career" /> <summary>LeetCode Is a Filter — Just Not for What You Think There’s a belief in the software industry that a strong LeetCode profile means something important. It doesn’t. Or more precisely: it means something, just not the thing people think it means — and not the thing you want if you’re trying to hire good engineers. This isn’t a beginner’s take. This is the perspective you arrive at after you’ve...</summary> </entry> <entry><title>The January Contract Freeze</title><link href="https://kevinpanko.xyz/posts/the-january-contract-freeze/" rel="alternate" type="text/html" title="The January Contract Freeze" /><published>2026-01-08T21:09:00-05:00</published> <updated>2026-01-08T21:09:00-05:00</updated> <id>https://kevinpanko.xyz/posts/the-january-contract-freeze/</id> <content type="text/html" src="https://kevinpanko.xyz/posts/the-january-contract-freeze/" /> <author> <name>Kevin Panko</name> </author> <category term="career" /> <summary>Every January, I watch large organizations hit themselves in the face with the same rake. Everyone knows the work is coming. The teams are staffed. The roadmaps exist. I’ve already sat in the meetings where people talk confidently about what we’ll build this year. And then January arrives—and suddenly, no one is allowed to work. Contractors are benched. People are told to burn PTO. Middle man...</summary> </entry> <entry><title>Almost Found a Github Security Hole</title><link href="https://kevinpanko.xyz/posts/almost-found-a-github-security-hole/" rel="alternate" type="text/html" title="Almost Found a Github Security Hole" /><published>2025-05-31T21:46:00-04:00</published> <updated>2025-06-01T19:53:24-04:00</updated> <id>https://kevinpanko.xyz/posts/almost-found-a-github-security-hole/</id> <content type="text/html" src="https://kevinpanko.xyz/posts/almost-found-a-github-security-hole/" /> <author> <name>Kevin Panko</name> </author> <category term="software" /> <category term="github" /> <summary>Recently, I was working through a class on github and almost found a way to break the security protocols and write to a repo that belongs to someone else. In the course, the instructor shows people how to fork his repository and then shows what it looks like when he deletes a file from it. The thing is, I do not own that repo so I am not allowed to do that myself. I wanted the full experience...</summary> </entry> </feed>
