Sounds like a UX nightmare and a huge pain. I'm glad that privacy maximalists don't design user interfaces...
Wow, this comment sounds a lot more dickish than it was intended to. What I mean is, secure design would be that the app can't even see repos that it isn't authorized for, which means the user has to go through some back channel privacy settings page to authorize it every time they set up a new repo.
I don't want to have to specifically authorize x y and z repos every time I touch the app, and I seriously doubt anyone else does either.
Actually we do design UI, every day. And there are plenty of ways to do this in a comfortable fashion without authorizing read access to the contents of every repository. You could for example, show a list of all repos and when you click to edit one for the first time ask for permissions once for that repository - hardly a UX nightmare?
You probably don't want some random, just-released / potentially buggy application touching all your repos. Wouldn't you want to test it on a throwaway repository first to see if you actually want to use the app / does the app work properly, and then authorize it only for the repos you want.
I see the value of a lot of these programs/courses as connecting you with your first job. What did that look like for you? Did you move? Find something local? Did Tealeaf help you?
This course doesn't have the direct matching that the in person courses do. It's mostly on you. They do encourage you to attend local meetups to network.
I live in the same city as one of the instructors and he offered to connect me with local people for a job, but I ended up not needing it as I got a job with the person who ran my local meetup.
i am a graduate of tealeaf academy. i took all 3 courses, which took about 4 months to complete. I got my 1st dev job about 2 mo. later. They did help find a job by introducing me to their rails/ruby contacts in the city i was living in. I didn't have any OOP experience prior to the course. I totally recommend this if you want to learn rails to bootstrap your own product or change careers and become a dev. I did this for both.
You know, I never asked him directly what he thought about it. He was just happy I knew rails, and knew programming enough to work in other languages as well.
