Posts

Showing posts from November, 2026

IntelliJ keeps opening your .xlsx files? Here is how to stop it

You double-click a .xlsx in the Project view, expecting Excel to open, and instead a tab appears inside the IDE. Maybe it renders correctly, maybe it shows a wall of XML. Either way, the file is now open somewhere you did not intend, and the editor you wanted never launched. This is not a bug and it is rarely caused by the IDE core. It is a file type association , and it is one setting away from being undone. The harder part is knowing which component claimed the extension, because it might be a built-in module you never installed on purpose, or a plugin you added months ago and forgot about. Why an IDE claims a file type at all Every IntelliJ-based IDE has a FileTypeManager that maps extensions to a parser. When you open a file, the IDE asks that manager which parser to use. If something registered .xlsx , the IDE opens it internally; if nothing did, the OS opens it with the default application. The mapping is layered. Built-in modules register their formats at startup. Plugins regi...

Why plugins corrupt your .xlsx files (and how to check before it happens)

A corrupted .xlsx file is almost never the result of a bad library. It is the result of a save operation that was interrupted, or a write that replaced more of the file than it needed to. The distinction matters, because the first is a design flaw you can detect in advance and the second is a silent one you usually discover days later. If you have ever installed a spreadsheet plugin, opened a workbook, changed one cell, and found the file unopenable afterwards, you have hit one of the three failure modes below. All three are avoidable, and none of them require the plugin to be malicious — just careless about a file format that punishes carelessness. The format that makes corruption easy An .xlsx file is a zip archive. Inside it there is a shared strings table, one XML part per worksheet, a styles part, and — critically — a _rels directory that records how all those parts reference each other. That last piece is what separates a spreadsheet from a text file. Excel does not store ...

Why Task Manager Says 95% Memory When Nothing Is Running

You open Task Manager on a machine that feels sluggish. Memory is at 94%. You scroll the process list and add up the big ones: browser 2 GB, everything else maybe 3 GB total. That is 5 GB on a 16 GB machine. So where did the other 10 GB go? This is the most common memory question I get, and the answer is almost never "you have a leak." It is usually that the number at the top of Task Manager and the numbers in the list below it are measuring different things, and neither one means what people assume. Here is what each number actually is, which ones you can ignore, and the one that is worth worrying about. The number at the top is not "used by programs" On the Performance tab, the Memory panel shows four things that matter: In use — pages currently held by processes, drivers, and the kernel Available — memory that can be handed to a process right now Committed — total private memory promised to processes, including what is backed by the pagefile Cached — file dat...

Windows 11 Is Full and It's Not Your Apps: Where the Space Actually Went

You uninstalled three games, moved your photo library to an external drive, and cleared the Downloads folder. The drive is still red. I have been through this on four machines now, and the conclusion is always the same: the space is not in your apps. It is in four places Windows never shows you in a normal file listing, and one of them is almost certainly the biggest. This is how to find out which one, without deleting anything you will miss. First: stop deleting things The instinct when the bar turns red is to start removing files. That is the wrong order. You cannot fix a space problem you have not measured, and "delete stuff until the bar goes green" is how people lose the only copy of a document. Spend ten minutes measuring first. Everything after that is a decision, not a guess. Step 1: Read the storage breakdown Settings → System → Storage gives you a bar chart of what Windows thinks is using space: Apps, Documents, Pictures, Temporary files, and so on. It is useful for...

The spreadsheet that ate my test suite

I lost half a day to a spreadsheet last month. Not to the data in it — the data was six rows of test fixtures. I lost the time to the fact that every tool I tried either could not open the file, or opened it and then quietly damaged it on the way out. That experience is not unusual, and it points at something most developers get wrong about .xlsx files: we treat them like documents, when they are actually small databases wearing a zip archive. A spreadsheet is not a document Rename an .xlsx to .zip and open it. Inside you will find a handful of XML parts: a shared strings table, one part per worksheet, a styles part, and a relationships index tying them together. Excel never stores "the grid". It stores cells with type annotations, and every visual property — the column widths, the fills, the merged ranges — lives somewhere else, referenced by index. Once you know that, the failure mode becomes obvious. A tool that reads the whole workbook into a generic representation and...