_1tan

I built a collection of one-page printable templates for decisions, prioritization, and reflection. The twist: they're designed to be filled out with pen and paper, not digitally.

Why paper? Writing by hand is slow—and that's the point. When I type, I can outpace my thinking. When I write, I catch myself mid-sentence realizing "wait, that's not actually true." The friction is a feature.

What's included: - Decision Canvas (pros/cons + second-order effects + cognitive bias check) - Eisenhower Matrix (urgent vs. important) - Stop/Start/Continue audit - Rubber Band Model (what's pulling me forward vs. holding me back) - Cognitive Bias Checklist (pre-flight check before any big decision)

Tech: All templates are written in Typst. GitHub Actions compiles to PDF, generates PNG thumbnails, and auto-generates the README from metadata comments in each .typ file. Zero manual release process.

Philosophy: If a decision is easily reversible, don't use a template—just move. These are for the choices that keep you up at night.

GitHub: https://github.com/philippnagel/thinkingtemplates

I'd love feedback on which templates are actually useful vs. overthinking-theater, and ideas for new ones.

I work mainly in energy market communications and systems that facilitate energy trading, balancing and such. Currently most parties there take minutes to process messages and I think there could be a lot to learn from financial systems engineering. Any good resources you can recommend?

I manage a team of around 15 devs (small org) and currently some use the built in features of IDEA or GitHub Copilot - basic stuff.

I think, also from personally contributing a lot using Claude code, that we could use the tools better and in more areas like for example code reviews. Do you have any tips or strategies on introducing the colleagues in a sensible way to what's out there?

I built a tiny prediction market that lives entirely in GitHub Issues—no external database. Each market is a concrete question about repo work, e.g., “Will Issue #123 be closed by 2025-11-15?” Collaborators buy YES/NO shares to express beliefs, and the price (0 - 1) reflects the team’s collective forecast. This helps with planning, prioritization, and making expectations transparent - without real money.

Under the hood: signed JSON snapshots (market and ledger) embedded in issues, LMSR pricing, seq-based optimistic concurrency with retries, and collaborator-only trading.

I haven’t deployed a public instance yet for the repo - planning to do so after incorporating initial feedback. Repo: https://github.com/philippnagel/gantt

I’d love feedback on governance (caps per user, conflicts of interest), which questions are most useful (deadlines, PR merges, releases), and the UX of comment-driven trading.

I recently fell into a small rabbit hole and discovered the world model-based software development effort estimation. There are various models and tools like COCOMO (and the more recent COCOMO2) and others (See 1).

So far in my professional career, mostly in Start-ups I have yet to come accross anyone using those. Is this more common in langer orgs or government agencies? Are those helpful at all? Would love to learn about your experiences.

1: https://en.wikipedia.org/wiki/Software_development_effort_estimation#Comparison_of_development_estimation_software