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 work in prototypically four-week iterations, with quality engineers and softwaredevelopers working in close collaboration. This finally bit us after a four month stint of development blew through its testing schedule by a factor of four: two scheduled weeks turned into two months before the product reached stability.
Keep in mind that some of the development tools like WordPress themes and Magento framework aren’t free. Building a software product, the massive part of your budget is the developers’ salary. To calculate precisely how much you need to spend on that, analyze the following factors: Developers’ seniority.
Bizosys Technologies, a Bangalore, India based softwareengineering company was founded in 2009. Guttula, Bizosys' CEO, and Karana founded the company with the goal to "simplify softwaredevelopment." Toward that end, they have created two products. You can also read more about Bizosys on the 1M/1M Incubation Radar today.
Present at the Creation It was early 1991 and Apple’s softwaredevelopment team was hard at work on QuickTime , the first multimedia framework for a computer. And, of course, Adobe said, “Oh, by the way, you don’t mind if the softwareengineer comes with us, do you?” Adobe renamed ReelTime to Adobe Premiere.
These are highly-skilled people that make up critical parts of your softwaredevelopment teams. And there’s another reason, also technology-driven, why boundaryless teams are possible now — the democratization of education for softwareengineers. Reason Three: The Democratization of Education.
Frequency of buzzwords (programming languages, frameworks, OSes, software packages, etc.). In the second, the candidate is using some standard industry lingo as a crutch — what he said could easily be applied to pretty much any softwareengineering position. Powered by Reverie Framework. Resume length.
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.
Now that we’ve built out our first service to prove out the framework, we want to start allowing teams to build lots of new services along with the additional infrastructure pieces needed to support these new services. At its heart, DDD outlines an approach to softwaredevelopment with a set of principals and tools.
they are easy to write, frameworks have been chosen, examples exist, etc. If you are introducing unit tests for the first time and trying to limit end to end tests, make sure that the team is set up for success with unit tests?—?they If a team is told to write unit tests but doesn’t know how, they likely won’t.
they are easy to write, frameworks have been chosen, examples exist, etc. If you are introducing unit tests for the first time and trying to limit end to end tests, make sure that the team is set up for success with unit tests?—?they If a team is told to write unit tests but doesn’t know how, they likely won’t.
Use frameworks in interviews to explain your qualifications and show your thought-processes. I wasn’t a very good softwaredeveloper, and I was only modestly capable as a UX designer, but I learned enough to recognize clean code and effective, inspiring design when I saw it. I learned that softwareengineers?—?or
What existing systems will we leverage, what programming languages, softwaredevelopment methodologies, web application frameworks, revision control systems, etc.? How can we address this risk? What technology research is required? What technologies will we use? What other kinds of systems will we likely need? Accounting?
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. It’s an *freaking open source*.net net implementation. Checkout [link].net March 25, 2011 at 3:23 pm.
I do disagree about two other points: First, this isn't the "quora rockstar engineer" perspective. It's my perspective as well and I'm not a softwareengineer let alone a rockstar. I mean a rockstar developer, you need a reliable, steady, bull-like technical partner.
In this post, we’re sharing a build vs. buy framework to help you consider the opportunity costs and make an informed decision on whether to buy software off the shelf or build a custom solution. How to decide when to build versus buy: A decision framework. Risks vary based on whether you develop or purchase software.
Weve built Sandcastle specifically for an entrepreneur with an idea, who is not a developer. Sandcastle is a softwaredevelopment service for entrepreneurs. Nothing essential that I disagree with you in your post, but when read by other people with minimal softwareengineering experience, they can have too high expectations.
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