I made a little hobbyist app for myself, and I think it's pretty nice and occasionally think about polishing it up and releasing it. And the first reason I don't is because I'm not interested in promoting it, and it's pretty pointless to release to no one. But the much bigger reason is because I'm not interested in implementing the remaining 80% that I don't use myself.
I also made several hobbyist apps for myself. Sometimes I thought what if I just posted it as a Show HN, but I am just rarely in the mood for implementing features others ask for, outside of work which pays me enough that I'd oblige.
I made a little hobbyist app for myself, and I think it's pretty nice and occasionally think about polishing it up and releasing it. And the first reason I don't is because I'm not interested in promoting it, and it's pretty pointless to release to no one. But the much bigger reason is because I'm not interested in implementing the remaining 80% that I don't use myself.
I made one plugin for myself and released open source in github. The amount of, sometimes hostile, request I had to implement stuff I did not care made me stop the development.
I made a little hobbyist app for myself, and I think it's pretty nice and occasionally think about polishing it up and releasing it. And the first reason I don't is because I'm not interested in promoting it, and it's pretty pointless to release to no one. But the much bigger reason is because I'm not interested in implementing the remaining 80% that I don't use myself.
I made a little hobbyist app for myself, and I think it's pretty nice and occasionally think about polishing it up and releasing it. And the first reason I don't is because I'm not interested in promoting it, and it's pretty pointless to release to no one. But the much bigger reason is because I'm not interested in implementing the remaining 80% that I don't use myself.
I also made several hobbyist apps for myself. Sometimes I thought what if I just posted it as a Show HN, but I am just rarely in the mood for implementing features others ask for, outside of work which pays me enough that I'd oblige.
It's been 25 years now but this exact thing is why I switched majors away from CS in college, I decided back then that I didn't want an employer/client telling me what to build. I liked software as a hobby but think it would have been a miserable profession (for me, not projecting to anyone else).
I didn't read the article but in my experience, 80% of the application are parts that you rarely touch, config stuff and "LEFT JOIN" stuff. There is always one or two parts where all data comes together and that is the heart of your application. Yeah those are the parts your users care about and pay you to make.
It's against the rules to say this, but it would definitely help to actually read the article.
The best decision I ever made was moving from a company that acted on the whims of whomever the sales team spoke to last, to a company that had a strong product vision and was happy to say no to their customers on occasion. It's a lot less exhausting when you're not changing priorities every quarter. You also avoid the soul crushing experience of working really hard, crunching to get a feature out, only to realise yo…
This is one of the things I try to suss out when I interview somewhere. Do you have a product team (or at least someone in leadership) with a stable requirements vision, or do you just haphazardly develop based on whoever your sales team last talked to. Having a stable roadmap is an absolute requirement for me. I may not agree with the roadmap or priorities, but I'd rather have them than not have them. I've worked in…
Another thing to be wary of is a product where there are a small number of customers, maybe even just one, who contribute the vast majority of the revenue. Because then, even with a good product vision, it's going to be very hard to say "no" to what they ask for.
"Your application"? That post talks about Microsoft Office. That's the giant corporation + the government's application. Give LibreOffice as an example if you want to talk about large apps that can be "yours", at least partially.
And indeed, we should make sure the apps we write are FOSS, so that those users who care about those various 20%'s feel that its also "their application", and may actually help out - with money or code or time.
He also pioneered 'velocity tracking' for SWE tasks. Seems like a major disservice in hind sight. But then again I don't think I can't blame him for Agile and Jira.
But I think he's the only one to have done it right. I've never seen velocity tracking correct for measured inaccuracy in each developer's estimates. I've tried so many times to implement his EBS approach, but no one wants to do it.
Sure. If I remember the details correctly it was some sort of individual approximation of 'veolicity story whatever points' too, to make it less arbitrary and obviously stupid to KPI-PIP-stack rank people with.
I made a little hobbyist app for myself, and I think it's pretty nice and occasionally think about polishing it up and releasing it. And the first reason I don't is because I'm not interested in promoting it, and it's pretty pointless to release to no one. But the much bigger reason is because I'm not interested in implementing the remaining 80% that I don't use myself.
If you're not releasing it as a product for sale, there's absolutely no obligation to promote it, or add any features that you don't use. People can use it as-is if it fulfills a need, or fork it and add what they think is missing.