I have a friend who’s looking to become a marketable developer fairly quickly, but is essentially trying to go from zero to hero. Despite starting a project in Python to randomize wedding slideshows, he’s never really done development, nor does he understand its core concepts (classes vs. objects, for instance).
He kinda just needs a job, plus the ability to make useful tools for himself.
Folks are telling him Java and *.NET, and I (mostly) agree for the simple purposes of 1) easy desktop or web development, and 2) using keyword-heavy languages to reinforce programming concepts. Not strong reasons, no. If he just wanted a job, I’d recommend UI development.
Plus, for marketability in Charlotte, NC–home of plenty of Big Banks–diving into quasi-enterprise development can get you a cube (albeit maybe shared) and a comfortable paycheck. Good luck finding a Python gig here.
The goal was to handle recurring donations. Every month, Suzy wants to donate $10 to Cool NPO. It’s not a pledge, in that she’s not dedicating herself to $120 for one year. Just $10/month. (Forever! Bwua-ha-ha!)
In the interests of pushing my .NET knowledge, I began migrating the Geist character sheet project that I’d started in Django to .NET MVC 3. I hadn’t done MVC in .NET since MVC 1 was beta’d, but hey, MVC is MVC is MVC. Right?
So in the interests of making things more interesting and more testable, I decided to dive into the Entity Framework 4. My beginning read of POJOs in Action, along with my previous experience with .netTears–I mean, .netTiers–had me generally familiar with the concepts of entities, contexts, and repositories.
Kicker is, POJOs is just a book (and one I’ve barely dived into), and .netTears uses code generation, meaning I could get away with treating it as just a very hefty ORM in the applications it was in. Generate and go.
Getting my fingers in it was a whole ‘nother experience.