| [alias] | |
| co = checkout | |
| st = status | |
| cob = checkout -b | |
| logg = log --all --decorate --oneline --graph --stat | |
| l = log --decorate --oneline --pretty=format:\" %cn committed %h on %cd : %s\" | |
| le = log --color --graph --pretty=format:'%Cred%h%Creset -%C(yellow)%d%Creset %s %Cgreen(%cr)(%ci) %C(bold blue)<%an>%Creset' | |
| ac = !git add -A && git commit | |
| ca = commit --amend --no-edit |
| :: https://vuejs.org/images/lifecycle.png |
I work as a full-stack developer at work. We are a Windows & Azure shop, so we are using Windows as our development platform, hence this customization.
For my console needs, I am using Cmder which is based on ConEmu with PowerShell as my shell of choice.
Yes, yes, I know nowadays you can use the Linux subsystem on Windows 10 which allow you to run Ubuntu on Windows. If you are looking for customization of the Ubuntu bash shell, check out this article by Scott Hanselman.
| :: Architecture and Systems Design | |
| → http://highscalability.com/all-time-favorites/ | |
| → https://www.youtube.com/watch?v=ZgdS0EUmn70 | |
| :: Coding Practice | |
| → https://codepath.com/ | |
| :: Uber Engineering | |
| → https://eng.uber.com/ |
| :: type → about:config on address bar | |
| :: set 'dom.allow_scripts_to_close_windows' to TRUE (Double Click on 'FALSE') |
| position: absolute; | |
| top: 5; | |
| bottom: 0%; | |
| left: 0; | |
| right: 0%; | |
| background-color: #ffffffa1; | |
| z-index: 99; | |
| padding: 79% 0% 00% 43%; |
| :: RefUrl | |
| → Documentations :: https://developers.google.com/web/fundamentals/primers/promises | |
| → udacity :: https://classroom.udacity.com/courses/ud898 | |
| → Online JS editor :: https://playcode.io/126236?tabs=console&script.js&output | |
| :: An activity is a non-atomic task ( task is an non-atomic Activity and used when the work in progress can be broken down to a finer level of detail) or procedure decomposable into actions. | |
| :: An action is a task or procedure that cannot be broken into parts. | |
| :: When to Use Activity Diagram | |
| → When making a dynamic model of any process. | |
| → Design processes (what designers do) | |
| → Designed processes (what designers create) | |
| → During analysis | |
| → During resolution (decision) |
| RefUrl → https://www.oreilly.com/library/view/software-architecture-patterns/9781491971437/ch04.html#idp1166176 | |
| RefURL → https://blog.mwaysolutions.com/2014/06/05/10-best-practices-for-better-restful-api/ | |
| :: 200 – OK – Eyerything is working | |
| :: 201 – OK – New resource has been created | |
| :: 204 – OK – The resource was successfully deleted | |
| :: 304 – Not Modified – The client can use cached data | |
| :: 400 – Bad Request – The request was invalid or cannot be served. The exact error should be explained in the error payload. E.g. „The JSON is not valid“ | |
| :: 401 – Unauthorized – The request requires an user authentication | |
| :: 403 – Forbidden – The server understood the request, but is refusing it or the access is not allowed. | |
| :: 404 – Not found – There is no resource behind the URI. |
