Earlier quoted context omitted.
>In my experience reducing features is better to begin with. This is right approach. Lean. If you don’t have PMF, reduce your features until you find it. Pivot. Maybe pivot again. Eventually you’ll find a market to serve. Just don’t fall into the sunken cost fallacy. Time box your market exploration.
How do you mark the difference between pivoting and adding new features?
I spent five years building a webapp and got my first $1 (2022)
71–80 of 101 posts
Re: I spent five years building a webapp and got my first $1 (2022)
#72Re: I spent five years building a webapp and got my first $1 (2022)
#73How do you guys get funding to build things for such a long time? Rent, food and health insurance in my area costs $50k per year. If feels I have no choice but to earn a salary. Dropping a quarter of a mil on an app that might not pan out seems out of the question.
You could just not do a Web app. There are plenty of apps you can build that don't require any upfront costs. I'm working on an app that runs entirely on a consumer PC.
Re: I spent five years building a webapp and got my first $1 (2022)
#74Re: I spent five years building a webapp and got my first $1 (2022)
#75> Yes, you guessed it, let's go with Electron and CoffeeScript. > The main tech stack is still CoffeeScript, but we changed the UI framework from React to Riot.js. > I've installed Babel, Mocha, ESLint, and added libraries via npm. > I've rewritten my entire code base from CoffeeScript to ES6. > The introduction of MobX, a state management library, and the introduction of Flow, a type checking system. > So I rewrote…
I am guilty of trying to keep up with the buzz like learning Rust even if I don't need it (get by with JS/Python/C++)
Re: I spent five years building a webapp and got my first $1 (2022)
#762.54:1 contrast for text which spectacularly fails any accessibility specs. Please don’t do this
The new, superior method is https://www.myndex.com/APCA/. It yields an Lc of 50.4, which is (as you’d expect) wildly unsuitable for body text.
Re: I spent five years building a webapp and got my first $1 (2022)
#77> Yes, you guessed it, let's go with Electron and CoffeeScript. > The main tech stack is still CoffeeScript, but we changed the UI framework from React to Riot.js. > I've installed Babel, Mocha, ESLint, and added libraries via npm. > I've rewritten my entire code base from CoffeeScript to ES6. > The introduction of MobX, a state management library, and the introduction of Flow, a type checking system. > So I rewrote…
Re: I spent five years building a webapp and got my first $1 (2022)
#78> Yes, you guessed it, let's go with Electron and CoffeeScript. > The main tech stack is still CoffeeScript, but we changed the UI framework from React to Riot.js. > I've installed Babel, Mocha, ESLint, and added libraries via npm. > I've rewritten my entire code base from CoffeeScript to ES6. > The introduction of MobX, a state management library, and the introduction of Flow, a type checking system. > So I rewrote…
Exactly why I have zero regrets going native on macOS. Yes, Xcode isn't the best to put it mildly and SwiftUI is still maturing.. but I am so glad I don't have to deal with the modern web stack. Daily smiles instead of facepalms, most of the time!
Re: I spent five years building a webapp and got my first $1 (2022)
#79> Yes, you guessed it, let's go with Electron and CoffeeScript. > The main tech stack is still CoffeeScript, but we changed the UI framework from React to Riot.js. > I've installed Babel, Mocha, ESLint, and added libraries via npm. > I've rewritten my entire code base from CoffeeScript to ES6. > The introduction of MobX, a state management library, and the introduction of Flow, a type checking system. > So I rewrote…
Re: I spent five years building a webapp and got my first $1 (2022)
#80Earlier quoted context omitted.
It’s interesting 12 years ago I released v1.0 of the full stack open source platform for anyone to use to quickly put together pretty much anything on the Web in a standard way, and focus on actually growing it, but I have faced opposition from day 1, on weird bases First, I was told that the name of my library “conflicts with the excellent Q.js library for promises” and that no one was going to take a look. Well, pr…
Web devs specifically seem to be especially prone to inheriting biases from more senior devs that they've worked with, to the point that they spout things like "php is terrible and no one should use it" or "jquery is bloated and useless" without actually having used the technology they're rallying against. Or sometimes they'll maybe have messed around with a poorly written legacy application, or they'll go through a…
Where we were in the early 2000s wasn't bad, it was actually pretty slick compared to all the "shiny" we have today.
There will always be problems, but the idea that to solve the problems we should use Yet Another Cool Library/Language is just incorrect. Sometimes its good to refactor/rewrite, but often the rewrite is just as bad (or worse) as the old thing. You should have a very compelling reason to do so (at least for large scale rewrites, removing tech debt is OK).