From d95fc5ca9e6a9c28894514b77e77b6b0eb58fbe9 Mon Sep 17 00:00:00 2001 From: Mitja Felicijan Date: Thu, 26 Jan 2023 11:36:44 +0100 Subject: A bunch of theme changes and removal of Cactus comments --- content/posts/2015-11-10-software-development-pitfalls.md | 11 ----------- 1 file changed, 11 deletions(-) (limited to 'content/posts/2015-11-10-software-development-pitfalls.md') diff --git a/content/posts/2015-11-10-software-development-pitfalls.md b/content/posts/2015-11-10-software-development-pitfalls.md index c5d243a..ec7fcb8 100755 --- a/content/posts/2015-11-10-software-development-pitfalls.md +++ b/content/posts/2015-11-10-software-development-pitfalls.md @@ -5,17 +5,6 @@ date: 2015-11-10 draft: false --- -**Table of contents** - -1. [Ping emails](#ping-emails) -2. [Everybody is a project manager](#everybody-is-a-project-manager) -3. [We are never wrong](#we-are-never-wrong) -4. [Micromanaging](#micromanaging) -5. [Human contact — no need for it!](#human-contact--no-need-for-it) -6. [MVP is killing innovation](#mvp-is-killing-innovation) -7. [Pressure wasteland](#pressure-wasteland) -8. [Conclusion](#conclusion) - Over the years I had the privilege to work on some very excited projects both in software development field and also in electronics field and every experience taught me some invaluable lessons about how NOT TO approach development. And through this post I will try to point out some absurd, outdated techniques I find the most annoying and damaging during a development cycle. There will be swearing because this topic really gets on my nerves and I never coherently tried to explain them in writing. So if I get heated up, please bear with me. As new methods of project management are emerging, underlying processes still stay old and outdated. This is mainly because we as people are unable to completely shift away from these approaches. -- cgit v1.2.3