I searched and I found a lot of old stuff because Discourse was heavy updated. I liked to read the work leading your sucess.
I’m not a dev but I paid a lot of ‘devs’ that work 1/10 as I can (of course, not on Discourse). So I’m here trying to learn more 
Primarly because I born in a country without so much discipline, responsability or motivation to do things and doing is on me from I remember my life.
I’m using computers from DOS and used the first 3.1 Windows PC’s. So probably I’m with a lot of folks around that started playing and then gets involved into their own tech related communities and/or business.
I can read basic lines of code, I was very good at logic on school but I don’t have more background and I know that’s not enough.
I’ve installed our Discourse instance plus a couple of apps on Linux because I’m in Linux from more than 10 years ago.
I always felt at home with terminal and back-end. CSS gives me headache so I’m on the way leaving that for artists (!)
Random freelancers are worst than solo breaking things and 2/5k for solve specific things in a 10/15 to-do list are too expensive for me until scaling or a couple of years to my finance.
I’m ENFJ and kind of street engineer if the real engineers here don’t ban me for sacrilege or trolling with this words 
The point
Is possible to someone with my very little IT background, learn rails, use the API and the back-end apps where Discourse is built?
You use sideqik and know how to search, modify and delete all the things from Rails and I really want the same.
EDIT: Please, don’t get me wrong. I’m not asking how to be a developer but understanding more to improve my work with them.
Knowing the basis for guiding developers without experience on Discourse back-end (that’s very common those days) is mandatory for me and I wish to learn.
Thanks for read!
4 posts - 4 participants
This is a companion discussion topic for the original entry at https://meta.discourse.org/t/how-to-learn-more-about-discourse-back-end/260765