CTBook: Managing a tech team
CTBook: Managing a tech team
About the Book
CTBook = CTO's Book is the book for people of marketing, sales, management, and even for other developers. The goal is to understand the behavior, jargon, and obstacles for the developers when you want to move forward in your tech project. Whether you have a fulltime or contract developer, your own development company, this book is your companion to prevent you to get lost (or even be scammed) with all the knowledge and experience from a developer. It's a recommended lecture if you are starting a new project or company or if you have one.
We will see topics like: What kind of devs do I need to launch my project? What's do backend, frontend, devops or CTO mean? Do I need a developer for my project or should I start without one? What is remote working and why people are trending it?
This book contains experiences about some startups with decided to have their own dev team and they give us recommendations on why this is a MUST in the majority of cases.
About the Author
Table of Contents
- Prologue
-
Introduction
- Contribution
- Preface
-
Developer Jargon
- Programming
- Programming language
- Algorithm
- Framework
- Program, Applications and Web Pages
- Databases
- Bugs and Errors
-
Application Development Steps
- About it
- Discussing the idea, visualization
- Choosing a developer or team
- Legal aspects
- Use of agile methodologies
- Fast or excellent?
- It’s testing time
- Your first users
- Keep adding more value to the user
-
Your own development team
- About it
- I have no budget
- I have enough budget
-
Entrepreneur Troubleshooting
- About it
- My developer is gone
- My developer asks me to redo all the code again
- I hired a new developer for my team and the first few days he does nothing. He keeps reading the code.
- My developer talks to me in technical jargon
- My developer gives me unreachable deadlines
- I entrusted my product’s development to an agency and there are many errors.
- I pay for an app development and I didn’t receive the source code
- My application have no documentation
- My frontend/mobile developer told me that our project will need an API
- My Backend developer says it needs to connect to an API, I thought this was only done by a Frontend role
- My server/app is down
- My developer is working in different freelance projects out of the work
-
Developer Troubleshooting
- About it
- They set me pretty tight development deadlines.
- Non-technical people suggest that I use technologies that someone else recommended.
- I always develop in the same technologies, I don’t learn anything new.
- They offered me stocks instead of a higher salary. Is this viable?
- Why do you add more bugs? We must add more features.
- You have to add machine learning, blockchain… (insert here the most “trendy” technology of the current year).
-
Technical Debt
- About it
- How could it happen?
- How can we solve this?
-
Remote Working
- About it
- Pros and cons
- How can I control a team that is not in the same place as me? What if they honor laziness and I can’t see them?
- Is there any other alternative to remote work, but one that gives my workers that flexibility?
- Recommended tools
-
Feature Development: Is not so complex
- Introduction
- Example #1: As a user, I want to register or log in using Facebook or my email address.
- Example #2 Reservation through a restaurant web page
-
CTOs: Age and experience for startups
- Introduction
The Leanpub 60 Day 100% Happiness Guarantee
Within 60 days of purchase you can get a 100% refund on any Leanpub purchase, in two clicks.
Now, this is technically risky for us, since you'll have the book or course files either way. But we're so confident in our products and services, and in our authors and readers, that we're happy to offer a full money back guarantee for everything we sell.
You can only find out how good something is by trying it, and because of our 100% money back guarantee there's literally no risk to do so!
So, there's no reason not to click the Add to Cart button, is there?
See full terms...
Earn $8 on a $10 Purchase, and $16 on a $20 Purchase
We pay 80% royalties on purchases of $7.99 or more, and 80% royalties minus a 50 cent flat fee on purchases between $0.99 and $7.98. You earn $8 on a $10 sale, and $16 on a $20 sale. So, if we sell 5000 non-refunded copies of your book for $20, you'll earn $80,000.
(Yes, some authors have already earned much more than that on Leanpub.)
In fact, authors have earnedover $14 millionwriting, publishing and selling on Leanpub.
Learn more about writing on Leanpub
Free Updates. DRM Free.
If you buy a Leanpub book, you get free updates for as long as the author updates the book! Many authors use Leanpub to publish their books in-progress, while they are writing them. All readers get free updates, regardless of when they bought the book or how much they paid (including free).
Most Leanpub books are available in PDF (for computers) and EPUB (for phones, tablets and Kindle). The formats that a book includes are shown at the top right corner of this page.
Finally, Leanpub books don't have any DRM copy-protection nonsense, so you can easily read them on any supported device.
Learn more about Leanpub's ebook formats and where to read them
