Podcasts about rails tutorial

01:16 - Brandon’s Superpower: Recognizing Others’ Superpowers and Spotting Potential Talent * Convincing Others * Recognizing and Talking About Failure(s) 09:23 - Brandon’s Personal Journey & Transformation Towards Humility * Wanting To Be Heard * Placing Identity * Developing Empathy * Speaking Candidly Re: Growth * Talking About Negatives in Your Past 25:40 - The Importance of Community and Community Leaders * The Ruby Scholar and Guide Program (https://rubyconf.org/scholarships) * Michael Hartl’s Rails Tutorial (https://www.railstutorial.org/book) * The Beerware License (https://people.freebsd.org/~phk/) 34:35 - Being Kind vs Being Nice * Privilege 40:59 - Being Austistic and Being Visible * Tales of the Autistic Developer - The Mentor (https://dev.to/baweaver/tales-of-the-autistic-developer-the-mentor-5hi6) * Brandon’s illustrated conference talks with cartoon lemurs (https://twitter.com/keystonelemur/status/1291488545450926086) * “Looks like me” * Calling Out Hubris (https://www.merriam-webster.com/dictionary/hubris) 52:32 - Tech Is Political Reflections: Jamey: When someone gives you feedback it’s because they trust you that you’re going to do something about yourself and do better. Brandon: Thinking about who is saying something. John: The power we can embrace by talking about our personal history. This episode was brought to you by @therubyrep (https://twitter.com/therubyrep) of DevReps, LLC (http://www.devreps.com/). To pledge your support and to join our awesome Slack community, visit patreon.com/greaterthancode (https://www.patreon.com/greaterthancode) To make a one-time donation so that we can continue to bring you more content and transcripts like this, please do so at paypal.me/devreps (https://www.paypal.me/devreps). You will also get an invitation to our Slack community this way as well. Special Guest: Brandon Weaver.

THEMES DISCUSSED: Going through a coding bootcampGender equity in techInternship Experience Career goals RESOURCES MENTIONED:Actualize Coding Bootcamp Main Street Codes Ruby on Rails Tutorial  UdemyCodecademy CONNECT WITH MITCHLinkedIn: https://www.linkedin.com/in/heymitchfischer/Twitter: https://twitter.com/heymitchfischerCONNECT WITH CECITwitter: https://twitter.com/CeciBenitez13LinkedIn: https://www.linkedin.com/in/cfischerbenitez FOLLOW THE PODCAST: Twitter: https://twitter.com/ChicagoTechiesInstagram: https://www.instagram.com/chicagotechies/Facebook: https://www.facebook.com/chicagotechiesLinkedIn: Chicago Techies Podcast Music composed by Anna Eichenauer, check out her work here. Thank you so much for listening to this podcast! If you enjoyed listening to this episode, please leave a rating and a review on iTunes. Use the hashtag #ChicagoTechies for any shoutouts and comments on our episodes.

Welcome to another episode of Develomentor. Today's guest is Michael HartlMichael is an education entrepreneur and the founder of Learn Enough. Michael is the author of over ten books, including the Ruby on Rails Tutorial, one of the leading introductions to web development, and received a Ruby Hero Award for his contributions to the Ruby community. He is also the author of the influential mathematical essay The Tau Manifesto and founded the internationally celebrated math holiday Tau Day in 2010. Previously, Michael taught the core physics curriculum at Caltech, where he was a popular instructor with the students and received a Lifetime Achievement Award for Excellence in Teaching. He is a graduate of Harvard College, has a Ph.D. in Physics from Caltech, and is an alumnus of the Y Combinator entrepreneur program.Apart from his interests in education and entrepreneurship, Michael enjoys choral singing, studying languages, and reading old books. He is also an advanced student of Krav Maga, holding a Level 5 rank (a “black belt in self-defense”).(https://www.learnenough.com/about)If you are enjoying our content, click here to support us!Quotes“It took me a while to figure out as an entrepreneur that what should I be doing is taking the teaching and writing skill sets that I learned in grad school and applying them to product creation.”“Don’t all move to Silicon Valley. Realize that Silicon Valley is on the web and you can find it with a web browser.”—Michael HartlKey MilestonesWhat inspired Michael to start companies and to be in tech?Michael recalls some of his early failures as an entrepreneur.Insoshi was a Y Combinator backed social network that Michael founded. What was it like working with Y Combinator in the early days?Michael shares his path for becoming an education entrepreneurHow was Michael able to write a book on coding without having the a computer science background?What is some background on Michael’s tech education company Learn Enough? What does Michael you have against the number Pi? The Tau manifestoAdditional Resourcesclick here for full episode show notes Essays by Paul Graham (one of the founders of Y Combinator) – http://www.paulgraham.com/articles.htmlRuby on Rails Tutorial – tech book written by Michael HartlLearn Python the Hard Way: by Zed Shaw The Tau Manifesto – Michael explains that Pi isn’t all its made out it be – https://tauday.com/tau-manifestoConnect with Michael HartlLinkedInTwitterhttps://www.learnenough.com/https://www.railstutorial.org/Follow DevelomentorTwitter: @develomentorConnect with Grant IngersollLinkedInTwitter

I talk with Michael about various miscellaneous topics including evolution, Stephen Hawking, Tau (a number equal to two times pi), Michael’s time in Y Combinator, and Michael’s experience developing the Ruby on Rails Tutorial.

On this week's episode, Steph returns from vacation and Chris makes some noise about a fantastic new button. They discuss Steph's continued adventures in search of the perfect mechanical keyboard and then dig into two listener questions on landing a first job as a developer and what frameworks and languages to focus on, as well as discussing some of the common objections to GraphQL.Rails ActionableErrors - Migration ButtonCODE KeyboardKeychron K2 keyboardCassidy Williams on TwitterAvdi Confident Code talkAvdi Confident Ruby bookRobustness principleThe Rails TutorialStack Overflow 2019 developer surveyDataloader for GraphQLgraphql-batch from ShopifyGraphQL persisted Queries

This week we're joined by Zach Gibb, a Software Engineer at Hoard, for a conversation about how he transformed from having no interest in computers to using them every day to creatively solve problems. While we certainly learn a lot about what programming is, and how someone might get started building websites, we also talk about other communication skills that make someone great at working with others. Show Notes What did Zach do to get started? How do you even build a website? Imposter Syndrome: a psychological pattern in which an individual doubts their accomplishments and has a persistent internalized fear of being exposed as a "fraud" Getting past your fear by breaking down big problems into small ones Personality traits that might help you with software engineering Overcoming anxiety and how it relates to writing software Links Zach's Linked In (https://www.linkedin.com/in/zachgibb/) Follow Zach (https://www.instagram.com/zachgibb) on Instagram Learn more about imposter syndrome (https://en.wikipedia.org/wiki/Impostor_syndrome) Interested in learning to code? Steve's a big fan of this one: Rails Tutorial (https://www.railstutorial.org/book) — but seriously, if you finish it, you'll know how to code. It's easy when you Learn Code the Hard Way (https://learncodethehardway.org/) There's lots of great courses on Udemy (https://www.udemy.com), but make sure you look for sales! Please also feel free to get in touch with us... happy to help you get on the right path! Big thanks to NGHTSWM (https://itunes.apple.com/us/artist/nghtswm/1316607579) for the use of their song, Fiji (https://itunes.apple.com/us/album/fiji-single/1436041716), on this show.

Sponsors: Sentry use the code “devchat” for 2 months free on Sentry small plan CacheFly Host: Charles Max Wood Special Guest:  Josh Justice Episode Summary In this episode of My Ruby Story, Charles hosts Josh Justice, software engineer at Big Nerd Ranch, a Mobile app development, training and design firm. Listen to Josh on the podcast Ruby Rogues on this episode. Josh wanted to be a software developer ever since he was very young, his father worked in IT so he had access to computers from very early on. After studying computer science, he started working as a developer in JavaScript, PHP and in Ruby. His specialties include Ruby on Rails, Ember, Vue.js and React Native. Josh really enjoys content creation for other developers and is currently streaming React Native TDD Fridays 2pm EST at Twitch.tv. Josh and his family recently adopted a baby boy in addition to his two daughters. Listen to the podcast to hear more about this miraculous adoption story! Links Ruby Rogues 391: Frontend Testing Like a Rubyist with Josh Justice React Native Testing feat. Josh Justice of Big Nerd Ranch Josh’s Twitter Josh’s GitHub Josh’s LinkedIn Michael Hartl's Ruby on Rails Tutorial Josh's Blog Learn Test-Driven Development Object Oriented and Functional Programming Blog Post https://devchat.tv/ruby-rogues/ https://devchat.tv/my-ruby-story/ https://www.facebook.com/DevChattv Picks Josh Justice: Webpacker Object Thinking Learn Test-Driven Development Ember and Rails Live Stream   Charles Max Wood: The Effective Executive by Peter F. Drucker      

Sponsors: Sentry use the code “devchat” for 2 months free on Sentry small plan CacheFly Host: Charles Max Wood Special Guest:  Josh Justice Episode Summary In this episode of My Ruby Story, Charles hosts Josh Justice, software engineer at Big Nerd Ranch, a Mobile app development, training and design firm. Listen to Josh on the podcast Ruby Rogues on this episode. Josh wanted to be a software developer ever since he was very young, his father worked in IT so he had access to computers from very early on. After studying computer science, he started working as a developer in JavaScript, PHP and in Ruby. His specialties include Ruby on Rails, Ember, Vue.js and React Native. Josh really enjoys content creation for other developers and is currently streaming React Native TDD Fridays 2pm EST at Twitch.tv. Josh and his family recently adopted a baby boy in addition to his two daughters. Listen to the podcast to hear more about this miraculous adoption story! Links Ruby Rogues 391: Frontend Testing Like a Rubyist with Josh Justice React Native Testing feat. Josh Justice of Big Nerd Ranch Josh’s Twitter Josh’s GitHub Josh’s LinkedIn Michael Hartl's Ruby on Rails Tutorial Josh's Blog Learn Test-Driven Development Object Oriented and Functional Programming Blog Post https://devchat.tv/ruby-rogues/ https://devchat.tv/my-ruby-story/ https://www.facebook.com/DevChattv Picks Josh Justice: Webpacker Object Thinking Learn Test-Driven Development Ember and Rails Live Stream   Charles Max Wood: The Effective Executive by Peter F. Drucker      

Sponsors: Sentry use the code “devchat” for 2 months free on Sentry small plan CacheFly Host: Charles Max Wood Special Guest:  Josh Justice Episode Summary In this episode of My Ruby Story, Charles hosts Josh Justice, software engineer at Big Nerd Ranch, a Mobile app development, training and design firm. Listen to Josh on the podcast Ruby Rogues on this episode. Josh wanted to be a software developer ever since he was very young, his father worked in IT so he had access to computers from very early on. After studying computer science, he started working as a developer in JavaScript, PHP and in Ruby. His specialties include Ruby on Rails, Ember, Vue.js and React Native. Josh really enjoys content creation for other developers and is currently streaming React Native TDD Fridays 2pm EST at Twitch.tv. Josh and his family recently adopted a baby boy in addition to his two daughters. Listen to the podcast to hear more about this miraculous adoption story! Links Ruby Rogues 391: Frontend Testing Like a Rubyist with Josh Justice React Native Testing feat. Josh Justice of Big Nerd Ranch Josh’s Twitter Josh’s GitHub Josh’s LinkedIn Michael Hartl's Ruby on Rails Tutorial Josh's Blog Learn Test-Driven Development Object Oriented and Functional Programming Blog Post https://devchat.tv/ruby-rogues/ https://devchat.tv/my-ruby-story/ https://www.facebook.com/DevChattv Picks Josh Justice: Webpacker Object Thinking Learn Test-Driven Development Ember and Rails Live Stream   Charles Max Wood: The Effective Executive by Peter F. Drucker      

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan CacheFly Host: Charles Max Wood Special Guest:  Chandan Jhunjhunwal Episode Summary In this episode of My Ruby Story, Charles hosts Chandan Jhunjhunwal, a tech lead at Coupa Software from Pune India. Listen to Chandan on the podcast Ruby Rogues on this episode. Chandan studied electronics in university but was hired as a software engineer at IBM after university and really liked programming. He then continued working as a developer for a startup before founding his own startup. Chandan is now working for the procurement department at Coupa Software. Chandan feels that no matter what your background is, nothing is too hard and  if you like something you should dive in and do it. He also points out that especially in technology there is always a learning curve. Links Ruby Rogues 314: DynamoDB on Rails with Chandan Jhunjhunwal Chandan's GitHub Chandan’s Twitter Chandan's LinkedIn https://devchat.tv/my-ruby-story/ https://www.facebook.com/DevChattv Picks Chandan Jhunjhunwal: Rescuing The Daughter No Ordinary Moments by Dan Millman Michael Hartl's Ruby on Rails Tutorial Metaprogramming Ruby by Paolo Perrotta   Charles Max Wood: Born to Run by Christopher McDougall Ultramarathonman by Dean Karnazes

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan CacheFly Host: Charles Max Wood Special Guest:  Chandan Jhunjhunwal Episode Summary In this episode of My Ruby Story, Charles hosts Chandan Jhunjhunwal, a tech lead at Coupa Software from Pune India. Listen to Chandan on the podcast Ruby Rogues on this episode. Chandan studied electronics in university but was hired as a software engineer at IBM after university and really liked programming. He then continued working as a developer for a startup before founding his own startup. Chandan is now working for the procurement department at Coupa Software. Chandan feels that no matter what your background is, nothing is too hard and  if you like something you should dive in and do it. He also points out that especially in technology there is always a learning curve. Links Ruby Rogues 314: DynamoDB on Rails with Chandan Jhunjhunwal Chandan's GitHub Chandan’s Twitter Chandan's LinkedIn https://devchat.tv/my-ruby-story/ https://www.facebook.com/DevChattv Picks Chandan Jhunjhunwal: Rescuing The Daughter No Ordinary Moments by Dan Millman Michael Hartl's Ruby on Rails Tutorial Metaprogramming Ruby by Paolo Perrotta   Charles Max Wood: Born to Run by Christopher McDougall Ultramarathonman by Dean Karnazes

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan CacheFly Host: Charles Max Wood Special Guest:  Chandan Jhunjhunwal Episode Summary In this episode of My Ruby Story, Charles hosts Chandan Jhunjhunwal, a tech lead at Coupa Software from Pune India. Listen to Chandan on the podcast Ruby Rogues on this episode. Chandan studied electronics in university but was hired as a software engineer at IBM after university and really liked programming. He then continued working as a developer for a startup before founding his own startup. Chandan is now working for the procurement department at Coupa Software. Chandan feels that no matter what your background is, nothing is too hard and  if you like something you should dive in and do it. He also points out that especially in technology there is always a learning curve. Links Ruby Rogues 314: DynamoDB on Rails with Chandan Jhunjhunwal Chandan's GitHub Chandan’s Twitter Chandan's LinkedIn https://devchat.tv/my-ruby-story/ https://www.facebook.com/DevChattv Picks Chandan Jhunjhunwal: Rescuing The Daughter No Ordinary Moments by Dan Millman Michael Hartl's Ruby on Rails Tutorial Metaprogramming Ruby by Paolo Perrotta   Charles Max Wood: Born to Run by Christopher McDougall Ultramarathonman by Dean Karnazes

Are you trying to get a jump-start on your tech career while you're still in school? Have you found that perfect internship - or job - but you're not sure how to approach it? If so, this is the resource for you. Michael discusses how to craft your résumé, how to prepare for interviews, and much more. Written by Michael Deng: https://twitter.com/themichaeldeng Read by Abbey Rennemeyer: https://twitter.com/abbeyrenn Original article: https://fcc.im/2BCESfo Learn to code for free at: https://www.freecodecamp.org Intro music by Vangough: https://fcc.im/2APOG02 Transcript: Seven semesters ago, I started college with no programming background. The only thing I had was lofty aspirations of working in tech. When recruiting season first rolled around, I applied to a bunch of companies. I got a few callbacks, but that’s it. No follow-ups. No onsite interviews. Nothing. I kept trying. I applied to over 150 companies. I faced dozens of interviews. I failed way more than I succeeded. But that’s all right. Because those failures made my moments of triumph all the more memorable. Along the way, I met helpful mentors and guided ambitious mentees. These people are now working at places like Airbnb, Facebook, Google, SpaceX, and Snap. As for me, I landed an internship at Uber last summer. And I’m on track to accept a full-time job at one of my favorite companies when I graduate. Now that I’m in my final year of school, I want to share everything I’ve learned over the years. This isn’t meant to be the ultimate handbook. It’s only a modest guide born out of my love of helping others reach their goals (and my love of Legos). By the end of this article, you’ll know everything I wish I had known when I first started sending in applications. A few words before we begin… Don’t let your struggle for the perfect job take over your life. School is a time of self-discovery and all-around personal growth. So go out there and meet people who are doing different things. Join diverse student organizations and take part in activities outside your comfort zone. It’s all too easy to associate your self-worth with how prestigious of a job you can get. But remember: there are so many more important things in life than work. My best memories of college aren’t spending weeks on end prepping for interviews or even getting offer phone calls. They’re exploring San Francisco for the first time with my closest friends. They’re playing volleyball with my hilarious teammates. I value these unique experiences I shared with people I love much more than any job. To paraphrase my favorite quote by Twitter and Medium founder Ev Williams: “Failure of your [work] is not failure in life. Failure in your relationships is.” Don’t lose sight of what’s important. It’s also no coincidence that everyone I know with a strong support system eventually found success. When you fall into a slump — and all of us do — you need your friends to be there for you. I would never have made it through my first year without amazing friends who kept me afloat. Now, let’s get started. You pumped? I’m pumped! Building fundamentals Before we get to the good stuff, you need to build solid fundamentals. Seems obvious? Absolutely. But this is the hardest step of this guide, so listen up. Now, this guide is designed for college students, so if you’re in high school, scram! Just kidding. In fact, I admire your initiative. When I was in high school, I didn’t have the faintest idea what I wanted to do. Leading up to college, your top priority should be solidifying your math skills. Computer science relies heavily on mathematic concepts like probability, logic, and number theory. Without math, you’re not going to get far in hard weeder classes and technical interviews. If you’re already proficient in math, keep reading. Most of this guide is just as applicable to you as it is to college students. Skip to the online classes section below and progress through the rest of this guide. Landing an internship as a high schooler is challenging, but certainly not impossible. OK. Back to college students. Building fundamentals starts with your intro programming classes. Pay attention and master the basics. A popular but misguided notion is “GPA doesn’t matter.” Although it’s true that most companies won’t scrutinize your GPA, any gaps in your fundamental knowledge will come back to bite you later. By getting a decent GPA, you’re also most likely getting a grasp of the basics. Your classes will cover a lot of basic knowledge, but they’ll barely scratch the surface of modern technology. Go explore interesting topics around the core concepts taught in class. This is how you gain a breadth of knowledge and come up with future project ideas. If you’re not studying computer science, don’t worry. I have friends who changed their minds and started CS their Junior year. They still graduated on time with great job offers, so you’re not too late at all. This said, you will need to make sacrifices and take extra classes every semester. If you’re not able to take CS classes in college, there are plenty of awesome online resources to help you out. Two of the best online intro courses are Harvard CS50x on edX and CS101 on Udacity. After this intro, you need to master data structures and algorithms. I recommend Princeton Algorithms Part 1 and Part 2 on Coursera, or CS61B by UC Berkeley. To make sure you’re on track, reference Google’s Technical Development Guide. Don’t worry if you struggle at first. A few weeks into my first semester, I was completely overwhelmed. I spent days studying concepts that took other students hours to grasp. I thought about giving up every week. “How am I ever going to catch up to those prodigies?” But if you ask me or any of my friends who made it through, we’ll all tell you the same thing: Learning to program isn’t about how talented you are or how early you started coding. It’s about perseverance. Building up your programming intuition takes a long time — much like learning a human language. You won’t see the light at the end of the tunnel for a long time. But trust me. If you take one step at a time, you will eventually get there. Staying motivated is difficult, but there’s a secret. Focus on mastery instead of results. Make it your goal to get better at a skill rather than achieve a certain result. Dr. Heidi Grant Halvorson did a study where she asked two groups of people to solve various problems. The first group was told to score as high as they could. The second group was told to treat the problems as a learning opportunity. The results were surprising. The first group got frustrated, whereas the second group persisted and solved more problems.​ By focusing on mastery, you view obstacles and time pressure as things that will help you grow. In contrast, a result-oriented mindset frames problems as irritating roadblocks impeding your way. What’s more, you’ll see continual progress if you concentrate on mastery. Every time you read a new paragraph or solve a new question, you’re improving your skills. This kind of continuous gratification is incredibly satisfying. So next time you’re studying for class or practicing for interviews, focus on getting better instead of acing the exam or landing the offer. You can read more about this tactic in Edmond Lau’s Quora post. Beyond basic coding skills, you need to know what’s happening in the tech industry. This goes beyond sounding smart during recruiting. By paying attention to the industry, you’ll be the first to discover new opportunities to propel your career forward.​ For online reading, check out TechCrunch, Techmeme, Product Hunt, and Hacker News. If you’re a frequent Twitter user, follow tech news sources. On Medium and Quora, personalize your feeds to get insightful takes on the industry. If you’re into email newsletters, look into Axios Pro Rata, CB Insights, and Mattermark Daily. To do a deep dive on a particular company, use Crunchbase and the company’s blog. You can also learn about the company’s culture from Glassdoor. Finally, don’t forget to actually talk to people. I learned so much about the tech world from casual conversations with friends and classmates. Over time, you’ll read about a lot of interesting companies. Begin compiling a spreadsheet of companies you’re interested in from day 1. When you apply to these companies in the future, use this spreadsheet to track your progress. Once you have the fundamentals down, it’s time to apply your skills. One of the best ways to do that is by… Building projects If you’re like me, you don’t have much experience to begin with, and that’s OK! The first step is populating that empty resume with projects. When I first decided to work on a project, I had decision paralysis for days. “What should I make? What if it’s not original? What if people don’t like it?” Later, I realized it doesn’t really matter what the project is. Learning something and finishing what you start is much more important. But this doesn’t mean you can make whatever you want. If your project is too trivial, you won’t impress any recruiters. If yourq project is too complex, you’ll lose momentum before completing it. Aim to do a project you think you can complete in one to two months. The project should involve data structures, algorithms, and design decisions. And do something you’re interested in so you’ll actually take it all the way to completion. Here’s a compilation of project ideas on Reddit for inspiration. After coming up with an idea, take some time to plan, but don’t take too long. You want to start as soon as possible. Now, you might be wondering “Isn’t it irresponsible to jump in prematurely?” Generally, yes. But personal projects are different from company projects. Personal projects should teach you something new and strengthen your background during recruiting. Unlike company projects, you don’t need to obsess over design and code quality. If you’re feeling stuck at the beginning, write down some code — any code. Building a personal project is like writing, you just start. Don’t worry if it doesn’t make sense. Seeing code in an editor will get your juices flowing. Track your project with version control. If you don’t know what that is, make a Github account and learn how to use Git. You need Github as it’s the primary way you save and display your projects. If you can, make your project live so recruiters can play with it. Most recruiters won’t inspect your code, so a live demo is the best way to show off your project. Aim to complete three to five projects by the time you start applying. A terrific first project is a personal website. You learn the basics of web development and get your own space on the internet to display your work. Codecademy has two excellent tutorials on building websites: Make a Website teaches you the basics of HTML, CSS, and Bootstrap. Deploy a Website teaches you how to put your website on the internet. Step 3 of this tutorial isn’t necessary, just use the free .github.io domain. Too easy? Convert your personal website into a dynamic blog. To do this, you need to learn a web development framework like Rails or Django. Check out the Ruby on Rails Tutorial or The Django Girls Guide. The Muse and Awwwards have examples of personal websites if you need design inspiration. Also, you have to check out this wicked personal website. Hackathons are great for motivating yourself to do projects. Schools and organizations around the world host hackathons, which are project-building competitions lasting several days. In this short span of time, you’ll learn a lot, come up with unique ideas, and meet interesting people. Many hackathons reimburse travel, so there’s no excuse not to go. Use Hackalist or Hackevents to discover upcoming ones. Some of the top North American hackathons I know of are PennApps, HackMIT, HackNY, MHacks, HackTech, HackIllinois, CalHacks, TreeHacks, Hack the North, YC Hacks, and Greylock Techfair. You can also contribute to open source projects. Working on open source is an awesome way to add value to meaningful projects. Plus, you learn a lot from seeing code written by more experienced engineers. Jumping into open source for the first time can be intimidating. Two good entry points are Google Summer of Code and Sayan Chowdhury’s article on open source for beginners. Github also just released their very own open source guide. Find a cool project and dive in. You’ll get the hang of it soon enough. Research is an alternative to projects. If your school has a student research program, great! Apply asap. If it doesn’t have one, look up what research your professors are doing. If their work seems interesting, email them and ask if you can contribute. You’d be surprised at how receptive they are to eager undergrads. In the future, you can even ask your team to refer you to cutting-edge companies. Keep in mind research belongs under Experience rather than Projects on your resume. It can be tough balancing projects and school. One complaint I hear frequently is “I don’t have time to do side projects while taking classes.” I’m personally guilty of saying that from time to time. It’s tough to set aside time for projects because, unlike school, you’re not held accountable by deadlines and exams. After a day of studying, it’s tempting to choose social media or video games over your project. But if you keep putting it off, the semester will be over before you know it. To combat procrastination, force yourself to work on your project a little bit every day. Even if it’s just 15 minutes, you’ll form a habit of making continual progress. This is also why hackathons and research projects are so great. They impose external deadlines and expectations so you can’t drag your heels. Now that you have some experience, you need to put it somewhere. Creating a resume Writing a resume might seem pretty straightforward, but there are lots of nuances. After all, it’s the first thing recruiters will read about you. It’s crucial to make a good first impression. …And you need to make that impression fast. Recruiters spend an average of six seconds reviewing a resume. You heard that right. Six seconds. Almost all that time is spent on your name, companies, job titles, start/end dates, school, major, and project titles. Everything on your resume should be tailored towards helping recruiters find these key pieces of info as fast as possible. Here are some important guidelines. Easy to scan. Stick to one page. Keep it black and white if you’re not skilled at design. Colors are noisy. Stick to a standard format (chronological, no weird fonts, 10.5 to 12 pt font size, 0.5 to 1 inch margins). Standard formats are more readable by resume-parsing programs and easier to skim by recruiters. Keep it concise. Text walls discourage readers. Highlight the key points Make your name big. Highlight company names, job titles, start/end dates, school name, major, and project titles. Important content should be higher up. For a student, the order of importance is usually Education > Experience > Projects > Skills. Cut the fat. Objective and Summary are unnecessary. Descriptions should say something tangible. “Exceptional team player” doesn’t work. “Increased user conversion rates by 20%” does. People without technical background will be reading your resume, so get rid of convoluted details. Don’t neglect the details: Include the higher of your cumulative GPA and your major GPA. If they’re both less than 3.0, leave it off. Include links to a live demo or Github repo for each project. Don’t include anything you wouldn’t be comfortable answering questions about. Most people make this mistake when listing their skills. After finishing your resume, have your peers review it. Ask them to be honest and harsh. My first draft was awful compared to my tenth draft. Use online resume builders if you’re short on time. Standard Resume and CakeResume are two outstanding tools that make it a breeze to generate a handsome resume. If you don’t have a LinkedIn profile, create one. LinkedIn enables recruiters to find you and helps you maintain your professional network. Plus, you need it for the cold-emailing recruiters later. With a few projects under your belt and resume in hand, you’re ready to begin preparing for interviews. Getting battle-ready for interviews Interview problems can be separated into two buckets, behavioral questions and technical questions. You need to start practicing both at least two months before applying. Since recruiting season kicks off in August/September, summer break is a good time to begin. Behavioral questions The purpose of behavioral questions are to find out more about your background and if you actually did what you said on your resume. Don’t take the behavioral interview lightly. A poor performance can sink your chances of getting the offer. To ace behavioral questions, you need a strong answer to “Tell me about yourself” and three stories to handle all other questions. “Tell me about yourself” is the most common behavioral question you’ll get and you need to crush it. Don’t make the cardinal mistake of regurgitating your resume. Instead, tell a story. Capture the attention of the interviewer with a strong introduction. Then, transition into a commentary about your key projects and experiences. Don’t prattle on about the details — keep it simple and emphasize the outcomes. Finally, explain why you’re interested in the position. It’s tempting to talk about every single thing you did, but you’ll lose your interviewer. Keep it concise. Your answer should be one to two minutes long. Prepare three stories you can tell in response to all other behavioral questions. Typically, you’ll be asked to give examples of leadership, overcoming a challenge, or failure. Each of your three stories should show at least one of these themes. A story needs an initial summary, a problem, three to five action steps, and a final outcome. Here’s an example. Summary: Lead an unmotivated team to complete CS project Problem: Two team members didn’t do their work and wanted to drop CS Action 1: Talked to them one-on-one to understand why they’re studying CS Action 2: Told them although it’s tough now, they can succeed if they work hard Action 3: Emphasized that they’re invaluable to the rest of the team Action 4: Used google calendar to plan meetings and Trello to track progress Action 5: Held social events to bring the team closer Outcome: Finished the project and all got at least A- This story can be used to answer any question about leadership or overcoming a challenge. Now go think of your own! Not all your stories have to be about tech. For example, I always talk about how I helped my volleyball team overcome defeat. With this, you should be able to pass any behavioral interview. To learn more, read the Behavioral Questions section in Cracking the Coding Interview. Technical questions Technical questions are the essence of the tech interviewing process. Here’s a list of topics you need to know to pass technical interviews. To master these topics, use the following four resources: Cracking the Coding Interview (~2 months before applying) LeetCode (~1 month before applying) Mock interviews (~2 weeks before applying) Glassdoor (~2 days before interviewing) Cracking the Coding Interview is one of the best resources out there. Gayle Laakmann McDowell’s Cracking the Coding Interview is the quintessential tech recruiting manual. First, read the Technical Questions section. Take notes to help you remember the main ideas. As for practice questions, concentrate on the Arrays and Strings, Linked Lists, Stacks and Queues, Trees and Graphs, Objected-Oriented Design, Recursion, and Sorting sections. Also, familiarize yourself with the Bit Manipulation, Scalability, Databases, and Threads and Locks sections. If you’re having trouble with any of the topics, study the first couple pages of that section. They contain a short and sweet explanation of the topic. Attempt each question for at least 30 minutes before looking at the solution. After reading the solution, you should still implement it and test it on your own. Otherwise, you won’t fully understand the logic. Finishing CtCI should take three to four weeks of dedicated effort. LeetCode is the second resource you should tackle. It has a huge list of problems ranked by difficulty. Each problem has its own tests, time complexity requirements, and solutions. Aim to complete 30 to 50 questions and be comfortable with medium level questions before you start applying. If you do just three a day, you can finish 42 in two weeks. It’s easy to get frustrated by Leetcode at first. In the beginning, I couldn’t solve a single easy problem. I improved over time, but I still get stuck frequently on medium and hard level problems. The good thing is interviews are different from Leetcode. In an interview, you get hints if you’re stuck. Plus, deducing the correct logic is more important than writing runnable code. Although Leetcode isn’t the best simulation of real interviews, it’s phenomenal for building problem solving intuition. Mock interviews are highly effective if you do them right. The trick is emulating a real interview as closely as possible. If you’re the interviewee, be professional, ask questions, and talk out loud. If you’re the interviewer, time the interview, engage in the conversation, and write down feedback. I suggest booking a private room on campus and grinding through back-to-back interviews. Make sure the room has a big whiteboard to draw on. Take turns interviewing and being interviewed by a friend who’s also recruiting. Being able to understand the interviewer’s perspective will improve your own interviewing skills. Glassdoor is an invaluable resource for company-specific info. In most cases, you don’t need Glassdoor until a few days before your interview. Unless the company is very large, Glassdoor won’t have many specific interview questions. Glassdoor is better for learning about the company’s general interview process. Navigate to the Interviews section and filter by the position you’re applying for. Sometimes there are different labels for the same job, so look through all of them. Read candidates’ experiences and think through the interview questions they posted. You likely won’t get the same questions, but working through them will give you an idea of what to expect. Making your application stand out It’s finally time to send out applications and start seeing your hard work pay off! Recruiting season begins in August/September, but you can reach out a month or two earlier. For off-season jobs, apply at least 6 months before. First, you need a list of companies to apply to. If you’ve been following the tech industry, you should already have some companies in mind. To add to your list, check out The Breakout List, Wealthfront’s Career-Launching Companies List, and the CrunchBase Unicorn Leaderboard. For more ideas, here’s a list of 163 companies I looked at when I was recruiting. Don’t be picky about which companies to apply to. If you think the product is interesting or you’ve heard good things about the company, then apply. Worry about choosing after you get a few offers. The application process I recommend first applying and interviewing for companies you’re less interested in. This is a good way to train for future interviews of companies you want more. But don’t do too many — you don’t want to burn out. When I recruit, I try to keep the process under 3 months and not do more than 10 onsite interviews. Anything more than that, I run out of steam and my performance suffers. When you’re scheduling your interviews, spread them out. Interviews are mentally draining, so you need time to rest in between. Companies won’t mind if you ask for a week or two before starting their process. Once you’re ready to apply, use a 5-pronged approach: Referrals Emailing recruiters Career fairs Online applications This list is ordered by success rate and time commitment. For example, referrals have the highest success rate but require the most time. Referrals are the single best way to land interviews. When an employee refers someone, that’s the golden endorsement. Referrals make up for less than 10% of applications, but 20-50% of eventual hires. Ask your friends or older students to refer you. You can also ask employees for a phone chat or coffee to learn more about the company and request a referral at the end. Don’t be shy about this. If you get hired, the employee who referred you gets a bonus — it’s win-win for both of you. Cold-emailing recruiters is the next best thing to referrals. For smaller companies without a formal recruiting pipeline, reach out to an Engineering Manager instead. For even smaller companies, just email the CEO or CTO. The easiest way to get email addresses is asking your network for recruiter contacts. You need a LinkedIn account to find email addresses. Look up the companies you want to apply to on LinkedIn and filter their employees by recruiters. Next, install Hunter or Slik, which lets you get the email address from a LinkedIn profile. Hunter doesn’t like it if you try to sign up using a personal email, so use your school email. Your emails should be concise. State your interest in a position and include a summary of your background. Remember to attach your resume. To save time, make a template. You just have to change the name of the recruiter, the name of the company, and your statement of interest. If you don’t get a reply in a week, follow up. If you don’t get a reply in another week, follow up again. Career fairs get you face time with recruiters and engineers. For career fairs, check which companies are attending beforehand. Jot down the ones you’re most interested in because you might not have time to talk to all of them. Print out 10 to 20 copies of your resume to pass to recruiters. Be ready to answer questions about your experiences and projects. I recommend going early — miss class if you have to. You’ll avoid the lines and catch recruiters before they’re exhausted from chatting nonstop. Don’t feel pressured to ask recruiters questions if you don’t have any. You won’t offend anyone if you get straight to the point and ask if they have openings. After your conversation, make sure to get their emails so you can follow up later. Oh yeah, and actually follow up! Don’t let those business cards gather dust with the free t-shirts and drawstring bags. For hackathons, you’ll be targeting one company you really like instead of 10 to 20. Company sponsors will set up shop at the venue. This is your in. Before the hackathon, find the sponsoring company you want to target. When you arrive, introduce yourself to its engineers and recruiters. Use their API in your project and interact with them throughout the hackathon. On the last day, go show them your project. Then, ask about job/internship opportunities. At this point, they’ve already seen your work ethic, creativity, and interest in their company. You’re pretty much guaranteed an interview. Hackathons can function as indirect career fairs also. I know people who’ve landed interviews through talking to engineers and recruiters from sponsoring companies at hackathons. For more advice on this strategy, read Ryan Norton’s article. Online applications are the easiest way to apply. Use a shotgun approach. Most applications only ask for your resume, so it’s easy to apply to a lot of companies in one go. Intern Supply, the Easy Application List, and your school’s career website are essential for finding open positions. Most of the time, you don’t need a cover letter. But if the company makes the cover letter mandatory or asks for a short answer response, be careful. In this case, the company really cares about fit, so craft a meticulous response. I’ve been burned many times by disregarding mandatory cover letters and short answers. Take your time when writing — a hurried response will show. For applying online, I also recommend TripleByte. You first complete a coding quiz. Then, TripleByte matches you with top companies and fast-tracks you through their hiring processes. Bear in mind this resource only works for finding full-time jobs. Conquering the interview For many people, this is the most nerve-wracking part of the process, but there’s no need to be anxious. The interviewer is on your side (even if it doesn’t seem like it). Before we go any further, there’s one thing you have to keep in mind. Show enthusiasm! Enthusiasm plays a huge role in whether you get an offer. Companies these days love to talk about how much they value culture fit. What they basically mean is they want someone who’s enthusiastic about their mission and product. The truth is most candidates aren’t good at being enthusiastic. The best way to ensure you do it is preparing a list of things you like about the company in advance. When answering behavioral questions or asking questions, bring up the items on your list. Use the company’s blog and its Crunchbase profile to find things you can talk about. Now, let’s go over some best practices for technical interviews. When you first hear the problem, write it down. Then, clarify with your interviewer what you think the question is asking. Don’t assume you understood the question the first time you heard it. Next, write down a few example inputs and outputs and verify they’re correct. This gives you time to think of a solution and provides tests you can run later. If you need more time to think, don’t be afraid ask for a minute to brainstorm. It shouldn’t be too hard to devise a brute-force solution. Talk through it with your interviewer while thinking of ways you can improve it. Continue bouncing ideas off your interviewer until you come up with a better solution. Explain it to your interviewer and only start coding after they’re satisfied. While you’re working through the problem, continuously communicate your thought process. How you think is more important than the actual answer. Be outspoken, but don’t blab on endlessly. Take pauses to think and let the interviewer make suggestions. Don’t space out or look distant. You should direct your full attention towards the interviewer to engage them. If they’re engaged, they’ll give you positive signals if you’re on track and hints if you’re not. What’s more, they’ll be emotionally invested in you and want you to succeed. At the end of the interview, you’ll get time to ask questions. Remember an interview is two-way. Don’t just ask questions you think the interviewer will like to hear. Ask questions you actually want to know the answers to. I suggest asking about personal experiences to get more authentic answers. Remember these tips and you’ll be ready to ace technical interviews. The average interview process looks like this: Coding challenge > Recruiter chat > Phone interview > Onsite interview The process varies by company. Sometimes the recruiter chat will be first. Sometimes you won’t have a coding challenge. But the general structure is similar. The coding challenge is a straightforward test. It’s usually hosted on Hackerrank. I suggest doing a couple of questions on it ahead of time to get familiar with the format. There’s no trick to the coding challenge. Pass as many tests as you can. With enough practice on Leetcode, this should be a walk in the park. The recruiter chat is an informal conversation. It’s usually for setting up the phone interview and answering any questions you have. You might get one or two behavioral questions. Once in a while, you might get trivia-esque technical questions like “Explain how a hashmap works.” Candidates rarely get rejected at this stage (although I’ve managed to do just that a few times). Treat this as a chance to learn more about the company. Ask high-level questions — recruiters generally don’t know technical details. Make sure to ask about the format of the rest of the interview process so you aren’t caught off guard by anything. The phone interview stage is one to two rounds of technical interviews. Sometimes you’ll do a video chat instead of a phone call. You’ll typically code out the answer in a shared editor like Collabedit. If the connection is bad or you’re having trouble understanding the interviewer, speak up. You’re not going to get docked points, so don’t try to tough it through. The onsite interview is three to six rounds of interviews with a lunch in between. A day of back-to-back interviews is exhausting — get enough sleep beforehand! Onsite interviews are mostly technical, but some companies mix in behavioral and design rounds. The lunch is for you to learn more about the company, so relax a little. During the interview, use the whiteboard to your advantage. Leave plenty of space on the right side and between the lines so you have room to make edits. After the interview, don’t dwell on it. Thinking about it isn’t going to change the final result. Treat it as if you were rejected and continue applying and practicing. Evaluating the offer Congratulations! You got an offer! Give yourself a big pat on the back — you earned it. But your work isn’t done yet. First, thank your recruiter and re-express your enthusiasm for the company. Then, ask for your offer in writing. It’s time to negotiate. A job offer isn’t an act of generosity — it’s a proposal to strike a deal. Naturally, a deal involves negotiation. I’m not going to elaborate too much on negotiation tactics. Just read Haseeb Qureshi’s killer guide on negotiation. Bear in mind some offers are non-negotiable, but it never hurts to try. Avoid unpaid jobs. In 90% of cases, it’s not worth it. I’m all for prioritizing learning over pay, but at least work for a company that values you enough to pay you. If you have more than one offer, congrats! You’re awesome. But now you have to make a decision. Choosing which offer to accept is a nice problem to have. The best offer depends on the specific candidate, but here’s one universal suggestion I hope serves you well. Make a list of 10 professional and personal goals you want to achieve in the next 10 years. It could be anything, like paying off student loans, founding a startup, or mastering a new hobby. Choose the job that brings you closest to these goals. Here are a couple more tips to remember: Your future manager is vital to your career growth. Find a great mentor who will double as your champion. Do internships at different companies to gain broader experiences. You’ll learn more and expand professional network. Optimize for learning and growth over pay, unless the pay is really bad. Work at one brand name company. It’ll make recruiting in the future easier, but know that it’s not the end of the world if you don’t have one. Choice of programming language doesn’t matter. What matters is learning good engineering practices and how to work in a team. Choose an engineering-first company with a software/hardware product. Don’t forget about passion. It’s an amazing feeling building a product you believe in. Conclusion This brings us to the end of this guide. I hope that with this, you’ll be much better prepared than I was when starting a career in tech. In the beginning, getting an offer might seem impossible, but the key is treating it as a series of milestones rather than one enormous task. If you make a little bit of progress every day, you’ll be there before you know it! When you do get that dream job, don’t forget to give back. Share your experiences and extend referrals. Pass on the love, and we’ll all fly higher.

Panel: Charles Max Wood Guest: David Hemmat This week on My Ruby Story, Charles talks to David Hemmat about his educational background, career choices, and suggestions for developers. David is a web developer who works mainly with Ruby on Rails. In the past few years, David has done work for a number of clients including Condé Nast, Six Red Marbles, ShopKeep, and Couplewise. Currently, David is working on a number of personal and professional development projects. In particular, we dive pretty deep on: David’s background How did you get into programming? David’s first job was being a software developer in the Dominican Republic. Ruby on Rails Consulting and referrals Contract work and being a freelancer Upwork Freelancer Reddit Is there anything that you have done with Ruby or in the community that you are particularly proud of? Talks about Ruby on Rails What are you working on now? The company and Blue Coding. They are interested in hiring a Ruby on Rails developer. If you are interested in this position e-mail at: hr@bluecoding.com or info@bluecoding.com. Hiring Finding someone you can trust to lead the charge. Links: Fresh Books Upwork Freelancer Reddit Digital Ocean CacheFly Blue Coding David R. Hemmat’s Website David’s E-mail: david@davidhemmat.com Medium Account for David Hemmat Sponsors: Digital Ocean Picks: David Rails Tutorial by Michael Hartl Codecademy Rails Casts Platzi Charles Framework Summit Ruby Hack Microsoft Build Podcast Movement

Panel: Charles Max Wood Guest: David Hemmat This week on My Ruby Story, Charles talks to David Hemmat about his educational background, career choices, and suggestions for developers. David is a web developer who works mainly with Ruby on Rails. In the past few years, David has done work for a number of clients including Condé Nast, Six Red Marbles, ShopKeep, and Couplewise. Currently, David is working on a number of personal and professional development projects. In particular, we dive pretty deep on: David’s background How did you get into programming? David’s first job was being a software developer in the Dominican Republic. Ruby on Rails Consulting and referrals Contract work and being a freelancer Upwork Freelancer Reddit Is there anything that you have done with Ruby or in the community that you are particularly proud of? Talks about Ruby on Rails What are you working on now? The company and Blue Coding. They are interested in hiring a Ruby on Rails developer. If you are interested in this position e-mail at: hr@bluecoding.com or info@bluecoding.com. Hiring Finding someone you can trust to lead the charge. Links: Fresh Books Upwork Freelancer Reddit Digital Ocean CacheFly Blue Coding David R. Hemmat’s Website David’s E-mail: david@davidhemmat.com Medium Account for David Hemmat Sponsors: Digital Ocean Picks: David Rails Tutorial by Michael Hartl Codecademy Rails Casts Platzi Charles Framework Summit Ruby Hack Microsoft Build Podcast Movement

Panel: Charles Max Wood Guest: David Hemmat This week on My Ruby Story, Charles talks to David Hemmat about his educational background, career choices, and suggestions for developers. David is a web developer who works mainly with Ruby on Rails. In the past few years, David has done work for a number of clients including Condé Nast, Six Red Marbles, ShopKeep, and Couplewise. Currently, David is working on a number of personal and professional development projects. In particular, we dive pretty deep on: David’s background How did you get into programming? David’s first job was being a software developer in the Dominican Republic. Ruby on Rails Consulting and referrals Contract work and being a freelancer Upwork Freelancer Reddit Is there anything that you have done with Ruby or in the community that you are particularly proud of? Talks about Ruby on Rails What are you working on now? The company and Blue Coding. They are interested in hiring a Ruby on Rails developer. If you are interested in this position e-mail at: hr@bluecoding.com or info@bluecoding.com. Hiring Finding someone you can trust to lead the charge. Links: Fresh Books Upwork Freelancer Reddit Digital Ocean CacheFly Blue Coding David R. Hemmat’s Website David’s E-mail: david@davidhemmat.com Medium Account for David Hemmat Sponsors: Digital Ocean Picks: David Rails Tutorial by Michael Hartl Codecademy Rails Casts Platzi Charles Framework Summit Ruby Hack Microsoft Build Podcast Movement

Show Notes und Links Projekt ANA Tag 2 final Rails Girls App Tutorial Scaffold Gerüst für die Ressource bauen Tutorial englische Begriffe für Ressourcen verwenden (Einzahl-, Mehrzahlbildung) Struktur in ANA: ein Projekt (project) hat n Anforderungen (requirement) => 1:n Relation project has_many requirements requirement belongs_to project MVC (model, view, control): Ruby on Rails Tutorial zu MVC Ressource project model: project.rb views: edit.html.erb, index.html.erb, new.html.erb, show.html.erb controller: projects_controller.rb enthält Methoden index, show, new, edit, create Datenbank rake db:migrate Views html.erb Ruby code in Klammern Aufruf der Ruby Funktion Rückgabewert der Ruby Funktion soll ausgegeben werden Start des Servers rails s http://localhost:3000/projects http://localhost:3000/requirements Datenbank SQlite Wikipedia Artikel, Homepage Bootstrap getbootstrap HTML, CSS, und JS framework Responsive Design Wikipedia Internationalisieren und Lokalisieren Wikipedia internationalization Numeronym i18n localization Numeronym l10n pdf-Dokument erzeugen: Prawn prawn prawn-rails Railscast Episode Prawn by Example DSL - domain specific language Wikipedia Rapid prototyping, iterative Entwicklung VHDL JIRA Ticketsystem

Show Notes und Links Rails Girls Rails Girls Vienna Wiener Installationsanleitung Wiener Tutorial Buch Head First Ruby Leseprobe Autor interviewt beim letzten Ruby on Rails Podcast Episode 216 Buch Hello Ruby von Linda Liukas Buch Agile Web Development with Rails von Sam Ruby Buch The Ruby on Rails Tutorial von Michael Hartl Buch Programming Ruby 1.9 & 2.0 (4th edition) aka The Pickaxe Book von Dave Thomas und Chad Fowler Sektor 5 Ruby Ruby on Rails Javascript Bootstrap MVC Konzept DSL Domainspecific Language Compiler Heroku Webseite, Heroku bei Wikipedia Railshoster Nitrous Sketchnotes

本期由 Terry 和 Daniel 主持，邀请到了 Andor Chen 以及 Rei 一起聊聊技术类书籍的翻译以及自出版的相关，包括现状，工具，平台，方法等一系列问题。 Ruby on Rails 教程 How to build a blog engine in 15 minutes with ruby on rails Creative Commons The Ruby on Rails Tutorial Michael Hartl Web开发敏捷之道 Ruby程序设计语言 burr Leanpub 豆瓣阅读 CoffeeScript小书 J·K·罗琳 图灵社区 SelfStore Stripe Sphinx Doc AsciiDoc Atlas Design Code GitBook softcover Special Guests: Andor Chen and Rei.

时光如梭，我们已经迎来了 Teahour.FM 的一周岁生日。 在这一期特别节目里，我们聊了很多有意思的话题，在此先卖一个关子。 节目中提到的“我最喜欢的Teahour.FM节目评选”的调查表地址是：https://jinshuju.net/f/u7ycDz 填写调查表的听众就相当于自动参加了我们的抽奖送大礼活动, 我们期待获得你的反馈。 奖品详情： Knewone 提供的 3个 Yeelight Blue 智能灯泡 Andor Chen 提供的 3本 Ruby on Rails Tutorial 中文版电子书 XDite 提供的3本 Rails 101 电子书以及 3份一年期的Logdown高级帐号。 貔貅交易所 提供的3个比特币红包 云梯 提供的3个免费 VPN 帐号(可使用3个月) AngularJS Backbone.js Marionette SJR batman.js Ember Spine 37Signals Intridea fengche.co RubyConf China Tealeaf Academy 三温暖 Logdown Rails Rumble COOKPAD Hackathon GDG 大秦帝国 凯恩斯大战哈耶克 刀剑神域 GEB 牌局心理学 Crush It! SAAS 简书 七牛 Seven Databases in Seven Weeks Special Guest: xdite.

  Single Table Inheritance is a great way to handle related models that descend from the same class. The classic example is a Car class with Ford, Chevy, and Honda subclasses. This Ruby on Rails Tutorial provides an example and explains how Rails puts all of the information in the same database table and allows you to query things from both the superclass and subclass. Download 59.5 MB Download (iPod and iPhone) 36.3 MB

  Single Table Inheritance is a great way to handle related models that descend from the same class. The classic example is a Car class with Ford, Chevy, and Honda subclasses. This Ruby on Rails Tutorial provides an example and explains how Rails puts all of the information in the same database table and allows you to query things from both the superclass and subclass. Download 59.5 MB Download (iPod and iPhone) 36.3 MB

Michael Hartl put together a free rails tutorial online. We met at RubyConf and determined to talk about his tutorials. His path into Rails development has been interesting to listen to. Similarly, his thoughts on business are inspiring. We talked about a great way to support Teach Me To Code. And that is by purchasing his videos and book here. I don't usually promote products, but I think this one is a terrific one and I hate asking for money in return for nothing, so in this case you get some great videos and a book! Download this episode