![]() Buy low and sell high - New languages, tech, frameworks etc.Manage risk - Spread your time/money into a good diversify.Invest regularly - Internalize this habit, learning without interruption.Knowledge portfolio - Knowledge is an expiring asset User decide whether you have produced a good enough software.Good enough != sloppy poorly produced code.Decisions are subjective (Intuitions) or objective (Facts)?.Review and keep you eyes on what's happening around you.In this way we shown them a glimpse of the future.įrog soup - It is to remember the big picture Then we can w8 until they start to put X there. We can do a trick, Create what you can with your resources and when they ask you "is that all?" you will answer them "It will be better if X be there". Those things are called "start-up fatigue". Meets and committees = guard to save their resources = delays. ![]() Ask budget = need to be approved = delay.Definition of fire in software development process: deadlines, release dates, trade show demos, etc.But as far as it is possible they do not inflict unnecessary damage to properties. The fire department's first priority is to put out fire.Neglect accelerates the software rot faster anything else.Negative thoughts can spread among the team. So more windows brakes and this is contagious. Broken Window: A broken window instills in the inhabitant of a property the feel of abandonment.But some projects somehow tackle issues, setbacks. A project can get decay even with best-laid plans and best peoples.As you may know Entropy means that a systems go toward maximum disorder.This is all about software rot - or in a more soft term: "technical debt". ![]() ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |