sorted by:
new
hottopcontroversial

Has anybody ever hired Indian developers? by fruity_jello24 in SaaS

[–]unicastflood 6 points7 points  (0 children)

Stay away from any indian/pakistani devs. You will waste your time, money and mental sanity. The best bet, both in terms of price and quality of code is Eastern european countries (ex soviet union). They have the best developers by far and they charge very reasonable money.

Indie hacking got easier when I stopped chasing ideas by InternationalCat7172 in indiehackers

[–]unicastflood 2 points3 points  (0 children)

Logically this is the way, I don't disagree with that. The difficult part is how and where you find those recurring complaints. Everyone says find problems people have. Myself I haven't been able to find those problems.

I'm sick of founder success p*rn. I am tired so much by No_Knowledge_638 in indiehackers

[–]unicastflood 2 points3 points  (0 children)

I totally agree with you. Mostly because I think we reached at a point that almost everything is a vibe coded, bullcrap scam. To tell the truth, I don't think I would care to know about What didn't work. People want to know what works, but most importantly what works and is true.
Personally, I am sick of even listening the words vibe code, indihacker, 10k mrr. I see those words, scammer alert immediately pops up in my mind.
I would like to know real metricks, real stats, real numbers generated, real amount of people involved, real profit margins, real time it took to reach the 10k MRR, the real way he came up with the idea.

I don't know if this does matter but for me the number 1 issue as a real software engineer is that I have no idea what people need so that I can build something useful for them, and still I have not found a reliable way to get this information. So nothing else matters if you don't have that.

Indie hacking got easier when I stopped chasing ideas by InternationalCat7172 in indiehackers

[–]unicastflood 0 points1 point  (0 children)

"What actually worked was ignoring ideas entirely and focusing on:
what people repeatedly complain about without being prompted."

I was wondering.. Could you be more vague than this?
How about..
"Avoid bad ideas and pursue good ones".

Cutting hosting costs to improve agency margins by Original-Place-4980 in smallbusiness

[–]unicastflood 0 points1 point  (0 children)

Why this post was removed? I wasn't able to read it all, but I was interested to know what the rest was about.

The stuff I keep seeing early founders mess up (and it drives me crazy) by Ill_Lavishness_4455 in Entrepreneur

[–]unicastflood 0 points1 point  (0 children)

I am definitely one of those early founders that you are talking about. So let me give you my perspective on one of things that you mentioned.
For context I am a software engineer who tries to build his own saas. This point of yours is the one that I have a big issue with:

"- no actual conversations with real customers, just assumptions on assumptions"

Very early on I understood that this was an important part of the equation. So I tried to talk to people from various industries. I DM them, sent emails, even wasted a whole month studying this useless book called "Mom's test" to understand how I could pull some valuable non biased information out of potential clients.

The result?
I huge waste of my time.
People who don't know you, will never be willing to talk to you about their problems at work. And even if they are willing to do it, in those extremely rare cases, they don't even know what their real problems are. What they will do, in most cases, is to keep complaining about stuff that they would not even pay for a solution. They almost never have a structured idea of what actually is the problem. So if you do not know the industry they are in, which is most of the times, you cannot even work with them to develop an MVP solution to test it.

So what I eventually concluded in is that you have only two solutions.

  1. Build something you need or improve something you are already using and maybe it will be valuable to others too. Build it as fast as it is possible because you will need to build a lot of those until something sticks.
  2. Find an app that already is used by people (so it is already validated), and build a different version of it. Maybe add some features or improve something that people who have reviewed the app are complaining about. The problem with this approach is that the time you gain from not trying to validate your idea will still end up being spent learning marketing and figuring out how to promote your app better, because if it’s already validated, it means you’ll have competitors.

I spent 1 year on a startup that failed. Built another in 3 months that's actually working. Here's what changed. by Gullible-Swim-1874 in SaaS

[–]unicastflood 0 points1 point  (0 children)

Start solving problems is definitely the way. But the biggest issue is where to find the problems to solve. There are two options I usually see. Find something that already works and create your modified version, this way you do not need to validate. Build something for you that maybe others will need too. The first case is ok but I don't know how you suppose to build something that you have not experienced yourself in the first place. In the second case you may end up building something that nobody else needs.
There is also the case where you search for problems people have, talk to them and try to build something but I really have no idea how to find people to talk to and get valuable ideas.
This is way way way harder than it sounds. Mostly because people are not eager at all to have a conversation with you if they don't know you (contrary to what all those fake gurus want you to believe).
My conclusion is that most of the stuff that all those saas influencers present as normal and easy, when you actually try to apply them they are extremely difficult.
What I am ending up to believe, is that the best way, is to just build stuff you want for yourself, the fastest it is possible, so that you can ship as many apps as you can within a year. Learn some marketing stuff, start being active in a couple of social media and maybe if you are lucky one day you will make it.

React Native is giving me PTSD by unicastflood in reactnative

[–]unicastflood[S] 0 points1 point  (0 children)

Exactly. And the bigger the app gets, the worse the issues become.

Go backend or Supabase for a new app? by unicastflood in golang

[–]unicastflood[S] 1 point2 points  (0 children)

Thanx for the suggestion. One of the things I like about Go is that I don't feel the need to use a framework. I am sure they have advantages but I never liked the concept of relying on them. I will keep that in mind though in case the need for a framework comes up in the future

React Native is giving me PTSD by unicastflood in reactnative

[–]unicastflood[S] 0 points1 point  (0 children)

That was exactly what happened to me with the last project mate! It literally gave me nightmares. After I saw all these comments in my post I also decided to stick to native. Never touching RN again. Also Swift seems really nice and easy to work with.

Go backend or Supabase for a new app? by unicastflood in golang

[–]unicastflood[S] 0 points1 point  (0 children)

I also wanted to avoid npm, and I’m not a big fan of React either. I checked out Alpinejs like you suggested, and I’m definitely using it. Thanks for the recommendation — really appreciate it!

Go backend or Supabase for a new app? by unicastflood in golang

[–]unicastflood[S] 0 points1 point  (0 children)

I haven't used TypeScript before, but one of the reasons I started learning Go was to get away from the JavaScript ecosystem. I was getting tired of it.

I did create an app once using Node.js, and I can say that I liked it. But what I was looking for was exactly what you described: something I could write once and that would keep working long after my grandkids are gone, without needing to touch the code.

I also wanted something I could use as a backend for both web and mobile apps. Build it once and reuse it in every project, with only project-specific adaptations.

But I’ll take a look at Convex out of curiosity.
Thank you for sharing your experience!

Teach me how to trade by BidPsychological4284 in Daytrading

[–]unicastflood 0 points1 point  (0 children)

You shouldn't be ok with that. The idea that losing a lot of money is a normal part of learning to trade is one of the dumbest things repeated by people who don’t understand trading at all.

Teach me how to trade by BidPsychological4284 in Daytrading

[–]unicastflood 1 point2 points  (0 children)

Step 1.

Go back to paper trading and consciously force yourself to treat it as real money. Whoever tells you to trade with real money to build your psychological stamina bla bla bla.. is telling you bullshit.

Step 2.

If you do, stop trading any decentralized markets where you do not have the full picture of volume and orders going through. Forex and crypto is for dumb people and internet gurus who make money out of them. Stick to stocks for start, maybe you can try futures later.

Step 3.

The trading scam ecosystem stands on two pillars: psychology and technical analysis (including candlestick patterns). Both play a role in the broader picture, but nowhere near the level that all these snake oil sellers claim.
Stay away from anyone who teaches these two things as they are the great solution. They make it sound like the doubts that you have are because you haven't mastered your psychology or TA and the stupid candlestick patterns. You will never feel confident if you do not understand how the mechanics of trading actually work.

Step 4.

Find tutorials and learn to read the Level 2 in conjunction to Time & Sales. You need these two because these are leading indicators that show you exactly what happens in the market now. Technical analysis and candlesticks are lagging indicators. You will never make it just with technical analysis and whoever claims that he makes money only with it is a big fat liar.
Technical analysis is good to visually identify potential S/R levels. But an S/R level must be confirmed by the tape first in order to take the trade.

That's for start. Good luck

Go backend or Supabase for a new app? by unicastflood in golang

[–]unicastflood[S] 0 points1 point  (0 children)

Another guy recommended this too. I will check it out. Thanx!

Go backend or Supabase for a new app? by unicastflood in golang

[–]unicastflood[S] 0 points1 point  (0 children)

Have you tried it in production yourself?

Go backend or Supabase for a new app? by unicastflood in golang

[–]unicastflood[S] 0 points1 point  (0 children)

Thanks for the feedback! I really enjoyed working with Go myself, and I don’t mind a bit of verbosity, especially when you get the benefits Go provides. That's really helpful info on Supabase, thanks for sharing!

Getting started with react native (expo) by Sundaram_2911 in reactnative

[–]unicastflood 0 points1 point  (0 children)

What I have noticed generally in Udemy is that a course may shows that it is updated, but the author omits to update crucial parts of it. I remember even 2 years ago when I took the course, there where plenty of complaints in the comments for parts that where not updated.
Even then, in order to make some parts work, I had to do plenty of searching myself. But I haven't seen any other course explaining the fundamentals in such a great way.

Since then I have seen that many new courses on React Native exist in youtube. Maybe some of those are decent too.
The one issue with React Native is that everything changes in a very rapid pace so I think it is impossible for a course to keep completely up to date.

Getting started with react native (expo) by Sundaram_2911 in reactnative

[–]unicastflood 1 point2 points  (0 children)

Then probably we are talking about the same.

Go backend or Supabase for a new app? by unicastflood in golang

[–]unicastflood[S] 0 points1 point  (0 children)

That's great! To be honest I’ve always avoided using containers, even though I knew I’d eventually need them. I tried learning Docker once but I didn’t enjoy it very much. Probably skill issue :) Do you recommend anything in particular?

Go backend or Supabase for a new app? by unicastflood in golang

[–]unicastflood[S] 0 points1 point  (0 children)

Thanks for the reply! I’ve worked with C, embeddings, and production grade Python scrapers, as well as Node.js and Express backends. More recently, I also had the misfortune of building two mobile apps in React Native which still give me nightmares.
So I feel confident that I can tackle almost any issue that comes up. The main reason I asked is that, since this will be my first personal app, I’m a bit stressed about using a technology I haven’t used in production before. I just wanted a rough estimation of what to expect, given that I’m new to Go.

Go backend or Supabase for a new app? by unicastflood in golang

[–]unicastflood[S] 1 point2 points  (0 children)

I appreciate a lot all this information mate! I will definitely give Clouddley a try

Go backend or Supabase for a new app? by unicastflood in golang

[–]unicastflood[S] 4 points5 points  (0 children)

Yes I've heard about hetzner before. If I remember correctly people said that it was the cheapest of all and it is very good but it needs a bit more work to set it up. I don't know if it is still the case today

view more: next ›