26 Days of Commitment: A Video Journal
- Thread starter boatBurner
- Start date
(O_o)
H̨̼̩͐̑͆̀̚&
Anyone with his fucking journal, a strange trend on WF.
The only journal I'll follow is for an aspiring webcam girl and her "10 days to a massive 30cm anal dildo"
The only journal I'll follow is for an aspiring webcam girl and her "10 days to a massive 30cm anal dildo"
That is an impressive amount of courage and discipline, if you follow through. There is no possible downside to this because even if you haven't mastered RoR by the end of your leave you will at least have one helluva head start and a foundation to build on.
Congrats on your commitment, and cheers to you as well sir.
- subbed
Congrats on your commitment, and cheers to you as well sir.
- subbed
I think the so-called trend of journals is a good one. It's almost a case study of sorts, and no matter the end result, once completed the journal will hold value for people with relevant interests.
It's shit like this that adds significance to a community, imo. And I'll be damned if I joined a community full of peweps.
Normally I hate journal type threads, because they usually go nowhere. But I think you're the type who will actually follow through and make it so I wish you the best of luck.
I don't do much designing/coding myself. I tend to outsource that stuff, but one of the guys I ended up hiring full time for a web app I did a few months back was a teller at my bank. We got in to a convo about my business etc and the dude told me a story of how he learned to code php in 4 days -a friend of his had had a one of his friends searching for coders for a 5k paying php gig. So he asked him (the teller) if he knew anyone who could code this, to which he said that sure, he could do it himself and when pressed by his friend if he even knew any php he basically "yeah, yeah, do it all the time".
He didn't know squat but learned it by the deadline and kept on learning through out the job. At the end of it he even got a written recommendation from the company doing doing such a slammin job.
I know another guy who didn't know squat about adwords but got hired almost the same way as an adwords manager at a company -mind you this is a company spending 2mil a year on adwords. He took (or more like weasled his way in to the job) blind and spent the next 2 weeks reading adwords books til his eyes bled and even going so far as spending $500 of his own savings too test the concepts in action since he he knew that he'd make that back and more if he did the job right. Which he did.
Point is they got initiative while some other guys I know have spent months trying to learn HTML and CSS (and everything else) and got nowhere.
Always learn under pressure. Have something specific in mind to build and attach a hard deadline and start doing and screwing up in the process. Don't do it theoretical.
You definitely seem like someone who'll do well though so good luck, I have no coding advice in general to give except to keep on the pressure and dont give in if you screw crap up.
I don't do much designing/coding myself. I tend to outsource that stuff, but one of the guys I ended up hiring full time for a web app I did a few months back was a teller at my bank. We got in to a convo about my business etc and the dude told me a story of how he learned to code php in 4 days -a friend of his had had a one of his friends searching for coders for a 5k paying php gig. So he asked him (the teller) if he knew anyone who could code this, to which he said that sure, he could do it himself and when pressed by his friend if he even knew any php he basically "yeah, yeah, do it all the time".
He didn't know squat but learned it by the deadline and kept on learning through out the job. At the end of it he even got a written recommendation from the company doing doing such a slammin job.
I know another guy who didn't know squat about adwords but got hired almost the same way as an adwords manager at a company -mind you this is a company spending 2mil a year on adwords. He took (or more like weasled his way in to the job) blind and spent the next 2 weeks reading adwords books til his eyes bled and even going so far as spending $500 of his own savings too test the concepts in action since he he knew that he'd make that back and more if he did the job right. Which he did.
Point is they got initiative while some other guys I know have spent months trying to learn HTML and CSS (and everything else) and got nowhere.
Always learn under pressure. Have something specific in mind to build and attach a hard deadline and start doing and screwing up in the process. Don't do it theoretical.
You definitely seem like someone who'll do well though so good luck, I have no coding advice in general to give except to keep on the pressure and dont give in if you screw crap up.
good shit tom, next time I'm on skype I'll give you my direct contact info if you need any help with anything since I'm erratic when it comes to staying logged into skype
Fuck you Tom. I spent 80+ seconds letting you know that you may have a small raptor problem and you can't even "like" my post?
lolol
touche good sir, I didn't actually see the raptor until you pointed it out. I was certain we had rid the house of those pests last weekend.
Update: Gameplan
[ame="http://www.youtube.com/watch?v=CYQt1RjsWSQ"]Learning Ruby on Rails in 26 Days: The Gameplan - YouTube[/ame]
An update: the gameplan.
[ame="http://www.youtube.com/watch?v=CYQt1RjsWSQ"]Learning Ruby on Rails in 26 Days: The Gameplan - YouTube[/ame]
An update: the gameplan.
^ Just watched the "gameplan", good luck with it.
Here's a suggestion. Figure out some kind of application or problem you want to solve using Ruby on Rails and then space the solving of that specific problem out over the 26 days and with each step post in extreme detail any questions you have about concepts or implementation. Since there are a lot of developers rooting for you, and we all think we know what the hell we are talking about, you won't be wanting for opinions and answers. RoR will do a lot for you but you may find it hides things from you may not realize you need to know, for example, database normalization (and MongoDB is not a excuse to not understand DB normalization).
Soliciting requests from the community sounds nice but you'd probably spend more time dicking around figuring out what somebody actually wants as opposed to building it, and if it's truly trivial to build it probably exists and has been open sourced somewhere already and if you feel you are under deadline to somebody else you may not take the time to explore the concepts behind the requirements that will go into transitioning form a simple "coder" to a "developer".
You may as well try and find one thing you can follow through from day 1 to 26 and have a real app to show for it at the end of the period. Are there any unique "itches" you can scratch amongst the discharged (or soon to be) community? Or do you have any apps that you currently think you would want to rebuild in your own style? You may not think building something of value would take more than 26 days but really 26 days isn't much time. Just because a demo video shows you how to "build" a blog in RoR in 10 minutes doesn't mean you would know what was abstracted away from you (a lot) and how you could apply similar patterns to different concepts or contexts.
Here's a suggestion. Figure out some kind of application or problem you want to solve using Ruby on Rails and then space the solving of that specific problem out over the 26 days and with each step post in extreme detail any questions you have about concepts or implementation. Since there are a lot of developers rooting for you, and we all think we know what the hell we are talking about, you won't be wanting for opinions and answers. RoR will do a lot for you but you may find it hides things from you may not realize you need to know, for example, database normalization (and MongoDB is not a excuse to not understand DB normalization).
Soliciting requests from the community sounds nice but you'd probably spend more time dicking around figuring out what somebody actually wants as opposed to building it, and if it's truly trivial to build it probably exists and has been open sourced somewhere already and if you feel you are under deadline to somebody else you may not take the time to explore the concepts behind the requirements that will go into transitioning form a simple "coder" to a "developer".
You may as well try and find one thing you can follow through from day 1 to 26 and have a real app to show for it at the end of the period. Are there any unique "itches" you can scratch amongst the discharged (or soon to be) community? Or do you have any apps that you currently think you would want to rebuild in your own style? You may not think building something of value would take more than 26 days but really 26 days isn't much time. Just because a demo video shows you how to "build" a blog in RoR in 10 minutes doesn't mean you would know what was abstracted away from you (a lot) and how you could apply similar patterns to different concepts or contexts.
Concur, ST2 is nice. I've been getting away from Visual Studio over the last three months and it's pretty liberating.
Fortunately I was read in on Sublime Text 2, so it is currently my primary editor.
Also justo, I really like your idea about picking one big idea and rolling through with it. My only reservation is the time it would take to really plan and break down (for the first time, mind you) the small processes to focus on. Any ideas for that?
Also justo, I really like your idea about picking one big idea and rolling through with it. My only reservation is the time it would take to really plan and break down (for the first time, mind you) the small processes to focus on. Any ideas for that?
