Many startups never even make it out of the front-door and stay in the idea phase, those that make it out of the idea phase are often crippled by people who are not fit to be co-founders or greedy / shady people, some of them that try to get VC often doesn't get any capital simply because the amount they need to build it is too much compared to the potential profit they can make and further-more, time - if it takes you two years to build something, by the time you're done, that market has already moved on.

So what I'm trying to solve is eliminating the need for VC for the tech platform, so I'm obviously taking all that risk on me, cut the time it takes to build a tech-startup from several years to 3-6 months so it can enter the market faster so that the platform has time to evolve with the market instead of chasing the market and then finally, if the platform is in place and the platform gets customers, it's easy to get VC since the biggest expense, technology, is already taken care of, it already has cashflow, the company is already worth a sizeable amount due to the technology already being in place, so the only VC needed, if any (better to keep a company private if possible) is for marketing, sales people etc.

Your idea sounds interesting, drop me a message sometime, can maybe integrate your platform somehow. Not a fan of Ruby on Rails btw, it struggles to scale which means it's expensive to run which is not great if you're a startup with limited funding.

Awesome! I recently worked on a school project where my team worked on something similar. We started developing an API abstraction layer on top of various cloud providers (currently AWS and Google Cloud). It was focussed on solving vendor lock-in in terms of using cloud APIs for app development. So, instead of using AWS or Google's APIs, a developer would use our API service that could be easily migrated between the cloud providers with a simple configuration.

Not sure if this is the best way to solve cloud vendor lock-in for developers, but that's how I got to learn about AWS, Google Cloud, and many architectural points. Due to time constraints of school project, we could not cover all services of AWS and Google Cloud, however we designed the entire structure modular so we could easily add new service layer or an entirely new cloud provider.

Glad to meet you here. :)

I'm an AWS n00b, but heavily invested in Google's cloud - my recent focus has become making software that's cloud/server-agnostic; so in other words, I don't want any kind of lock-in if I deploy on Google or AWS and migrating should be simple.

I have one app which is using almost every Google API you can think of running on Google App Engine, if I want to migrate this app to another cloud provider, I'll need to rewrite the app and if Google decides to shut down any of the APIs I'm using, I'm toast. Same applies to AWS.

So even though those APIs are convenient, I avoid them as far as possible unless I build a generic interface on top of those APIs that I can easily swing to another cloud provider if I need to.

I've given up on Coursera for now, I never get time to do the courses properly and there are so many courses I'd like to do. Looking forward to the day that I can directly download the courses to my brain :-)

It'd be nice if you can organise movie night events on this platform, we currently use Whatsapp to coordinate this between 30 people - pick some movies, vote on it, vote on a place to go watch it and where to get some food beforehand. IMDB is not really that social and Whatsapp gets very noisy to try and organise such events.

Get some sleep, at your age I was running on 0 - 2h sleep a day for many months at a time, with maybe a weekend of normal sleeping in between before doing it again for many more months and following this lifestyle for almost 5 years.

During those 5 years I eventually shifted into an extreme form of Polyphasic/Uberman sleep in order to make it through each day.

Keep up the no-sleep thing for too many years and it will affect your ability to write complicated code as your mind will permanently be clouded until you start catching up on that missed sleep and as you get older you might develop medical complications as a result of not sleeping enough.

As an example, I tried to work for 7 days straight and not sleep at all, by the time I got to day 7, it felt like I was on some sort of hallucinogenic drug that caused me to jump between fever and being cold, seeing things, hearing voices, talking to people that's not there, severe sugar cravings, completely messing up my sense of time with random blackouts of which I couldn't remember anything, but still wrote code during those times I was blacked out. etc. My friend who did the same project finished it in 5 days while sleeping 8-10 hours a day whereas I battled through 7 days of misery and just barely finished the project.

So tldr; get some sleep, you'll write better code if you do.

Okay, thanks I will take a look at it. ;)

@Björn a project must make fun and it is unimportant what it is. When a dating side makes fun than make it :)

I listened to a talk yesterday where a guy from Bosch was talking about their strategy for the IoT. I'm yet to do it myself but check out their site - it may give you some ideas / inspiration.

Wow, now i feeld bad , i want to set up a page for singles and you are controlling a house... :P

There's quite a lot of issue tracking systems built in PHP, maybe not building it in PHP could be a bigger selling point for others to get involved with?

Wikipedia has a list of big-name issue trackers and what functionality they offer: en.wikipedia.org/wiki/Comparisonofissue-tracking_systems

Bootstrap is fine, many designers know bootstrap and would be able to pick up where you left off.

Definitely post here when you have an alpha version available for testing!

I hope you will link it on Devmag.io when you have something to show, sounds really interesting!