Live data from Hacker News

Getting to 2M users as a one woman dev team [video]

brightonruby.com

111–120 of 303 posts

Re: Getting to 2M users as a one woman dev team [video]

#111
post #98

Earlier quoted context omitted.

[flagged]

[flagged]

It’s sad that text got flagged. Which proved a point.

I voted up. Words and behavior matter.

If your identity is so hung up on being a man and believing that men are “better” than women, your identity is a frail illusion.

Try to imagine being so “weak” that you can’t accept that there are women who are successful and some do better than you.

Re: Getting to 2M users as a one woman dev team [video]

#112

Earlier quoted context omitted.

It's due to fear. Fear of breaking something that may depend on that bad code. Test automation rarely covers every possible case, and nobody wants to be on the hook when some code changes cause other stuff to break.

And for all of the benefits of process, I have never met a level of documentation, verification, or testing that matches the advantages of having the entire code base originating from one mind. Generally this is not tractable because it cannot scale. But there are certain applications where it scales fine.

I don't think we need nearly as many devs as we think. We do need someone who is taking a hardline approach on limiting the amount of scope tackled at once, and then fewer devs that are downstream of that.

It is hubris to think that every problem admits the same solution, namely, throw as many devs as we can at it and hope for the best. But business isn't really known for being reflective.

Re: Getting to 2M users as a one woman dev team [video]

#113
post #25

Earlier quoted context omitted.

> Are there any other products with such a small team and a huge userbase? My game Nebulous was 1.5 devs (one full time one part time) and multiple millions of MAU. 9.5 years later it's still going well. > when the business requires more coding and technical debt comes how do they manage it Delete bad code. Replace with good code. Sounds simple enough but in my experience at mega and mid corps, step 1 is almost never…

Fleet commander or I'm guessing .IO?

.io. There have been more Nebulous's since I last checked :)

Re: Getting to 2M users as a one woman dev team [video]

#114

Earlier quoted context omitted.

[flagged]

I wish I could say it's surprising to me, but I've been here for a while. Hackers are not the philosopher kings that a generation before hoped they would be.

[dead]

Re: Getting to 2M users as a one woman dev team [video]

#115
post #110

Earlier quoted context omitted.

[flagged]

You're the only person who used "woke" in this thread, at the time of my comment.

Look harder, there are several- at least three comments older than yours say "woke" in them. Several comments have also been flag killed and the replies suggest they said something effectively synonomous

Re: Getting to 2M users as a one woman dev team [video]

#116
post #95

Pretty nice, 1 dev 3 team members in total and 1 million users? Are there any other products with such a small team and a huge userbase? Does this scale and when the business requires more coding and technical debt comes how do they manage it?

I owned a website with over a million users. Used cloudflare and a $20 cloud instance to run it. Also relied on certain other CDNs. Don’t own it anymore, but considering starting a new project.

What was the app about?

Re: Getting to 2M users as a one woman dev team [video]

#117

Looks like a pretty cool app! "Amazon-free Goodreads" is a pretty good pitch. I'm curious how freemium model works out for them though, I could imagine a lot of people thinking the free version is good enough for them.

My wife loves Storygraph, and has said that she thinks they give away too much for free and need to put more value behind premium.

Re: Getting to 2M users as a one woman dev team [video]

#118
post #201

[stub for offtopicness] [good grief]

[flagged]

The person who submitted this followed HN guidelines which state to use the original title of the article. I'm not sure why people need to freak out. HN didn't name the content, the content publisher did.

Re: Getting to 2M users as a one woman dev team [video]

#119

Earlier quoted context omitted.

It's due to fear. Fear of breaking something that may depend on that bad code. Test automation rarely covers every possible case, and nobody wants to be on the hook when some code changes cause other stuff to break.

That, and most orgs simply do not reward or even pretend to care about these kinds of improvements. If you delete bad (but working) code, and replace it with good (and, let's assume best-case scenario - also working) code, what has actually changed for the business? Nothing. Except that in 3 years the junior dev that gets a ticket about doing something in this area will come in and not notice the code isn't a dumpste…

One of the most rewarding aspects of my previous career at a company spanning from a startup to an IPO and beyond was deleting bad code and replacing it in a massive Rails app that was touched by hundreds of devs in a high churn environment. I also took on fixing massive schema inefficiencies that had a lot of risk of breaking nearly every other team's flow. It took a lot of careful work and communication across multi-year goals that I managed, mostly alone. I was allowed to do this by a few early folks who believed I was doing a good service for the company in the long run but kept hinting it was a bad career choice for me personally. I believe I was eventually let go for making these massive improvements instead of adding that green button that the new Product guy wanted. No regrets.

Re: Getting to 2M users as a one woman dev team [video]

#120
post #106

Earlier quoted context omitted.

it's always fear for me. I'd rather leave it commented out for a decade or so to be safe.

I never understood commenting out code when you have version control. I get why people do it, I’ve done it myself and then two days later been confused which of the 3 commented out function was actually the most recent. It’s infinitely more clear from the version control since the history is there for you to zoom through.

I think a lot of devs prefer the hover-to-blame feature in their IDE vs searching through history on GitHub.
Post reply on HN