Thanks frereubu. Sorry, I posted it because the author kadavy wrote the book "design for hackers" and it was big on HN a while ago. I was going to add the "design for hackers author" to the title, but I didn't want to editorialize it.
I thought this community would like it and can relate to it, but I understand if it goes against guidelines.
is this good enough to post or unflag, or is linking directly to Amazon not a good idea. Thank you!
... and just like that everyone all of a sudden hates product hunt on hacker news. I don't understand most of these comments.
Product Hunt is still very new and we're already talking about how the algorithm is no good and bad tweeting practices.
Of course other users are going to ask their friends to upvote their submissions. Of course the founders are going to make sure that quality products are shown near the top. Of course the founders are going to make sure that engagement is higher even if that means notifying users via twitter.
Why can't we just say congratulations!? Why do we have to hate so quickly? Everyone acts like they have been doing this for 10 years and they should have all this stuff fixed by now.
Agreed with parent comment. I'm a big fan of quitting, but make sure you address the issues in your life first. I was also a workaholic and was able to get out of it.
Even when I hated my job I could still sleep at night.
A lot of great advice in this thread. My input is to get involved in organizations that are the most likely to help you find clients.
If you're a digital marketer, get involved in digital marketing meetups. If your clients are most likely lawyers, go to lawyer meetups. When I say get involved, I mean really get involved. Get a position on the board. Immerse yourself in the community where your clients are.
You don't. You can give your input with the known challenges, but you don't tell him to stop doing the idea. People learn by failing and your best friend's idea may never work, but what he learns from that and what spawns from that might work.
I remember specifically when a company pitched their idea that it would never work, and 3 years later the business is doing really well.
The only way you can really tell your best friend to stop, is if you have direct experience in what he is trying to build and have succeeded.
Your friend will learn the hard way and that's the best learning that there is.
Agreed. Ship it for the sake of shipping it and using it as a portfolio piece. I remember one app in particular that I spent a LOT of time on including meetings with others, etc and I never launched it. It still makes me mad and haunts me.
So if you're close to launching the first app, launch it for the sake of launching it and seeing a project all the way through.
To be honest, this is great news for you. All this means is that you are on to something. Think about it. You have another company who has a million dollar investment, and the people behind the money must be OK with the path they are taking in your niche industry.
Yes, it's not right to steal stuff, but I would take this as a compliment. Forget about them, and focus on you. If you're lucky enough, they will copy your features again.
As some others have said. Focus on technology consulting if that's the life you want. You probably won't be a software dev, but you will lead software development teams who are often remote or offshore.
Accenture, Deloitte, IBM, Capgemini, KPMG. Look at those firms, because travel is usually 100% required.
I have worked for Accenture & Deloitte as a consultant and for many years and have implemented software used for internal teams.
It surprisngly works very similar to any other industry company. The software to be used internally comes from the top of the food chain and then pushed on to projects below it.
The goal is standardization across projects, so I think it would be extremely tough to use an "un-tested" or un-authorized tool at a project level without it coming from the top of the chain first.
Especially McKinsey where the process & methodologies are very defined. It would start from the top and then maybe use a "pilot" project for a small engagement.
They are often forward looking for their clients, but not forward looking internally if that makes sense.
Usually there is a "Tools & Methodology" team that is an internal team and that is who you should be selling to. This is the team that defines the tools that are used for projects.
Form a company with a generic consulting name, and brand yourself as yourself. That's what I do now and it works fine for me. When you bill give them your company billing information.
If your freelancing does get bigger than you can just step back to your company name.
I was scared in the last email I sent to over 30 people. Like /u/taternuts said, you have to be a little scared. But yes, you will get over it, but if it's a big push to prod - you will still be scared.