64 karma · joined November 20, 2013
What kind of query would you have to write to bring down a production db? What makes a solution like hive much better - I guess its optimized for this?
A lot of the advice around finding a co-founder is focused around college/childhood friends. And I think that's why most brush off online forms of finding partners to work with as inferior :shrug: - I think this is a mistake.
Quit viewing it as finding a co-founder and just view it as finding people to build and ship cool stuff with. It takes some of the pressure off the interaction and gives you all a chance to just practice working together.
Also if you want to collaborate on something find my email on my profile and here is my github https://github.com/roymoran. There just did it. If it works out cool, if not cool.
People that just want to collaborate and build stuff will do so. I don't think you need much convincing.
You stated it yourself, plan first. Define exactly what you are shipping. If you don't do this - it's going to feel like the development is never going to end because it never really will end unless you have a well defined stopping point or a set of features that you just won't ship without.
A lot can be said on how you plan - this can vary widely based on the type of project you are working on. You mentioned building a simple web application so here's my advice for that - be very clear with the objective of your project then use a method like moscow to prioritize feature ideas. Our minds run wild during brainstorming but lets reel it in to factor in our time constraint. So throw out everything non-essential - and when I mean non-essential it should make you feel uncomfortable with the amount of stuff you throw out.
TODOs are a good step - my only practical recommendation here is to go up a level of granularity. Define user stories/scenarios and/or features (I go without defining features and just leave it at user stories since this is enough for me) and tie your TODOs to these stories. Don't underestimate this work. This will help you make that context switch between development and the bigger picture of your project and who your users are.
I use GitHub and use their board to to tie in my issues with pull requests. If you use github do that - keep your TODOs close to your code maybe even track it in source control. Up to you.
> between just shipping a product and following the best engineering practices and actually defining what I really want to do....
Here are thoughts for your concerns. boiled down to a few words.
> shipping product
Plan.
> following the best engineering practices
Forget the deadline.
> actually defining what I really want to do
Stop and ponder.
If you want to try to make it work - try being the first person to say at your next standup "Hey I said I would get this done but I got blocked by this thing. Anyone have reference/documentation they can share so I can get unblocked?"
We're not all perfect so I know there's a part of the project that makes your head scratch or is blocking you. Come up with something to get the ball rolling. In the context of a standup its important everyone feels like they're in a safe environment. Anyways, just model the behavior and see what you get.
I know, I know - now you're the one in a vulnerable state. But that's why you're a leader. You do the things others are afraid to for the betterment of your team and the quality of your product.
https://github.com/search?l=C%2B%2B&q=c%2B%2B+embedded&type=...
I realize saying "metrics" is a bit broad but I imagine early stage startups track some of these like user-growth, revenue growth, subscription growth to get an idea of how their startup is performing or to help goal-set. Or is this an area where most hack together a spreadsheet that unifies data from external data sources?
Reach me on LinkedIn - https://www.linkedin.com/in/roy-moran-a8b42b9b/
op, take a couple months to build your product (considering this is a CRUD-like app) and then face the distribution problem.
Thanks for sharing this. This is something that has been extremely important for me to realize. When it comes to holding strong and passionate view points on any topic. I have to stop and understand that there is a reason that the person with an opposing view point may also be right from the perspective of their world view and I’m simply blind to it because I may never fully be able to understand their world view and they may never understand mine.
We all go through anywhere from slightly to drastically different life experiences that inform our world view. And it’s something I force myself to be more conscious about. But thank you for bringing this up in your context and experience.
Joe Gebbia put it nicely by making an analogy to the “gym of entrepreneurship.” Building a startup is one of those things that you need to work to get better at over time. Not many founders have many regrets but when they do express regrets it’s usually them wishing they had started earlier. Here’s Joes quote from his interview with Tim Ferris.
“People think we woke up and Airbnb was just created out of thin air. That couldn’t be further from the truth. I hope if there’s any takeaway from the stories that we’ve talked about today, it’s that there’s a long lineage of trying things, bumping into walls, getting rejected, failing, reframing that failure into learning, and trying to continue forward.
And so, by the time Airbnb came around, it was like I’d been in the gym of entrepreneurship for many years. So, it’s like you don’t wake up and just run a marathon all of a sudden. Nobody does that. You train for it. So, by the time it’s ready for race day, your body is conditioned for it. Your muscles and your system – everything is ready for you to go run 26+ miles.
I think entrepreneurship is the exact same way. I think it’s a misconception when people look at the magazine covers and they read the stories of a successful company and they think, “Wow, the people who started that, they built it and everybody came.” That couldn’t be further from the truth. I think “Field of Dreams” is probably the worst movie to ever happen to entrepreneurship. It created this idea, like, “Oh, wow, if you build it, they will come.” I can tell you, if you build it, they don’t come.
It takes this incredible perseverance and sometimes irrational belief in yourself to bring something to life in the face of lot of adversity and a lot of people saying it can’t happen. So, I hope if there’s any takeaway from the stories that I shared today, it’s that the simple act of spotting an opportunity, coming up with original solution and then taking that third, hardest step of putting something into the world, of trying something, putting your idea into practice – it doesn’t have to be the big idea.
It’s just about being in the gym and doing a rep, the gym of entrepreneurship, doing curls or something. It’s just getting in the habit of those three things. You spot an opportunity, you come up with an original solution, and you put your idea into the world. And the more you can do that, the better you are at spotting the next opportunity. Airbnb just happened to be a part of the lineage of all the things I’ve told you that happened before it.”
The auto industry with the self driving car will change and create new businesses. There’s a huge opportunity to get involved or create a startup in this space. It’s the next big wave of opportunity and there’s plenty of room.
Thanks for your thought. It reminded me a little bit about an interview with peter thiel where he responded to a question about the future. I guess popular culture in tech moves past ideas rather quickly and generally seems to jump from trend to trend until realizing the value of a trend.
Unfortunately, businesses tend to heavily influence the creation of the laws that give them an unfair advantage. Businesses get started, they get big, and then use their money to buy lobbying power. I wouldn’t be surprised if this was true in the taxi industry.
I don’t care for laws which exist to favor industry leaders.
If car manufacturers tried to clone what Uber has built they'll probably flop on making the technology usable, and the experience may just be overall frustrating.