Search icon CANCEL
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Going IT Alone: The Handbook for Freelance and Contract Software Developers

You're reading from   Going IT Alone: The Handbook for Freelance and Contract Software Developers A detailed guide to self-employment for software and web developers - from identifying your target market, through to managing your time, finances, and client behavior

Arrow left icon
Product type Paperback
Published in Dec 2016
Publisher
ISBN-13 9781783001408
Length 376 pages
Edition 1st Edition
Concepts
Arrow right icon
Author (1):
Arrow left icon
Leon Brown Leon Brown
Author Profile Icon Leon Brown
Leon Brown
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

Going IT Alone: The Handbook for Freelance and Contract Software Developers
Credits
About the Author
Acknowledgements
About the Reviewer
Preface
1. Introducing Freelancing 2. Positioning Yourself in the Market FREE CHAPTER 3. Defining Your Business Model 4. Creating a Brand 5. Networking, Marketing, and Sales 6. An Introduction to Client Types 7. Managing Clients 8. Negotiation 9. Software Development Resources, Patterns and Strategies 10. Software Development Methodology 11. Creating Quotes and Estimates 12. Project Management Appendix

Software problems: A recap


One theme that's consistent throughout this book is that the human factor can be problematic. This is not an observation meant to be pessimistic about the prospects of working with people, but of the exposure to problems that people introduce to software projects. These problems include:

  • Programmers — make mistakes, resulting in poor quality code that introduces security vulnerabilities and restrictions to react to future situations.

  • Project managers — underestimate the complexities of requirements and ability of their programmers.

  • Designers — over complicate designs, resulting in unnecessary complexity and project risks when integrating their designs into code.

  • Clients — fail to define their software requirements in a literal way that software people can make sense of and change their requirements over time.

  • Everyone — gets ill, needs holidays and change jobs.

Knowing in advance that the involvement of people in software projects are a risk can be used to your advantage...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime