I've been writing posts about Rails on http://www.justinweiss.com for a little over a year now, and I've heard from so many people that are excited about Rails, that have bought all kinds of videos and tutorials and courses and bootcamps, but just can't build their own projects.
So, I wrote a book to help. It's not so much a Rails tutorial as it is a guide to programming, project management, and motivation, using Rails as a medium.
I know I'm asking too much, but is it possible to get a hand on the chapter on testing only? I have been reading on tests, but most of the time I feel quiet lost. I'm afraid it might be the same here too.
* Bad estimates. When people are too aggressive with their estimates and miss them, it derails everyone that was depending on that team's stuff being done at a particular time. It causes blockages that cost way more than an over-estimate would have reserved as buffer time.
* Getting distracted. Dev should work really closely with design and PDM to get things done, but if Design / PDM has already moved on to the next project, it's distracting for everyone when they have to get pulled back in. Then, you have multitasking, and blockages, and stuff doesn't get done as smoothly as it should.
Feel free to contact me directly: email@example.com, and let me know you came from HN.
We're looking for a Web application developer to help shape the way people connect with the lawyers who will make a difference in their lives.
At Avvo, you'll get to work with smart, passionate people in small, focused, cross-discipline teams building Web, iOS, and Android applications. You'll take a product from conception to completion, shaping its direction the whole way. You'll have the flexibility to build each project in the way you think is best, using the best tools and technologies. You'll own the development of the project from the front end to the database layer.
We use whatever tools and technologies we think are best for the situation, including Ruby, Rails, Redis, Solr, Git, Chef, SASS/Compass, neo4j, Sinatra, Objective-C, and EC2.
We're looking for:
* Passion for building software. Huge bonus points if you've built or maintained open source software or side projects. (Send us your GitHub profile!)
* The ability to identify and institute software best practices throughout a team and organization.
* Someone who can provide technical leadership. You should be comfortable mentoring new developers, sharing knowledge across the team, driving a new project from the beginning, and thinking about how projects and teams will interact on a strategic level.
* Experience working on a large software project over several years. You should be able to reliably add features to shipped code, identify and reduce technical debt, participate in the product design process, estimate accurately, and provide quality feedback to the rest of the team.
* Enthusiasm for learning about new technologies and sharing them with your coworkers. We've seen huge productivity improvements from using new tech, so a keen eye for cool new stuff is a plus.
* Collaboration with other disciplines - you'll be working closely with designers and PMs, and it takes everyone's skills to build something remarkable.
* A strong desire to build the best product for your customers, no matter how long it takes to get there.
We'll give you:
* A competitive salary and generous stock options.
* The machine of your choice.
* Three weeks of vacation each year.
* Paid conference expenses, books, and classes.
* A great working environment in a beautiful building in the International District, on the bus and light rail lines, walkable from Belltown, Downtown, Capitol Hill, and Pioneer Square.
* A free ORCA card for all your public transportation needs.
* A strong work / life balance - we'll ask a lot of you while you're here, but we're not going to make you work 10-hour days.
Besides all this, I've been here for almost seven years and I still love it. Devs really get a lot of freedom and autonomy here, and we get to work really closely with other disciplines like product, design, and marketing. I love that, since we all get to learn from each other. And we ship code all the time.
This is such a key point. I launched a startup in 2003 that was successful, and did it for four years. But at the end of that project I knew that if I had to go back to using a LAMP stack, I was out of the web development industry. Learning Rails brought back my enthusiasm and love for programming.
When I was still at MS, a lot of these kind of bugs didn't get fixed -- the code checking against the old (smaller) path size would often not be owned by anyone anymore, and nobody wanted to touch it (because that would make them the new owner).
I've seen this problem when using @font-face generators that remove font hinting to save space. Last time I used FontSquirrel's generator, I had to specifically unset the option to remove hinting in order to get the fonts to look right on Chrome on Windows.