Remove Article Remove Software Engineering Remove Software Review
article thumbnail

Lessons Learned: Continuous integration step-by-step

Startup Lessons Learned

Lessons Learned by Eric Ries Monday, December 8, 2008 Continuous integration step-by-step Lets start with the basics: Martin Fowlers original article lays out the mechanics of how to set up a CI server and the essential rules to follow while doing it. It also happens whenever you have code that is checked-in, but not yet deployed anywhere.

article thumbnail

Why The Future Of US High-Tech Is Bright

YoungUpstarts

Take software developers as an example. Coming up with an idea for a new piece of software, developing it, and testing it is expensive. Yet once the software is coded, it can be reproduced millions of times at virtually no cost. This article was first posted in The Financialist.].

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

Trending Sources

article thumbnail

Programmer Competency Matrix

www.starling-software.com

Able to recognize and code dynamic programming solutions, good knowledge of graph algorithms, good knowledge of numerical computation algorithms, able to identify NP problems etc. Understands what assembly code is and how things work at the hardware level. Software Engineering. Some knowledge of virtual memory and paging.

article thumbnail

Verified Data Will Prevent “Fake It Til You Make It”

Hunter Walker

” My personal experience with this phenomena is when I find myself slipping into a mode where the pleasure comes from finishing the book/movie/article/etc rather than actually absorbing and enjoying it. A basic example is you must have downloaded an Apple iOS app before being able to review it.

API 128
article thumbnail

Revisiting the Software Design Manifesto (and what's changed since.

Startup Lessons Learned

Lessons Learned by Eric Ries Saturday, August 8, 2009 Revisiting the Software Design Manifesto (and whats changed since then) My recent article on technical debt and its positive uses generated a fair bit of controversy. The same might be said of good software. Here we have the beginnings of a theory of design for software.

article thumbnail

Lessons Learned: Stevey's Blog Rants: Good Agile, Bad Agile

Startup Lessons Learned

Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective. They take things like unit testing, design documents and code reviews more seriously than any other company Ive even heard about. Dates are irrelevant. Focus on launching.

Agile 76
article thumbnail

Google Engineer: How We Interview, How I’d Beat Us for Talent, & How Non-Technical Founders Should Approach Devs

View from Seed

Saurya Velagapudi is a senior software engineer at Google, based in their Cambridge, Mass., I’ve also tried to highlight some of the main lessons we can learn from Saurya throughout the article.). Google tries to cover a variety of topics, from the bare minimum, “Can you code?”