What is your current stack?
1–10 of 48 posts
Re: What is your current stack?
#2I'm getting into Go now, but I'm hopeful Rust will become the language of the future. I'm desperate for a great type system in a web framework. Elixir is cool, but I don't think I could find anyone to work on it for me.
Re: What is your current stack?
#3Re: What is your current stack?
#4Increasingly I am using more free/paid SAAS for services like file uploads, emails, storage, monitoring, etc. Not sure if we can call this approach a "stack" but surely it is becoming very relevant and it solves most requests I get. I guess it is also interesting to rapidly hack an MVP with such tools and if the thing picks up (traffic/user base) you can scale the services (pay more) or start programming them yourself, if the think flunks time/money was not wasted. It is also a big plus that these services play super nice with mobile native and mobile web, SDKs are always available. Maybe I am a wishful thinking hipster but somehow I feel this is the trend to follow.
Re: What is your current stack?
#5Frameworks: Rails / AngularJS / Cordova
DB: Postgres / Redis / Elasticsearch / Memcached / DynamoDB
Messaging: SQS
Plan on learning in the next few months:
More Clojure
Machine Learning
ReactJS (Hopefully a replacement for AngularJS / Cordova from above)
I've been picking things to learn based on reading programming books and observing trends. 7 concurrency models in 7 weeks, 7 languages in 7 weeks, and 7 databases in 7 weeks are all good places to start for finding something new to learn. As you can tell, I'm a big fan of the series as an introduction to a topic that can then be explored in more depth after reading.
Re: What is your current stack?
#6If I do my own REST back-end: node/express or good old php. If I go no-backend: parse.com or firebase.com (different use cases). Front-end: BackboneJS and the usual mix (CSS, HTML5, Bootstrap, Jquery, etc) and I am looking into adding ReactJS to the stack. Increasingly I am using more free/paid SAAS for services like file uploads, emails, storage, monitoring, etc. Not sure if we can call this approach a "stack" but s…
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.
Re: What is your current stack?
#7Re: What is your current stack?
#8If I do my own REST back-end: node/express or good old php. If I go no-backend: parse.com or firebase.com (different use cases). Front-end: BackboneJS and the usual mix (CSS, HTML5, Bootstrap, Jquery, etc) and I am looking into adding ReactJS to the stack. Increasingly I am using more free/paid SAAS for services like file uploads, emails, storage, monitoring, etc. Not sure if we can call this approach a "stack" but s…
> 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.
Re: What is your current stack?
#9The 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 we should focus more on the customer and turning the customer requirements into the product than on the technology working. We are an enterprise software company and so the less complicated the technology the better since we are not doing anything ground breaking from a technology standpoint. Our stack includes: (1) NodeJS/Express (2) Heroku (3) Angular JS (I don't get all the negative comments about Angular lately because it works fine for us) (4) Lodash (Javascript utilities) (5) S3 - static file storage (images and files) (6) Jquery (7) Bootstrap (8) Firebase (9) Angular Fire (to connect firebase with angular)
Using our current backend, we were able to build the SAAS product in about 1 month with only myself as a developer instead of 2-4 months that might be required if we had used the previous technology stack. Firebase, Angular, and the Node ecosystem really helped make the coding much faster than before.