5 ms·
100% with you. It's so hard to find real problems if you spend 90% of your time finding problems. Having a job is a great fix. Building side projects with no
by marclou 3y ago
100% with you.
It's so hard to find real problems if you spend 90% of your time finding problems.
Having a job is a great fix.
Building side projects with no purpose works too.
For instance, you can sell a boilerplate to make it faster, or get feedback from users and build for them.
Although it's much harder to start, and hard to navigate life without $ for months (years in my case)
- TheLastSultan 3y agoThe way I see it for you Marc, you spent 6 years building an audience on Twitter. Shipfa.st has a very short shelf life. The audience and trust of startup founders/lovers in the ecosystem has lasting value. Any ideas on how to capitalize on that?
- marclou 3y agoGood point. Either I'll build an audience on YouTube And/Or I'll build new startups Also, my Twitter is really small so there's much more work to do there. Any thoughts? Note: I've been building an audience there for 2 years (the first 4 years was me building in the dark)
- TheLastSultan 3y agoI think if you can focus on making informative content for YT at the same quality as your commercials it will be a smashing success. The key is focus. You have an eccentric charm that devs like myself enjoy. Your Twitter following will help you get from 0 to 1 there, but you should still be prepared for a steep curve before it generates revenue. I do have a radical idea that I am keen to share with you in particular. I am the Founder of RocketDevs.com. The 'amazing' thing about us is that we can ethically and reliably source GREAT developers and rent them out for $6/hr or $980/mo. This entry point is cheap for USD earners, but stil a fortune in some regions. The market opportunity here is early startups. People have ideas, but they can't spend $7k/mo on Turing. Fivver is shit. Upwork is avg $28/hr for mid-devs. With no affordable help, non-technical founders will scramble to find a 'technical' founder. You taught yourself how to code but few are that committed. Technical founders will reliably start a project and burn out quickly due to 0 help. Our audiences intersect strongly. My radical idea is that we work together. I use my deep technical experience to source great devs. You use your following so I can conveniently focus on the product and avoid the pain of 'building an audience' just to get the word out. Stable income for you and we're helping folks build their dreams. Look me up at linkedin.com/in/thelastsultan if you're keen. I think im in your inbox already.
- marclou 3y ago[dead]
- iamleppert 3y agoHow do you find developers for $6/hr and what do you mean you rent them out?
- ametrau 3y agoYeah. Which country I would very much like to know. 100% exploitation.
- throwaway_108 3y agoAny startups, in your view, nailing your advice?
- aleph_minus_one 3y ago> It's so hard to find real problems if you spend 90% of your time finding problems. > Having a job is a great fix. My experience differs: it is very easy to find real problems, and it is possible to implement a decent solution for at least some of them. But: many of the problems that various industries have are in my opinion self-inflicted because of their structures. What is hard is convincing potential customers that your solution would help them.
- mattgreenrocks 3y agoOnce it hurts enough, people pull out their wallets. What's that threshold? Well, that's the hard part. :)
- wharvle 3y agoExample: the entire software industry (to include, and perhaps especially, companies that develop software but aren’t exactly software companies) seems to have a problem with splitting tools across a bunch of vendors, many of which have heavily overlapping functionality. It adds friction to everything and makes it harder to see what’s going on, burning god knows how much productivity. But you can’t fix it by making another multifunctional tool, because you’ll just get people using one or two of your five feature-areas, and two or three other tools for the rest, same as now.
- askafriend 3y ago> seems to have a problem with splitting tools across a bunch of vendors Why is this a problem?
- wharvle 3y agoAdds a little overhead and friction to processes. Causes miscommunication and lost and scattered info, and worse visibility and awareness of what’s going on than could be achieved. The result is fairly significant rarely-accounted-for costs. I’ve seen it every place I’ve worked. Of course “well just use all the tools the right way and always look where you’re supposed to and put things in the right place” but it never works out so nicely in practice. [edit] example: paying for a half dozen services that provide, between them, two code repo hosting solutions, four CI solutions, six wiki solutions (LOL), two cloud hosting solutions, two CDNs, three issue trackers, and on and on… and mixing and matching those such that it requires daily manual upkeep to synchronize info between them (you’re not using all the features of each one, to be clear—or, if you’re really in hell, maybe you are), onboarding is messier than it could be, account management is a pain, you’re over-paying at least a bit on everything, “where did/does that go?” is a constant question, everyone needs several pinned tabs opened when they could have, like, two, et c et c. Usually the reasons for doing this aren’t even strong, it’s just how things have ended up.