Snippets and Thoughts of One Oracle Developer

I I live in Obsidian . My whole second brain sits in a git-versioned vault, and I open it every single day – for notes, work tasks, personal tasks, blog drafts, projects, everything. So if I'm staring at the same editor for hours, it might as well look the way I want. That's how I ended up building my own theme: One Oracle Developer . Catchy name, huh? It's a fork of the excellent Baseline theme, with a few tweaks on top. Why fork Create a theme from scratch is extremely demanding and time consuming. I checked all themes in Obsidian, and 95% of them were total garbage. Baseline was almost perfect, but I had to make a few small tweaks here and there so it works better with lists, checklists, and tags. I also adjusted the headers and fonts. The biggest issue was the folders/files tree, which felt a bit dull. Install Baseline and my theme and compare them yourself. What's different The theme is opinionated but small. Here's what it changes: Serif h...

F Four years ago I wrote Sharpen the saw . Same message still holds, but the saw changed. If you are still sharpening only what you know, you are sharpening the wrong thing. So let's do the uncomfortable check again. When did you last build something with AI (and I am not talking about few ChatGPT prompts)? When did you last try a new model, a new tool, or a new workflow? How much time did you spend last week consuming AI content vs. actually using AI to change something? Snowball with AI, or get buried by it Your knowledge is the small snowball. AI is the snow around. Used right, you compound years of experience into weeks of output. Used wrong, you generate plausible looking nonsense and call it a day. The point is not to let AI do your job. The point is to let AI do the boring 80% so you can go deeper on the part that actually needs you. Talking to users. Delivering value. If you are a senior and you still hand-write boilerplate code in 2026, you are burning ...

C Claude is great at many things, but it does not know your tools. It knows Oracle, it knows APEX, it knows PL/SQL. But it does not know ADT. So when you ask it to create a patch, it will hallucinate the commands and you will waste time fixing them. That is where skills come in. That is why I created ADT skills for you. What are skills? Skills are basically text files (SKILL.md) which you put in your project's ".claude/skills/" folder. When you ask Claude to do something, it reads these files first and follows the instructions. Think of it as a cheat sheet for Claude. You write the rules once and Claude will follow them every time. You can write skills for anything. Coding standards, naming conventions, deployment procedures, formatting rules. If you can describe it, Claude can follow it. I created two skills for ADT so far: adt and adt-setup . They are available on my AI_SKILLS repo . You can copy them to your project and adjust them to your needs. The ADT...