I've been a full-stack engineer since 2007. Sales, marketing, and networking has never been my strong suit. In June I decided to do something about that.
This is a cheatsheet for useful Git commands that we use semi-regularly, mostly for internal use as a quick future reference but I figured I would share.
The demand for software engineers is higher than ever, and it grows by the day. Custom software provides immense benefits to businesses and their customers. It is a necessity for most businesses to keep up with the modern world.
What would you say professional software engineers do? The job usually involves a lot more than writing code. Meetings. User feedback. Bug fixes. Design decisions. Choosing the right tools. Cost-benefit analysis. Team building. Delegation. The list goes on.
The job can vary significantly, depending on the role and level of experience, but at the end of the day, it all comes down to producing code which solves real problems and meets business needs. The effective output of software engineering can be measured as code committed, not by the number of lines or even the number of commits, but by the problems solved, features added, and systems integrated.
If you're a professional software engineer, there's at least a 99.99% chance you know what Git is, and you probably use it almost every day. The tangible work you produce is typically a series of Git commits and branches. The end result is the current version of your application.
What if you had a way to skip all of the time-consuming integration work, a way to pick and choose exactly the commits you need to produce your desired application? That is exactly what we're doing here.
If I've learned anything from being glued to a code editor for (probably too many) years, it's that the simplest approach is almost always the best one.
In the case of modern front end engineering and React especially, you can reduce everything down to two simple concepts...
Today marks the official beginning of Molecule.dev!
We have many exciting things coming.