Learn how to use git with commands for commiting, branching, rebasing and squashing
Category: Links
How we end up with big, ugly commit histories and how to prevent having one
Lots of common sense stuff but also some useful tips…
- Do your dirty stuff inside your own fork.
- When you are on a feature branch, always rebase or pull –rebase.
- To make the history look more meaningful and modular, make use of git add -p and git rebase –i
- Never rebase any shared branch onto your feature branch and force push to any shared branch.
How To Program A Ford Focus Remote Key Fob 2008 – 2011
Bookmarking this for my wife’s old car…
- Unlock all doors using the power door lock switch on door panel.
- Turn ignition from OFF to ON 8 times within 10 seconds, with the 8th time ending in ON. Door locks will cycle to confirm programming mode. (*ON is as far forward as you can turn without starting the vehicle*)
- Within 20 seconds press any button on first keyless remote. Door locks will cycle to confirm programming.
- Within 20 seconds, press any button on a second keyless remote. Door locks will cycle again to confirm programming. (*If you only have one remote to program skip step 4*)
- Turn ignition to OFF. Locks will again cycle to indicate end of programming mode.
Source: How To Program A Ford Focus Remote Key Fob 2008 – 2011 – YouTube
The next popular programming language is probably English
It sounds like Github copilot workspaces will be a lot like working with outsourced development efforts. They are both likely to be better at generating technical debt than useful code if not managed effectively.
Source: https://every.to/chain-of-thought/i-spent-24-hours-with-github-copilot-workspaces
Hints for Distributed Systems Design
These hints are not novel, not foolproof recipes, not laws of design, not precisely formulated, and not always appropriate. They are just hints. They are context dependent, and some of them may be controversial.
What’s New in the Reliable Web App Pattern for .NET
The pattern champions resiliency patterns such as retry, and circuit breaker, performance efficiency patterns like the cache-aside pattern and optimizes for cost and security. It also shows you how to achieve a 99.9% business service level objective (SLO) with multi-region support.
The Serverless Illusion
Serverless reduces the need for (readily available) ops skills but increases the demand for (less readily available) distributed system design skills.
