Hacker News new | past | comments | ask | show | jobs | submit | gokulj's comments login

Congratulations and Good Luck! Curious about your tech stack choices that allowed you to cover iOS, Android and Web, with a team of one!


Thank you! Haha I'm not entirely sure I recommend my approach. Obejctive C + IGListKit + regular old UIKit on iOS, React through next.js (for SEO) and native css on web, and Kotlin on Android. As to why: I've gotten a bit brash from my college hackathon years, as well as worked on a similar stack during my time as a full-stack eng at Pinterest. From sheer muscle memory and ___domain knowledge, building out Queenly on these three platforms was quick. Regarding mobile dev, on native dev vs. using React native, I'd say there's an advantage to being able to handle native navigation and animations, a wall that one might run into when developing on a hybrid app platform like RN. Additionally, a little company history: Queenly was an iOS-first app, launched first to prioritized our power sellers in our community. The React web app followed that, with enough user growth in between to shelve any considerations for a migration to RN.


Short answer is an absolute yes! Would recommend building programming skills and experience in areas that build on whatever professional, academic experience/credentials you already have. For example, Python+Data Science if you have some math background or have worked in industries that use analytics a lot. Embedded systems if you have worked in auto, hardware/electronics, aviation industries etc. In general, try and use your age and experience to project a well rounded technical ability. Programmers are easy to find, but coders with good ___domain expertise are more valuable and hard to find. Also very valuable are demonstrable communication skills, especially written. So, if you have maintained any blogs or have had a journalistic stint you can use that to your advantage. Ageism exists no doubt, but a) tech industry continues to be one of the biggest drivers of jobs worldwide b) freelance/remote work based careers to some extent provide 'age irrelevant' opportunities. Overall, welcome and good luck!


They've recently launched an app to help with this discovery. https://techcrunch.com/2020/04/28/shopify-launches-shop-a-ne...


This might be of interest - https://frontendmasters.com/. Not tried them, have no affiliation.


Amazingly little to no use of images in the articles. Turning the 'an image is worth a thousand words' on its head. Seems to work well though. Examples: https://aws.amazon.com/builders-library/avoiding-insurmounta..., https://aws.amazon.com/builders-library/caching-challenges-a...


Good point. We should use more images. I’ll think about where we can add some for clarity! Now that we’ve done a bunch of talks at reinvent in these topics, we should have some that we can incorporate easily.


Compose (http://compose.io) offers RethinkDB, and doesn't look too expensive, but no free tier :-(.


Another virtual dom based framework worth a serious look is Mithril [1]. JS, all the way.

[1] http://mithriljs.org


1) Transfer your overall web development skills to another language/platform (Go, Clojure, Elixir or JS/Node). For anyone 'spoilt' by the beauty of Ruby, Clojure and Elixir are good choices. Given that you are coding professionally since 2008, you should be able to move into 'adept' category quickly in any of the above.

2) Utilize your Ruby programming expertise and become a Mobile developer !! Check out Rubymotion.com. Code in Ruby for Android and iOS.


Is it actually practical to use ruby for mobile apps as a contractor? I imagine most folks will want you to code native, no?


The main website didn't have a link to the docs, but found them here - http://docs.structr.org/ via the blog link - http://structr.org/blog/structr-10-data-cms-on-neo4j-release...


Only the fat Documentation link beside Download on the main screen (center) ;-)


To be fair: we added the button just now.. :)


ok ;)



Ah, this is cool. I really hope something like this grows/stabilizes and becomes the de-facto for web.

I think it takes 2 things... 1. Simple deploy of languages/services. 2. Scalability solutions (processing power / RAM / network interactivity).

I bet #1 is possible here, #2 seems less clear to me. any knowledge off the top of your head?


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: