This site uses cookies to improve your experience. To help us insure we adhere to various privacy regulations, please select your country/region of residence. If you do not select a country, we will assume you are from the United States. Select your Cookie Settings or view our Privacy Policy and Terms of Use.
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Used for the proper function of the website
Used for monitoring website traffic and interactions
Cookie Settings
Cookies and similar technologies are used on this website for proper function of the website, for tracking performance analytics and for marketing purposes. We and some of our third-party providers may use cookie data for various purposes. Please review the cookie settings below and choose your preference.
Strictly Necessary: Used for the proper function of the website
Performance/Analytics: Used for monitoring website traffic and interactions
As I mention in Symptoms of a Weak Development Team , the number one reason I get calls relates to an old softwareengineering adage: The first 90% of a project takes 90% of the time. But they are having a tough time getting it all the way done. The last 10% takes the other 90%.
As noted in Symptoms of a Weak Development Team , this is a symptom of the old softwareengineering adage: The first 90% of a project takes 90% of the time. Then, a month later, the product is still 90% done. And six weeks later – 90% again! The last 10% takes the other 90%.
We think teaching teams a formal methodology around the Lean Framework (Business Model design, Customer Development and AgileEngineering) is a natural evolution of how successful incubators/accelerators will build startups. Here’s the story of one such team; Jonathan Wylie, Lakshmi Shivalingaiah and the Evoke team.
One good example is the way in which we''ve adjusted the length of different phases of our agile sprints. We don''t follow a set agile methodology, but rather follow a more home-grown, minimal version of various approaches. Week 0 - New Feature 1 - Softwareengineers are busy building brand new features.
Use Solid Agile Process for Estimating Development Timeline. Almost every softwareengineer I've ever worked with is irrational in how fast they believe they can build software. At my last startup we eventually started using a process called "scrum," which is basically a framework for managing agileengineering projects.
I thought a good place to start was with the origins of the idea that "software design" should be considered a discipline in its own right, on par with computer science, softwareengineering, and computer programming. Here we have the beginnings of a theory of design for software. But what about Commodity? Expo SF (May.
The presentation was on outsourcing generally, not just softwareengineering and the audience was very early stage companies (some yet to be founded). We tried to provide a framework for startups to think about what activities should be outsourced and why. link] fnazeeri I’ve seen it work (and not).
Then we paired it with a cool icon that represents wisdom and agility, Owl. Mike is a softwareengineer and very familiar with a popular web development framework named Django. I am a pianist and love jazz and classical music. Django represents my love for music and Mike’s passion for coding.
So much of web development in the last few years hasn’t been because of sudden blasts of advancement the previous 15+ years didn’t make (examples: new libraries and frameworks every other day, new methods for doing stuff surfacing every two seconds and becoming trendy, so on).
net is the only framework in which you can build an app for all the major mobile operating systems (iphone, android, wp7). First of all,NET is a “framework”, not a “language” as you have said in your post. They use the MVC framework, which gets almost entirely out of your way. net implementation.
But what I think was hard, and it was something he couldnt consider was that it would be harder to find a *maintaining* programmer, and how much it would cost to run the software, because of technical details he didnt understand. So, while your post is a good summary (of things that cant be learned quickly. I liked it through #1-#5.
We organize all of the trending information in your field so you don't have to. Join 5,000+ users and stay up to date on the latest articles your peers are reading.
You know about us, now we want to get to know you!
Let's personalize your content
Let's get even more personalized
We recognize your account from another site in our network, please click 'Send Email' below to continue with verifying your account and setting a password.
Let's personalize your content