React has always used functional programming patterns. They used classes to define components, but even those applied functional principles.
1,689 karma · joined March 3, 2021
It shouldn't be about the time spend but how quickly you can validate assumptions, those are different things.
My point is: It's not "that easy". I'm pro indie hacking, but it's hard work and difficult to create a profitable business that you can live off. Spinning off crappy quick projects only works if you have a big audience you can sell to, and most don't have that, so they will have to put in a lot more effort and time.
They usually build a landing page or bad prototype, wait for people to come, then move on to "the next startup" if it inevitably doesn't work. Their ideas usually don't have enough potential to sell, and if they do they don't take them far enough to actually realize even a fraction of the potential.
I love bootstrapped companies, I'm all for building side projects and turning them into jobs, but this movement has moved away from that and is now about selling the dream instead of the work.
It sounds like the person you know did not do this and actually created something valuable, that's amazing and I congratulate them. I would like the indie hacker movement to move back to celebrating these success stories instead of the influencer BS.
Edit: and maybe I am a bit bitter as I loved the indie hacker movement. I found it to be incredibly inspiring, and I truly miss the stories of people doing lots of hard work, solving difficult problems, and building incredible products and companies.
It works for the influencers because their audience is big enough, but for everyone else it’s very unlikely to work and they will just pay for the courses and boilerplates the influencers are shilling.
Most things that create significant sustained value will take a lot of time.
It’s sad to read the blog posts of people spending so much time building crappy products no one will ever use, and still trying to sell you on their latest idea.
It’s sad that this is what indie hacking has become.
I thought the article did a good job of explaining this issue, the intro with the cover is a nice analogy
Once you take VC money, like Figma did, your goal is a lucrative exit.
It's high risk, high reward. It's a different way to build a company, and it's not really possible to change that once you take that route.
Doesn't mean you have to do this. I am all for building steady profitable private companies that aim for the long run, I think it's a great way to build great companies, but then you should stay far away from VC money, take a lot less risk, have different compensation strategies etc etc.
A "proper" startup does indeed include an exit as that's the point where they give a return on investment to their VC's. That is the startup game, use the VC money to accelerate growth, then exit/go public.
Not saying I like it, but once you take the VC money that is the game you play.
Indeed, Adobe's actions will be interesting. They will have to compete, maybe they can buy Sketch or similar?
And they might also just want out of the $20B price tag as you are right that it's a crazy price today.
I do think its the right outcome and better for customers, the government is doing what it needs to do.
But I still empathize with the people involved.
It's about the expectation of everyone involved.
Eventually every company needs to turn a profit, so for the company it might not make that big of a difference or even be better (if they can turn a profit which I assume Figma can), but for the investors and individuals involved it's a very different situation as it means their capital is pretty much stuck. And I bet a $20B exit would be life changing money for a lot of people involved.
If Adobe can't buy them, what other exit options do they have? Go public?
Also Linear has been defining in terms of their website design, they have been doing a lot of impactful work.
Imo it's also good to realize in this kind of software, patterns and UI are very core to the product, so you are copying the essence of what this company has spend tons of time and resources to develop. Fintech might be different as it's less about UI.
Then there is also a difference between UI patterns and branding. The first: It's good to follow standards and expectations, the second should just not be copied imo.
Another factor is asking money for it, which it looks like they intent to do. I think that makes it even weirder to clone an existing product as now you try to compete and profit from other peoples work.
There is a fine but clear line between inspiration and copying, and imo this crosses the line.
Even if legal I would not use this product for that reason, and imo it reflects poorly on the people doing it.
Generally more practical than W3C.
(small note, in the readme it says `cp .env.sample .env`, looks like it should be `cp .env.example .env`)
2. Work on your network, talk to recruiters, peers in the industry, you can even do some interviews to practice. Not only might it help you if you need a new job, it gives you a taste of the actual situation, it might be better than expected or you know better what to prepare for and what you can work on.
3. Be open to freelance work and shorter projects.
4. Work on your skills, tune them to where the jobs are, build projects. Widen your skills with new topics/languages/frameworks/areas and get deeper expertise in your main area. Get your confidence back.
5. Start a company, but that is a lot more risky, and comes with a bunch of anxiety on it's own. It is also a lot of fun, I am enjoying it.
I think you need to do a good objective evaluation of your situation. Anxiety often comes from uncertainty, you might find it's not as bad as you fear it is, or you learn what you need to do. It sounds like you have a job, have experience, so you might be fine while just continuing to do what you do.
Also a bit confused as it seems there is nothing there besides an idea and a landing page.
Can't say prettier performance ever bothered me, but if it can run faster and leaner I'm all for it! Increase my battery life :D
In general it's really exciting to see the advancements in JS tooling, the quick successions of tooling in JS might be controversial, but I love it. Each step was a significant improvement over what was there before, and the current Rust rewrite wave has already given us great tools that I use daily.
I also like that there is some money being thrown at the problems!
In the most literal sense it's the minimum viable product, the minimum product that is viable [to sell/to test/to get feedback]. Which is still very much alive.
Most importantly your MVP should focus on the core functionality, this is often where you save most time. Products usually can branch out into many directions adding a bunch of cool, useful, but not essential features. For your MVP you should focus on the minimum functionality needed to make it valuable. Less features also means less work making them look good.
The same applies to design. The standards are higher today, so a bootstrap app might not be sufficient anymore, but you might not need an amazing experience with for example amazing graphics, animations, and delightful micro interactions to sell your product.
It very much depends on your situation and audience what your MVP might look like. For example if you target enterprise customers in an old industry the standards are much lower than consumer apps, and that bootstrap app might still work.
The challenge is determining what is and isn't essential, which is not easy. People often don't know, and that is exactly why it's good to get your product out and test it as quickly as you can so you can adapt to reality.
What an absolute savage takedown. The frustration drips from the page. Anyone aware of some good Github issues to read the source of this frustration?
Shots fired!
2. Three options: use the supabase admin panel, build something yourself (or use templates), or use a 3rd party tool - many low code tools can connect to postgres and there are also some specific integrations with supabase.
3. Supabase has auth built in, with RLS you can control data access.
4. Next.js is just React when it's in the browser, so yes, it will work well. If you use the Supabase realtime with their client library it will handle all the socket connection for you.
5. Have a look at https://www.madewithsupabase.com/tag/Open%20Source it's not all next.js but there are quite a few.
The portfolio looks great, congrats! I hope she will find a job soon, and good for you for building & promoting it ;D
People can present themselves differently than they are, and especially people with lower morales will have no problem presenting themselves differently if that is in their interest. Look at pretty much any big company CEO.
If you do need to gauge someone, look at their history, look at their actions, and look at their incentives. If they don't align with what they're saying you should not expect them to act any different than they did before.
I still find it important that the option exists if ever needed, and maybe even more important is the ability to move away from Supabase, which some people have done successfully (see for example https://news.ycombinator.com/item?id=36004925)
Other services like Firebase make that really complicated. I quite like that portability is one of their core principles.
There are some guides and templates on self hosting https://supabase.com/docs/guides/self-hosting but it's obviously a big complicated project with lots of features. It probably also requires a bunch of work to monitor, maintain and update it once you get it running.
Reliability, it depends on your app and requirements. Been using them for about a year and it has been really solid, the few times I did have some issues the support was really quick and helpful. But I do see your point, it might not work for everyone.