18 \ November 2018 \ http://www.phparch.comHow to Knock Down Any Project in Ten Steps- Burnout
What one programmer can do in one month, two
programmers can do in two months.- Fred Brooks
Burnout is an emotional state that manifests itself in many
ways, such as lack of motivation and self-confidence, a sense
of helplessness, anxiety, depression, and even deterioration
in physical health. The reasons for this state can be many,
including long working hours, constant stress, pressure from
the work environment, and lack of sleep. A worker in a state
of burnout is not fully productive and useful for the rest
of the team and the project itself. But these are tiny things
considering the physical and mental health of such a person
is put at risk. A situation in which more and more people feel
burnt out may not so much lead to the collapse of the project,
but it is dangerous for people in the first place. It is people
who need to be cared for first, and the project should wait.
Prolonged burn-out is very dangerous to health. In such
a case, you should talk to a psychologist, identify the source
and work out together how to deal with the problem. Mental
health is as important as physical health, and there is nothing
wrong if you seek help from a specialist.Summary
I have described above the 10 most common, in my opin-
ion, reasons why IT projects fail. This is my experience based
on ten years of creating web applications. Some of them you
certainly recognize, while others may be new. I sincerely hope
the awareness of the frequent causes of failures will allow you
to notice them in advance in your own environment. I hope
that within your team you will be able to avoid these pitfalls
and lead further projects to full success.Paweł Lewtak is developer with 10 years
of experience with web-based applications.
He created them from scratch from analysis
and writing specifications up to deployment
on production. He is a big fan of continuous
learning and continuous improvement.
@pawel_lewtakRelated Reading
- Building Software that Lasts by Susanne Moog. October
2017.
https://www.phparch.com/magazine/2017-2/october/ - The Dev Lead Trenches: Simple Project Management
by Chris Tankersley. November 2017.
https://www.phparch.com/magazine/2017-2/november/ - finally{}: On the Creativity of Programmers
by Eli White. April 2018.
https://www.phparch.com/magazine/2018-2/april/
php[architect] Books
DRM free. Available in
digital & print editions.
spl_
Joshua ThijssenHis passion lies in high-end and complex internet systems, code optimization and server administration. His programming is a freelance consultant, trainer and developer.
skills include-but are not limited to-PHP, C, Java, and Python, and he has experience on a wide range of operating systems. He is a regular speaker at international conferences and speaks
about a wide variety of subjects. You can find his blog on http://www.adayinthelifeof.nl.a php[architect] guideMastering
the SPL Library
by Joshua ThijssenThe Standard PHP Library (SPL) has recently gained popularity among PHP developers. With more complex applications and more data to process, the library’s vast
functionality can make development easier and more efficient, but the documentation for the SPL falls far behind PHP’s core documentation.
Mastering the SPL Library - the facets of the library, including background information where needed. Each entry is illustrated with code examples a php[architect] guide covers all
to give you an idea of how to use it. After reading this book, you will be ready to use the SPL interfaces, data structures, and - of course - the iterators.
This book is perfect for those ready to begin using the SPL library and for those already familiar with it who wish to learn the ins and outs of its more advanced features. With its
detailed information and code examples, this book is a great reference for all SPL users. Developers will want it on their desks at all times.