11–20 of 48 posts
Meteor. It's a fun, fast and modern web framework that uses javascript on both the server and client so it's easy to pick up if you already have web skills.
Earlier quoted context omitted.
> Increasingly I am using more free/paid SAAS for services like file uploads, emails, storage, monitoring, etc. Yes! I forgot to mention this in my answer. For prototyping, Parse is great. I recently built something in an hour that would've taken me a day in the past. When I get past the prototype, RDS, S3, and Dploy.io are also huge time-savers.
I surely will check out dploy.io, I was uploading static sites to AWS S3 through the AWS Console :(
I worked at 2 start-ups so here are the technology stacks: The first company was started 3 years ago and our technology included: (1) Python-Flask (2) Postgresql (3) SQL Alchemy (4) JQuery for web (5) Objective C for IOS (6) Bootstrap In my second company we wanted to take advantage of the growing ecosystem around Node. We also did not want to have to manage a DB, migrations, and server scripts. Our rationale is that…
When choosing a technology stack I look to Southwest Airlines for inspiration. I might sound strange but more people should embrace the Southwest model. As an airline, they only have 1 type of plane and tries to keep things as simple as possible. So instead of building some of your products in Ruby, other parts in Python, and another part in Erlang; it is better to just stick with one or two core technology. The rationale behind this is to reduce context switching, reduce errors and bugs that occurs at the crack of technology systems, make it easy to train and onboard other people to your project, and make it easier for yourself to maintain it over the long run. My rule of thumb is that software is maintained and read more often than it is written so now I tend to take much longer to write software because I have to think about how people would read it. For every 2 days of coding, I spend about 1 day of refractoring and I do this religiously to keep the technical debt low.
I worked at 2 start-ups so here are the technology stacks: The first company was started 3 years ago and our technology included: (1) Python-Flask (2) Postgresql (3) SQL Alchemy (4) JQuery for web (5) Objective C for IOS (6) Bootstrap In my second company we wanted to take advantage of the growing ecosystem around Node. We also did not want to have to manage a DB, migrations, and server scripts. Our rationale is that…
In my opinion, web technology has become so advanced that the technology for the most part should not matter as much. Unless you are doing something on the scale of Facebook or Google, your technology usually does not matter. Just choose the stack that you are most productive with. And some are more productive than others. When choosing a technology stack I look to Southwest Airlines for inspiration. I might sound st…
I worked at 2 start-ups so here are the technology stacks: The first company was started 3 years ago and our technology included: (1) Python-Flask (2) Postgresql (3) SQL Alchemy (4) JQuery for web (5) Objective C for IOS (6) Bootstrap In my second company we wanted to take advantage of the growing ecosystem around Node. We also did not want to have to manage a DB, migrations, and server scripts. Our rationale is that…
In my opinion, web technology has become so advanced that the technology for the most part should not matter as much. Unless you are doing something on the scale of Facebook or Google, your technology usually does not matter. Just choose the stack that you are most productive with. And some are more productive than others. When choosing a technology stack I look to Southwest Airlines for inspiration. I might sound st…
- Server: Node & express
- DB: Mongo (using mongoose)
- Frontend: Knockout.js using components (introduced in 3.2), Cordova when developing mobile.
- Hosting (db, services): Azure
Pretty standard with the exception of Knockout.js, which I think is criminally underrated following the introduction of components in 3.2, especially given all the recent hype around component/module based separation of concerns. Also Azure, mostly because I get $150 free monthly from MSDN.
( During my day job ) Front-End: AngularJS BackEnd: ROR Database: Postgress
( For my side projects ) Android Development ROR Redis/Postgress/freebase and lots of reading about Material Design
My current stack: - Server: Node & express - DB: Mongo (using mongoose) - Frontend: Knockout.js using components (introduced in 3.2), Cordova when developing mobile. - Hosting (db, services): Azure Pretty standard with the exception of Knockout.js, which I think is criminally underrated following the introduction of components in 3.2, especially given all the recent hype around component/module based separation of co…