from mietkiewski_dev@programming.dev to programming@programming.dev on 27 Apr 11:20
https://programming.dev/post/49470937
I was struggling to sit down and start my side projects, so I began reading more about productivity and motivation. Eventually I ended up writing a tiny Pomodoro timer for my terminal — mostly just to help myself get moving.
It’s super minimal: you enter the title, work time, break time, and number of intervals. At the end it generates a simple session report and asks you to write your own conclusion. I like reading my own reports later, so I added that feature.
I also enjoy reading short reports and summaries, so adding them felt natural. And honestly, I prefer building simple tools myself rather than hunting for the “perfect” app.
Works on Windows & Linux, needs only Python.
GitHub: github.com/Mietkiewski/MPomidoro
Gumroad PWYW $0+: mietkiewski.gumroad.com/l/mpomidoro
#programming
threaded - newest
Starting has always been the hardest part for me. Curious what helps you get going — I’m still figuring it out myself.
Finding music that locks me in is key.
Nice… Music definitely helps.
I feel like this might sound unhealthy of me but: The angrier/more frustrated I get, the better. Angry isnt bad in my head, angry at $thing gets shit done because I do not want to see it or have it in my head anymore than necessary.
Though I enjoy once I start even if I hate $thing since I like computers/coding/learning.
This single thing got me through university. I dont want to do $thing -> not doing it keeps it on my mind -> once I have a single minute free I will make a plan where to begin the thing -> when I have a good chunk of the time I may need for it I do it just so the thing is finally gone.
Healthy? Up for debate. Can’t argue with the results tho…
Edit: I am typically a very jolly and happy Person ^^ there is just this research and writing stuff in uni where it feels like pleasing some arbitrary line the prof drew ._.
Hey, could you remove the full Main.py from your comment? The project is closed‑source, so sharing the entire file isn’t allowed. Thanks!
It’s not though. It may not be FOSS, and by omitting a license you do keep the copyright by default, but it’s definitely not closed source either, it’s “source available”. Unless I’m missing the joke?
That comment is helping potential users vet your project before they use it, since not everyone has the motivation to go into the repo and take a look
Just to clarify — I don’t have any issue with people analyzing or quoting small parts of the code. The project is intentionally distributed on Gumroad as a “0$+” closed‑source release rather than as an open‑source GitHub repo. Since there’s no license file, it defaults to all rights reserved, which means full files can’t be redistributed.
Part of this project is also a learning exercise for me in how to package and distribute small tools. I’m genuinely interested in feedback on this approach.
But if someone posts the entire file publicly, it makes it harder for me to actually demonstrate the distribution model I’m experimenting with — the whole point was to release it through Gumroad, not as a fully exposed source dump.
I’m not a lawyer, but I would argue this actually means that even people who get it from Gumroad can’t use it “legally”. There should be a license which expresses your intent.
Buying the product gives people the right to use it — the license is only needed for redistribution or modifying the files. But yeah, you’re right that adding a license would make everything clearer. I’ll include one next time to avoid any confusion.
It’s implied, but it’s not clear - which is why whenever you “buy” software you actually buy a license to use it which clearly states how, where and by whom it may be used, on how many devices, under which conditions, etc etc etc.
That applies to licensed software. Here you’re not buying a license — just the right to use the tool. A license is only needed if someone wants to copy, modify or redistribute it.