| package main | |
| // This is an example of a resilient worker program written in Go. | |
| // | |
| // This program will run a worker, wait 5 seconds, and run it again. | |
| // It exits when SIGINT or SIGTERM is received, while ensuring any ongoing work | |
| // is finished before exiting. | |
| // | |
| // Unexpected panics are also handled: program won't crash if the worker panics. | |
| // However, panics in goroutines started by the worker won't be handled and have |
| if (!String.prototype.toCase) { | |
| Object.defineProperties(String.prototype, { | |
| 'toCase': { | |
| value: function(type = 'camel') { | |
| const seperators = { | |
| 'camel': '', | |
| 'pascal': '', | |
| 'snake': '_', | |
| 'domain': '.', |
| /** | |
| * Created by James Falade on 11/10/2018. | |
| */ | |
| var mtn = { | |
| pattern: /0(703|706|803|806|810|813|814|816|903|906)\d{7}/, | |
| name: 'MTN Nigeria' | |
| }; | |
| var airtel = { | |
| pattern: /0(701|708|802|808|812|902|907)\d{7}/, |
just the bare necessities of state management.
Hotlink it from https://unpkg.com/valoo.
You already know you should be making projects to learn things and potentially add to your portfolio. You've read your Malcolm Gladwell, you know that you need 10,000 hours of deliberate practice. Given you're just starting out, I have a slightly contentious suggestion for you: DON'T make anything new.
Your decision-making is a scarce resource. You start every day with a full tank, and as you make decisions through the day you gradually run low. We all know how good our late-late-night decisions are. Making a new app involves a thousand micro decisions - from what the app does, to how it should look, and everything in between. Decide now: Do you want to practice making technical decisions or product decisions?
Ok so you're coding. You know what involves making zero product decisions? Cloning things. Resist the urge to make your special snowflake (for now). Oh but then who would use yet another Hacker News clone? I've got news for you: No one was gonna use your thing anyway. You
The only way I've succeeded so far is to employ SSH.
Assuming you are new to this like me, first I'd like to share with you that your Mac has a SSH config file in a .ssh directory. The config file is where you draw relations of your SSH keys to each GitHub (or Bitbucket) account, and all your SSH keys generated are saved into .ssh directory by default. You can navigate to it by running cd ~/.ssh within your terminal, open the config file with any editor, and it should look something like this:
Host * AddKeysToAgent yes
> UseKeyChain yes
