howto software project management complexity UNIX KISS automated testing
art of #psychological good #motivating #communication is #CRUCIAL [+] first mention what is #good [+ist] what works [+] what is #positive then the [-] #catastrophes and never ending (?) computer #problems, so u may criticize this video in a comment BUT you will have to say something [+] positive first
everyone makes #mistakes = have the best possible self #error #correction before #customer is crucial!!!
o it all starts with a #CEO or other steak holder wanting to have a certain type of #software with certain #functionality, so please define what functions until what time-frame should be working?
so define what does #intime and #inbudget mean for the #project?
with a world full of never ending computer problems: #socialskills and respecting #psychology is #essentical, so watch your #language, always communicate [+] what is good [+] what works [+] what is positive then what does not work, where is the problem? (there will always be problems)
o hence #UNIX #KISS is crucial (keep it as simple as possible, make a lot of simple programs that do one thing, but does it well (well tested! X-D) and combine them (modules))
o use-case-test-dokumentation so essentiell! (write down how to test each function, then automate or semi automate the test!!! test with every new version)
oo humans make mistakes and even if someone tells you computers don't make mistakes, this is very wrong, as humans make mistakes and the more complex the problem the more mistakes... hence u can expect your computer and your os to contain billions of mistakes... but it workes mostly "good enough" for this or that task, in order for it to work "good enough" hardware and software quality needs to be ensured.
it's no use having the best hardware and faulty software
also it's no use having faulty hardware and running high quality software on it
o 1x dev + simple program (#UNIX #KISS) eye-ball it ok
oo 10x devs + complexity = amount of functions increases = likelyhood for errors: mit vielen funktionen = no you are not god u need to write a test for every function and every possible thinkable scenario or you will end up beeing hated like micro$oft for catastrophic closed source software quality = software that just does not work, not even seamlessly (full of errors)
good luck all involved