I'm developing a personal finance tool that doesn't sell my data, helps me see my daily spending habits, and tells me where to cut back and lean in. I got the idea after my wife and I spent the last 10+ years budgeting with an excel sheet, financial statements, and a rough financial independent game plan.
The thing is, I don't trust free financial services with my data. And I'd much rather pay for a tool that listens to what I need, don't need, and build it. Because I'm a hacker by trade, I decided to start building.
You can join me by requesting an early invite at inoutover.com. The first 20 signup get the product FREE forever.
I'm always interested to get feedback; feel free to discuss here. I'll be available.
"I just think it could help me learn more, faster and to improve my communications skills."
Use obscurity to your advantage. Your blog is not known (yet), but if you show up every day/week and write something you're learning, eventually you'll become the expert and goto source. This is the way I think about my personal blog.
Spend a few days identifying problems people pay for, particularly easy problems that you can build yourself. The key is that the solution has to be fairly easy to build since you're not comfortable full-stack. Once you've chose a solution that already makes money solving a problem, build the same solution but position it for either a niche market or make a better product than competitors.
I would at minimum leverage bootstrap or semantic ui as your ui. Otherwise, hire someone to do the web interface for you.
Streaming music requires money to pay royalty fees. The more users listen, the more money Spotify owes to record labels, artists, writers, and others who make music possible and accessible.
It's an art (not a science) to deliver a service (for next to free), while making a profit after paying royalties.
Spotify raising a billy debt round doesn't surprise me.
Good stuff - I know this has been in the pipeline for sometime. Excited to see it out in the wild. Congrats to the Zapier team on producing an awesome product - look forward to using multi-step zaps.
Google "Starting a business". You'll notice the first page results don't lead you to YC, Techstars, Hackernews, or anything (loosely) startup related.
You have to know what to search to land on HN or some other popular startup site. My point (and argument) is that most minorities don't know about YCombinator, HackerNews, etc; partially because most live in a non-startup, tech-oriented community. And searching for reasonable keywords like "start a business" isn't a direct invite to the world of startups.
This is why outreach is important. We need to key certain demographics into the startup world via outbound.
Put it this way, there are 50 states in America and the areas with the least amount of blacks/hispanics are where words like "startup" is king (and vice versa). Until then, outreach is vital until certain demographics pick it up at scale.
Heyo - builder here! This was a weekend hack. The main pain I found using Twitter is searching bios. Follower Lead is a simple tool allowing you to match words against twitter user's bios.
I have to counter some of the comments regarding buses and light rail being empty. This is completely untrue. People are using the light rail and buses in large sums. It has its off peaks but certainly before and after working hours is extremely busy. Most people who say their empty are likely the same folks not using public transportation. I had the same consensus before trying out RTD.
Downtown Denver resident here. I have to attest that the light-rail has been a tremendous win for Denver and surrounding area residents. Along with the bus system, Uber, and Car2Go, I started using light rail last December and never looked back. Even though there are hopeful plans to expand commuter rail to Boulder, I still think the FastTrack Program is a good decision. Boulder's been a stiffed by the new development but I can't imagine no commuter rail being implemented sooner than later.
Great post. I recently started a project using reactjs, and I have nothing but good things to say. The unidirectional data flow, the declarative nature, and the virtual DOM makes it powerful and very easy to like.
The best resource is to follow the tutorial (link below). The tutorial explains everything you may have a question about when comparing it to Backbone, Angular, or Ember.
I think part of the lesson learned from reading the post is MongoDB is best when you start sharding from the git-go, especially if you know you're going to have pounds of data.
Craig - great post. I think you missed a few huge benefits that drive the "NoSQL movement." Specifically, sharding and aggregation.
Most devs don't need the power of sharding, which is why that benefit can never be felt. But the reality is this is probably the #1 characteristics (huge benefit) of NoSQL databases. Google and Amazon definitely paved the way for this movement, primarily b/c they dealt with tons of data. Its simply cheaper to scale out (distributed) than scale up.
You can't aggregate data with a relational database. But you can aggregate with (most) NoSQL databases (exception is graph dbs). Instead of building relationships, with NoSQL you're building composites. The huge benefit here is enabling sharding while, having your data all in one place.
Lastly, a relationship db is made up of tuples and sets of tuples. With a NoSQL DB you can have complex data structures. I think this is the point you we're trying to make re: Documents.
I still love relational databases. It's cool to have options though. Before, relational was the only way.
The question is how do we determine which db to use (or use more than one)? Ah, the beauty of polygot persistance...
I'm developing a personal finance tool that doesn't sell my data, helps me see my daily spending habits, and tells me where to cut back and lean in. I got the idea after my wife and I spent the last 10+ years budgeting with an excel sheet, financial statements, and a rough financial independent game plan.
The thing is, I don't trust free financial services with my data. And I'd much rather pay for a tool that listens to what I need, don't need, and build it. Because I'm a hacker by trade, I decided to start building.
You can join me by requesting an early invite at inoutover.com. The first 20 signup get the product FREE forever.
I'm always interested to get feedback; feel free to discuss here. I'll be available.