際際滷

際際滷Share a Scribd company logo
FROM DEVELOPER
TO MANAGER
Laravel Tools, Tips and Processes
PovilasKorop
www.laraveldaily.com
August2016@LaraconEU
T H E R E L I V E D A L A R A V E L
F R E E L A N C E W E B -
D E V E L O P E R .
ONCE UPON
A TIME..
AND HE WAS
HAPPY!
Everyone loved and respected him.
And gave him more work to do.
I WILL HIRE OTHER
FREELANCERS!
C O M P A N Y . C O M
S O H E T H O U G H T
W H A T C O U L D P O S S I B L Y G O W R O N G ? . .
DEVELOPER
BUSINESS
OWNER
MANAGER
S O T W O T R A N S I T I O N S H A P P E N E D . . .
+
HOW CAN I CREATE PROJECTS
THAT BRING SUCCESS
TO MY CLIENTS?
Q U E S T I O N F O R A F R E E L A N C E R :
HOW CAN I HELP OTHERS
CREATE PROJECTS
THAT BRING SUCCESS
TO OUR CLIENTS?
Q U E S T I O N F O R A T E A M L E A D E R :
PROCESSES
C O M P A N Y . C O M
I T ' S A L L A B O U T
. . . A N D T O O L S T O I M P L E M E N T T H E P R O C E S S E S
C O M P A N Y . C O M
Examples of processes
Deployment
Readmeanddocumentation
Newdeveloperonboarding
Testing/QA
Project/taskmanagement
Communication/notifications
Crisismanagement
SO I'M STILL
LEARNING...
C O M P A N Y . C O M
But I will tell you some lessons learned,
also tools/tips that help along the way.
DEPLOYMENT
C O M P A N Y . C O M
P R O C E S S 1 .
forge.laravel.com
LARAVEL FORGE
envoyer.io
ENVOYER
github.com / bitbucket.org
USING BRANCHES
slack.com
SLACK INTEGRATIONS
https://github.com/spatie/laravel-backup
BACKUPS
bugsnag.com
BUGSNAG
TIPS ABOUT DEPLOYMENT
Responsibilities: Know who does what and when
Talk with clients about hosting upfront
Documented processes - so that anyone could potentially deploy code
But be careful about everyone deploying code
Standard staging servers is a great thing
Auto-deploy to staging
You still have to SSH to fix stuff
Don't panic
PROJECT
MANAGEMENT
C O M P A N Y . C O M
P R O C E S S 2 .
trello.com
TRELLO
toggl.com
TOGGL
teamweek.com
TEAMWEEK
TIPS ABOUT MANAGEMENT
Again - clear processes (what is "done", "pending" etc.)
Set up notifications properly (but not too many)
Deadlines, milestones and reasons for them
Views for clients and for developers
Review the whole thing once in a while
Visual feedback (screenshots / screencasts)
DOCUMENTATION
C O M P A N Y . C O M
P R O C E S S 3 .
docs.google.com
GOOGLE DOCS
README.MD
.ENV.EXAMPLE
https://github.com/mpociot/documentarian
API: DOCUMENTARIAN
TIPS ABOUT DOCUMENTATION
Think about others
Put documentation where it can be easily accessed
Don't write 20-page long tutorials
Videos and screencasts are a good thing
THANK YOU
M Y J O U R N E Y H A S J U S T B E G U N . .
L A R A V E L D A I L Y . C O M
P O V I L A S @ L A R A V E L D A I L Y . C O M
@ P O V I L A S K O R O P

More Related Content

From Laravel Developer to Manager: Tools, Tips and Processes