From Kyiv, in Kyiv.

  • 5 Posts
  • 159 Comments
Joined 5 个月前
cake
Cake day: 2026年2月4日

help-circle









  • According to Vaganov, most of the accusations boil down to the idea that if a person disagrees with the current authorities, they must necessarily “want to overthrow the political system.”

    Seems queer people have no other choice but to become the force that the government portrays them as. When a regime actively wants you dead, you must kill the regime before it kills you. Trying to play safe and apolitical may buy some time, but unless that time is spent organizing for power, not for tea parties, the results will be very sad.

    I don’t blame people for emigrating, but I hope they don’t, and that they radicalize instead. They are much stronger than NGO heads and other politicians made them believe.






  • Not the first time I’m reading this text, and I still don’t get a lot of it. Their previous form was ASP-based, which is also server-rendered, so which developer practice exactly doubled the number of users? Doubled compared to what? Did the marketing department also get a boost at the same time, and the updated website got better advertising somewhere? How did 96% satisfaction get calculated earlier, if there were so many users whose needs were not met? Where does the “20MB of javascript before we even render a form” number come from? What does “global javascript states” mean, regarding their previous React replacement attempt, and why is it bad, because MobX singletons used to be an actually pleasant, maintainable pattern in my practice? Was the previous replacement attempt vibe-coded, and who made the decision to have developers do it like that? Given the choice of Astro as the platform, and the suggestion of Remix, what makes the developer so sure “it will still work 30 years from now”, because these are much more complex targets than just React?



  • Sorry for the usual annoying question but have you received my e-mail from June 12th? I sent portfolio links and some more clarification questions. I’ve just found out that Gmail has placed my letters in spam folders this month; maybe Yahoo does, too.

    Regarding hardware, I didn’t ask because I assumed that if hosting is handled by administrators, they will take care of assessing and renting a capable server. My apps usually start on a €10/m Hetzner VPS and as they grow, admins upgrade plans or move it where it’s convenient for them. For media content, one client added a CDN later to an existing project, while others found a dedicated server provides enough bandwidth for their needs. Best experience with Debian and Alpine servers. One client wanted Windows, their IT staff took care of managing it so I’m not familiar with deployment to that platform. With GNU/Linux, musl and FreeBSD servers I had different levels of involvement, from sending the manager a Docker image or a repo and having their staff install and run it on their own, to full root, hosting and DNS access and me being paid for installation, documentation and a few hours of support every month.

    The primary interesting thing about your project is for me that nobody’s going to mess up my code with unreviewed LLM patches, and that it’s supposed to help indie artists who I assume are politically progressive and curious about free software.




  • EDIT: Other quotes I’ve gotten are $5,000 / $14,000 / $15,000 / $38,000 so the $7,000 estimate actually seems really low by comparison. Clearly the amount of features I’ve requested are quite challenging.

    Interesting, do estimates of hours also differ a lot? Do responders who have more senior qualifications estimate particular tasks as more difficult, according to their experience? I’m fairly confident that my estimate matches the tools I’m familiar with, but at the same time I’m neither still junior nor yet senior and might have underestimated some tasks, particularly those related to communication inside the team, because I’m used to working solo.


  • Thanks for the outline! Some follow-up details:

    Versions and categories. Does a category mean a comic, and a version mean a language? Are files uploaded in bulk?

    Blog and news. Is news meant for a specific creator, while the blog is for the website itself?

    Achievements. What should be tracked for a user to gain an achievement?

    Access control. To unlock a chapter, either: a user enters an access code; an administrator types their name into a form; or a Patreon monitoring script unlocks it automatically for a group of users according to some logic?

    Email server. Can you tell more about this part? What do automated responses involve?

    Appearance. Do you have mock-ups, particularly for the landing page and the about-us page? Maybe a design system? I can use generic daisyUI or Bootstrap components to make it look okay, but I’m not a designer myself, though I’ve taught an introductory design course for teenagers.


    Notes about requirements:

    Filesystem. I can store images outside the document root, and deny a file to a reader unless access control allows their signed-in account.

    JavaScript. I’d like the front end to be a server-rendered SPA, using Preact and Vite. This means the reader pages will load and be usable without client-side JavaScript. But some JavaScript will be used for interactivity, especially in the admin section.

    Mobile and Firefox. I daily-drive Fennec on Android, Firefox on Windows and Falcon on Debian, so these are the platforms I can ensure it works fine on.

    No-AI. You can and should review that anything I code for your project does not include anything LLM-generated; btw, I’m interested in what tools you use for that. However, the bundle returned to the client will include code of dependencies, and I know that developers of many libraries and tools do allow AI contributions, for example it’s in Valibot and Vite, to which I don’t know good alternatives. I will ask you to plan the contract in a way that doesn’t hold me responsible for LLM usage by other people.

    Maintenance. I do write documentation for every project that I author. It’s not very extensive, usually a README about installation, structure and some usage tips. Developers whom I onboarded to projects of my employers told me they appreciate it, but they rarely update my initial documentation on their own later. I’ll be interested in your experience with improving this.


    My ballpark estimate is 120 hours for the initial release with the features you mentioned. Programming further updates to the website can be negotiated as needed. From what I found $58/hour is an average wage of full-stack developers using my preferred technology in the USA in 2026, so this is what I’ll ask.

    Note that with my availability (day job, university, other clients) I can only allocate 10-20 hours per month. I use Kanboard, make periodic reports about what’s ready, and we can monthly discuss the priority of what features should be ready next.

    In case the website ever shuts down, can you then release the code with a free software license? I haven’t yet worked on a project with a policy like that, but I saw this the idea on fedi more than once, and I liked it; this is how Firefox and LibreOffice came to life.

    For further contact, do you have Delta Chat or XMPP, or how is it better to chat with you and other project members? What’s your timezone, and are you ok with not very fast responses, because I don’t spend much time on social media? I’m from Ukraine, EET/EEST (UTC+2/3).


  • What’s your project, and are you comfortable with implementations based on Node.js and/or WordPress? I’m quite busy until the end of summer, but open to taking a project later if it sounds interesting. Regarding the quote, what’s your country? I believe people from the U.S. should pay me the same they would their own countrymen, while for my Eastern European neighbors my rate is different. I still haven’t ever used AI for coding, but I use it as a summarizing assistant when writing university notes - it hallucinates a lot but helps me fight procrastination; a skeleton with mistakes that I can correct after carefully reading the sources is better than a blank page endlessly waiting for a good first sentence.