igor_marques

7 ms·

1.
Delivery Reports – Reasons to Adopt This Practice // Leadership Quickstop(leadershipquickstop.substack.com)
2 points by igor_marques 4y ago|1 comments
2.
by igor_marques 4y ago
How a simple practice can add a lot of value to a team's work.
3.
Git Basics: Rewriting a branch's commit history from scratch(medium.com)
1 points by igor_marques 8y ago|0 comments
4.
Remote Work: Introduction and Tips(medium.com)
65 points by igor_marques 9y ago|7 comments
5.
Simple Ways to Improve the Health Endpoints of Your Apps(blog.codeminer42.com)
1 points by igor_marques 10y ago|0 comments
6.
Monitoring Your App's Health with Sickbay and the Nurse(blog.codeminer42.com)
1 points by igor_marques 10y ago|0 comments
7.
Git Basics: Combining two (or more) commits into just one(blog.codeminer42.com)
1 points by igor_marques 10y ago|0 comments
8.
Git Basics: Adding more changes to your last commit(blog.codeminer42.com)
2 points by igor_marques 10y ago|0 comments
9.
Good communication in software development teams(blog.codeminer42.com)
2 points by igor_marques 10y ago|0 comments
10.
by igor_marques 10y ago
thanks for pointing this. It's fixed!
11.
by igor_marques 10y ago
The rebase would ideally be the last thing you do on your branch, and very carefully. And I also mention in the post that we should always use what's best for our teams, so if the squash merge works best for you, go for it! :)
12.
by igor_marques 10y ago
Nothing stops you to use continuous integration with this workflow. For instance, Travis-CI and Codeship support branching (they can tell you if the new build will be fine or not). I didn't mention that in the post because it's in
13.
Git Workflow Basics(blog.codeminer42.com)
187 points by igor_marques 10y ago|75 comments
14.
Rspec: Writing Custom Matchers (for Newbies)(blog.codeminer42.com)
1 points by igor_marques 10y ago|0 comments
15.
An easier way to write coding tutorials
2 points by igor_marques 11y ago|0 comments