Live data from Hacker News

My Second Year as a Solo Developer

mtlynch.io

141–150 of 387 posts

Re: My Second Year as a Solo Developer

#141
post #47
post #39

Earlier quoted context omitted.

" I'd pick poverty over the lack of autonomy, petit politics and meaningless work any day." Would you also put your kids in poverty? It's not a simple when you think beyond yourself.

I haven't made the choice to have children and so it doesn't apply to me. That is your decision and that class of problem doesn't apply to everyone.

Well if you do, know that the $3k/mo saas that took 2 years to build isn't going to put that kid through college but will allow you to be a present and engaged parent to your child for the precious few years before they go to school.

Re: My Second Year as a Solo Developer

#142
post #102

Sorry to say but this proves that for someone who actually has to work for a living ie earn money, corporate life is absolutely the correct choice. Even for Mr Lynch these experiments in charity wouldn’t be possible without the nest egg from google (which he acknowledged). To go from net 100k+ to below zero and still be unprofitable after two years is a financial disaster.

Nah, but it's hard to launch a successfull product; if it wasn't, everyone would be doing it. I'm doing contracting work for multiple different customers, long-term project, and I generate 100-200k of revenue on a yearly basis from that. That leaves me with slightly higher salary than if I'd work for a boss, but I have tonnes, and tonnes more freedom and time for my kids. It's just not possible to scale that past 300…

While I generally agree with you that products can scale much higher than consulting income-wise, when you say it's impossible to scale what you're doing past 300k/year due to time constraints...why not charge more for your time? If you have more people asking you to do work for them than you have time for, I'd think that clients would be willing to pay more in order to make it onto your schedule.

Re: My Second Year as a Solo Developer

#143
I think it's especially important to make sure that you interview customers and find out what their problems are before you even think about writing a single line of code. You should strive to get a mix of qualitative (because the stories you hear will let you empathize with the customer problems) as well as quantitative via surveys / small ad experiments. Once you have some signal, then proceed to start exploring solutions (and again, this isn't about writing code, you can do this entirely with mockups/napkin drawings, whatever it takes to get your point across) and test those solutions with the customers you interviewed earlier. Once you have some evidence that a) you have a problem that customers will pay to solve, and b) you have a solution that you have validated THEN you proceed to start writing the code.

The biggest change at my company is doing product development this way: understand the customer problem and the solution before writing code.

Hope this helps.

Re: My Second Year as a Solo Developer

#144
post #130
post #3

Encouraging to see your progress, keep it up! Reading about your projects, it strikes me that some have different potential than others for perhaps one clear reason: solving a problem vs not. Why not double down on Zestful? There is demand there, and some are willing to pay... This post I wrote recently may be helpful for you: https://tinyletter.com/garybasin/letters/how-to-know-what-pe...

Hate to be harsh - but I wouldn't call this progress... I would call this going backwards. From what I can see he is drastically cutting back his lifestyle and all living costs and calling it a profit? The business and enterprise of being s solo dev itself is failing enterprise. My advise (From experience) would be to be doing some outsourced/freelance work at this stage to help fund your projects.

Cutting back on one's cost of living can easily still be progress. If he's doing this to get rich, I would agree he is failing. However I don't think thats the idea. I think he wanted a different lifestyle, and one that was more self-directed. Through that lens, an astounding amount of progress has been made.

Re: My Second Year as a Solo Developer

#145

Earlier quoted context omitted.

Thanks! TBH, I just got bored. All of the inefficient aspect of my work got slowly eliminated over the years due to process improvements, which meant that only the most unpleasant, manual aspects were left over (read: legal, negotiation, business development, etc.). 80% of my income was consulting related. I tried to branch off into making a SaaS and "failed" (which I'm still kind of excited about but have no time to…

> iled" (which I'm still kind of excited about but have no time to pursue), but I did succeed in making an App Store portfolio which brings in decent profit. can you share what you did consult on? To me consulting is very mysterious as it's a very generic term but I'm always amazed by people earning 250K-500K due to "consulting". Is it easy to do or more like being in the right place/right time/right skillset?

> can you share what you did consult on? To me consulting is very mysterious as it's a very generic term but I'm always amazed by people earning 250K-500K due to "consulting"

Totally. I'm a generalist software engineer with a specialty in early stage startup tech. In addition to actually writing the code, setting up infrastructure (AWS and all that), and anything explicitly code or "DevOps" related, I also helped clients understand the development process, advised them on product, worked with designers, etc.

I agree that consulting is kind of a nebulous term, but if you ask me, it's essentially shorthand for "solving problems that people have that they can't (or don't want to) solve themselves". The problems that clients came to me with were all related to getting a startup off the ground from the technical side.

Re: My Second Year as a Solo Developer

#146

Earlier quoted context omitted.

You could probably talk to business owners with problems, launch an (appropriately priced; hundreds to thousands of dollars per year) product against those problems, build contingent on getting 10 commits to buy I don't doubt that you're absolutely right, but this bit strikes me as hard . I've struggled to find one business owner with a problem they perceive, let alone 10 with commitments to buying a solution for the…

> Ironically, it strikes me that there's a gap here for a business to solve; connecting entrepreneurial devs with business owners aware of problems. This. Why hasn't this gap been filled yet?

Elance? Odesk? There are a fair number of players in the "find a dev to solve a one-off business problem" space. The issue is that this is a market for lemons[1] on both sides - for business owners with problems, it's hard to verify that the entrepreneurial devs can actually implement a solution, and for the entrepreneurial devs it's hard to weed out problem clients.

Someone who solves or even slightly mitigates either of these issues will have a viable business. I know that for the "ensure the dev is competent" side of things there are many consulting companies that live and die by their reputations, but generally these don't usually scale up beyond a certain size, and when they do their reputation deteriorates. I am not aware of any businesses that attempt to solve from the flip side and weed out problem clients (if anyone is aware of such a service, I would be interested).

As if that wasn't enough of a challenge, if you do manage to connect quality devs to quality clients, there's the issue of sufficiently monetizing that relationship: you can charge a finder's fee or similar when you first connect them, but once a client finds a dev they like they will probably stick with that dev. So in that business you can lose business because you match people too poorly (and they leave because you can't help them) and you can lose business because you match people too well (and they leave because they've now found somebody they trust so they don't need your services anymore).

[1] https://en.m.wikipedia.org/wiki/The_Market_for_Lemons

Re: My Second Year as a Solo Developer

#147

Earlier quoted context omitted.

Most of my consulting work was with early-stage startups. I would ofter offer a fixed cash cap (say, $50k) at an hourly rate, and any work beyond that would accrue towards a SAFE. Less risk for the founder, gave me incentive to finish the bulk of the work within the cap, but also didn't punish me if I didn't.

what was your hourly rate on consulting?

$300 / hour.

Re: My Second Year as a Solo Developer

#148
post #79

Two cents offered because this post really strikes a chord with me, and I also spent some time chasing down rabbit holes early in my software business: These products do not appear obviously commercializable and multiple years invested into them without materially improving the businesses does not decrease my confidence in that snap judgment. You could probably talk to business owners with problems, launch an (approp…

Thanks for reading, Patrick! I'm a big fan of your work, and your Indie Hackers interview was one of the big motivators that sent me down the solo developer path.

>You could probably talk to business owners with problems, launch an (appropriately priced; hundreds to thousands of dollars per year) product against those problems, build contingent on getting 10 commits to buy, and be at +/- $100k in 12 to 18 months. Many people with less technical and writing ability have done this in e.g. the MicroConf community. If you want the best paint-by-numbers approach to it I've seen, c.f. https://www.youtube.com/watch?v=otbnC2zE2rw&t=2s

Thanks, I'll check out that video!

I hear that advice a lot from people I respect, and I put a lot of effort into that over the past year, but I was never successful.

The biggest problem I ran into was that there's this "disconnect problem." I know I'm a competent developer and can build niche solutions to $10k problems, but I don't know which companies have $10k problems. I can guess at it, but they sometimes don't even realize their $10k problem has a software solution. The companies also don't have incentive to talk to me to explore the possibility if I'm just a developer off the street.

In 2019, I tried to do this with stone quarries[1], sheet metal shops[2], and email copywriters[3], but the first two mostly wouldn't talk to me and the latter didn't seem to have enough opportunity for a niche business.

>I would encourage you, to the maximum extent compatible with your sanity, to prioritize "Will this get me more customers?" over behind-the-scenes investments like CI/CD which are very appropriate to Google but will under no circumstance show up in next year's report as One Of The Most Important Things I Did This Year.

I get a lot of pushback about my love for CI/CD, and it always puzzles me. Is CI/CD seen as difficult or time-consuming? For me, it's such a net positive on my time and mental energy to know that basic functionality works before I push to prod. There have been many times where CI has caught breaking changes that I'd otherwise have to catch by waiting for customers to complain or manually smoke testing my product after every push. And I don't have to do much to set it up - just slap in a Circle CI config.yml and flip a button.

>I would suggest devoting approximately zero cycles to cost control. You don't have a cost problem and no amount of cost control will bend the curve of your current businesses to sustainability. You have a revenue problem. Your desired state in the medium term will make it economically irrational for you to think for more than a minute about a $50 a month SaaS expense; marketing and sales gets you to that desired state, not cost control.

Thanks, I agree completely and you succinctly articulated a feeling I've long struggled to put into words.

I often get pushback about spending O(hundreds) of dollars on non-essential expenses, and it always feels like it's missing the forest for the trees.

[1] https://mtlynch.io/retrospectives/2019/05/#an-app-for-rocks

[2] https://mtlynch.io/retrospectives/2020/01/#sheet-metal-resea...

[3] https://mtlynch.io/retrospectives/2019/06/#taking-on-google-...

Re: My Second Year as a Solo Developer

#149
post #79

Two cents offered because this post really strikes a chord with me, and I also spent some time chasing down rabbit holes early in my software business: These products do not appear obviously commercializable and multiple years invested into them without materially improving the businesses does not decrease my confidence in that snap judgment. You could probably talk to business owners with problems, launch an (approp…

You could probably talk to business owners with problems, launch an (appropriately priced; hundreds to thousands of dollars per year) product against those problems, build contingent on getting 10 commits to buy I don't doubt that you're absolutely right, but this bit strikes me as hard . I've struggled to find one business owner with a problem they perceive, let alone 10 with commitments to buying a solution for the…

Yeah, this is why I have been working as a data analyst. I've taken on as many vendor management responsibilities as I can and help out with COGS and revenue attribution analysis for finance. I have been collecting ideas while making steady wage, and eventually I'll pull the trigger on something

I have a backlog of like 200+ viable new product / feature ideas that help solve some business problem or improve the efficiency of activities people do with financial transactions involved. Many are too small to be stand alone for sure, but I do not believe million dollar ideas are grown in a silo

Re: My Second Year as a Solo Developer

#150
post #79

Two cents offered because this post really strikes a chord with me, and I also spent some time chasing down rabbit holes early in my software business: These products do not appear obviously commercializable and multiple years invested into them without materially improving the businesses does not decrease my confidence in that snap judgment. You could probably talk to business owners with problems, launch an (approp…

Looks like this guy is trying to run a lifestyle business, and his investments pay enough interest that he can coast for a long, long time.

To be quite honest: He's spending all day playing.

That's a position I envy quite a bit.

Post reply on HN