face any challenge with flexibility 1 Smart Moves Most of the times the basics are not enough and you need to start be “creative” about how to approach to the problem 2 Last Resort If everything else failed there’s only one thing to do 3
works or 1. Always Reproduce the Bug Before You Start Changing Code 2. Read the error message / stack trace 3. Run your code every time you make a small change 4. Guess and Check 5. Write a Test Case that Reproduces the Bug
frustration of being bothered with questions so trivial that the asker could have quickly figured out the answer on their own with minimal effort, usually by reading readily-available documents. People who say "RTFM!" might be considered rude, but the true rude ones are the annoying people who take absolutely no self-responsibility and expect to have all the answers handed to them personally. http://rtfm.urbanup.com/773100
• Mostly overwhelmed with thoughts • Write it down ◦ Use pen & paper ◦ Post-it ◦ Evernote ◦ Notepad ◦ ... ◦ It doesn’t really matter where • Go back to your notes! • Check older notes as well for missed ones
always be your starting point • The Master is most often linked to the current production state ◦ So if it works there it is “safe” to use • Don’t use unstable branch as you don’t know exactly the state they are in ◦ You think you do? ▪ Would you bet your money on it?
It saves you from human mistakes • It allows other people to review you work • It allows other people to work on the same code • Some best practices: https://sethrobertson.github.io/GitBestPractices/
You’ll get all the fixes and won’t experience all the pain behind them • You keep the history clean • Rebase even within your own branch ◦ Squash commits together
friend • It helps you running the whole test suite while you keep coding • Go back and check all the pipeline steps for weird behaviours or warnings • Review your Merge Request before asking others to do it
but there are more? • Are you tackling the right one? • Focus one bug at the time, limiting the Yak Shaving • Separate the context for each bug (that means a new branch as well)
mud you get lost in trying to fix whatever thing comes up, losing sight of what you should be really achieving. Ask yourself this question would allow you to stop, think and possibly take a change of course. There’s no right number about the numbers of changes of course you can make in order to overcome the issue.
answer is no, then just ditch everything. Do a git reset --hard origin/master e start over, and this time you might not need to do anything as the problem was not actually a problem after all.
more easier • They can be applied in any context ◦ IDE ◦ Source Code ◦ SEO Rewrites (haproxy, nginx, apache, …) ◦ Shell (grep, sed, awk) ◦ GMail or any Email Client ◦ Google Analytics Filters ◦ …
exit with :wq • It changes your approach to working with text document • You can replace flexibly using the regex • You can write, easily enough, custom macros for anything • You can turn a spreadsheet in a bash script in 5 minutes • It can literally do anything: https://www.vim.org/scripts/ • It has few package managers as well: Vundle, Pathogen, NeoBundle, vim-plug
to your mind • Try to be synthetic and straight to the point • Include keywords, such as: framework, language, error code, error string, … • Use the quotes to narrow down your search (exact match) • Strip out un-relevant information from the error message, such as: file path of your pc, usernames, hostnames, …
• It is useful to understand when the last change was made • It is useful to read the commit message to get a bit of context (so here the necessity of clear and useful commit messages) • It is useful to check the whole commit structure • It is useful to know who wrote the code and ask him if he/she remembers anything about it
inside the file contents ◦ Yes, it supports RegExp • You can customise the output based on different needs ◦ Show a bit of context, by showing preceding and following lines ◦ Show the line number ◦ Inclusive/Exclusive matching
based on filename/dirname ◦ Yes, it supports RegExp • You can customise the output based on different needs ◦ Files older than X days ◦ Retrieve symlinks
didn’t encountered during your manual testing • They allow you to refactor without worries • They allow other to refactor without cursing the author • They let you write better code, in a testable way, even if you don’t write tests
a PHP code, but you need to get your hands dirty with server configuration • You might be working on a mobile app, but you need to set up an API service just to keep working • You might be working on a certain level, but you need to have the flexibility of looking elsewhere and acting on it, even if it’s not your responsibility. Or you’ll be stuck forever waiting the knight in shining armour coming to rescue you. No-one wants to be that damsel in distress ;)
to system • Drop the vendors folder • Loose the permissions, don’t be shy for a chmod -R 777 • Are the services running? • Can you reach, from where the issue is, the services? • Iptables? • DB Grants? • Are you hitting varnish rather than the frontend? • Is the VPN up and running? • Expired SSL keys? • Opcache? • Doctrine cache? • Are you looking at the right environment? • Is the source-code updated? • Have you dumped all the static assets? Need to Go Wild?
fabiocicerchia
kangnux
benjaminkim
77web
bkuhlmann
dunglas
bigamitiongit
mraible
pospome
palkan
pauloxnet
ski
izumin5210
csswizardry
sferik
phodgson
stephaniewalter
bkeepers
paigeccino
maltzj
rmw
mclloyd
thekraken
panda_program
jnunemaker
