Group items tagged

"Regardless of software process management type (waterfall, scrum, iterative etc.), there are some main rules which should be considered about software process management."

"But even in today's SW industry, there does not seem to be much of an expectation from SW professionals that we should have the 'capability/tools to build our own tools' that do much of the project work for us. I am not talking about the simple automation, things like rename/refactor or autocorrect, or intellisense and all that, I am talking about the kind of automation and tooling that writes or deploys software for us and saves hours, days and weeks of our time from handcrafting software solutions from scratch again."

The Microsoft .NET platform, originally introduced in 2002, is mature and it provides developers with great options for creating software that can meet the requirements of any project. With many options, though, it can be difficult for today's .NET developer to choose the correct .NET technologies for a project. Addressing this problem, Telerik has assembled its senior technical leaders to produce the Microsoft Platform Guidance 2012. This document attempts to provide prescriptive guidance for .NET developers trying to determine the best .NET technologies to use for specific software challenges.

"I'm often asked advice on how to be a better programmer. [..] I've been giving this quite a bit of thought lately and I've come up with what I think are the most important and timeless skills that a software developer can attain which will give them the best career opportunities and make them the most effective."

"Even with the rise of cloud computing, the world still revolves around servers. That won't last, though. Cloud apps are moving into a serverless world, and that will big implications for the creation and distribution of software and applications."

An interesting read: legacy software is there and an important part of our lives, but maintaining it may pose a challenge. The author argues that agile methods may even be more beneficial to teams maintaining legacy code than to teams that build brand new products from scratch.

"Dependencies are nearly unavoidable for non-trivial software projects. These can be large dependencies, such as web frameworks and databases, or smaller decisions, such as pagination helpers or simple math libraries. The inevitable inclusion of these dependencies, however, is not an excuse to shape the solutions of your system around what you do not own. Instead, there ought to be an emphasis on finding the right fit and then owning the way dependencies interface with your system."

"One of the things I like most about working in software development is the fact the for the most part you get to work with fairly intelligent people. I've always wondered why so many smart people manage their career so poorly."

"Agile software development with a focus on effective Scrum and proven team practices."

"The singleton pattern is one of the best-known patterns in software engineering. Essentially, a singleton is a class which only allows a single instance of itself to be created, and usually gives simple access to that instance."

"The book Growing Object Oriented Software, Guided by Tests states that you should never mock interfaces that you don't own. When I read that it caught me off guard. After all faking third party libraries that talk to databases or the network is the primary use case of a mock object right?"

A series of six articles desribing each of the five SOLID principles used for dependency management in object-oriented design and programming. When followed, these principles can enhance the maintainability of software.

Perhaps interesting after today's meeting...

The goal of this blog entry is to explain the basic concepts of Scrum in less than five minutes. You learn how Scrum can help a team of developers to successfully complete a complex software project.

Really, a few time management principles can do our life successful and improve software and web development to profitable and fascinating levels.

The Joel Test: 12 Steps to Better Code Have you ever heard of SEMA? It's a fairly esoteric system for measuring how good a software team is. No, wait! Don't follow that link! It will take you about six years just to understand that stuff.

I like the analogy "Software development, however, is more like rowing."