Remove Blog Remove Software Engineering Remove Software Review
article thumbnail

Technical Advisors: Every Startup Needs One

TechEmpower

They look at the code produced on a regular basis to ensure that it’s high quality and right for you. Specifically, they pay attention to: Is our code scalable and extensible? Do you have access to and ownership of the source code? Are developers following best practices in their code and life cycle?

article thumbnail

Lessons Learned: Continuous integration step-by-step

Startup Lessons Learned

Integration risk is the term I use to describe the costs of having code sitting on some, but not all, developers machines. It happens whenever youre writing code on your own machine, or you have a team working on a branch. It also happens whenever you have code that is checked-in, but not yet deployed anywhere.

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

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

Startup Lessons Learned

Lessons Learned by Eric Ries Thursday, November 6, 2008 Steveys Blog Rants: Good Agile, Bad Agile I thought Id share an interesting post from someone with a decidedly anti-agile point of view. Steveys Blog Rants: Good Agile, Bad Agile : "Google is an exceptionally disciplined company, from a software-engineering perspective.

Agile 76
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

Case Study: Lean UX at work

Startup Lessons Learned

Jeff keeps a blog here ( www.jeffgothelf.com/blog ) with tweets available at @jboogie ( www.twitter.com/jboogie ). Demos have become our design reviews.” The conversation around this sketch provides enough directional insight for the rest of the team to voice any concerns, to begin the estimation process and to start coding.

Lean 165
article thumbnail

Follow This Six-Point Checklist To Strengthen Employee Onboarding

YoungUpstarts

In fact, according to the Harvard Business Review , up to 20% of staff turnover occurs within the first 45 days of employment. Whether it’s an inactive email address, a project management software glitch, or a cracked computer screen, etc., They’ll also adhere to the other five steps provided throughout this blog.

Employee 165
article thumbnail

3 Things to Consider When Staffing a Software Development Project

mashable.com

Brett Miller is the president of Custom Software by Preston (CSP). For more than 10 years CSP has impressed clients with highly effective software solutions and teams of multi-talented software engineers. I'd approached Advanced Millennium Technologies, to develop our ERP software, last September.