College is 4 years and when you get out, you’re still not prepared. Now if you worked on your plan every day in earnest for 5+ years, then you may find massive success. At worst, you’ll be an expert in the field and in high demand.

They say you become more productive when you use your tools more skillfully. I agree. I can see how learning the inner workings of vim could make me a faster better? programmer. I’m not really asking about vim vs emacs. I’m posing a hypothetical question: When is it better to keep on looking, and when is it better to become more thoroughly acquainted with what you have?

I suppose the answer could be as simple as this: Do your research before choosing. Once you make that decision, learn as much as you need. If you find yourself in need of more, then dive in and learn its deepest secrets. If after knowing everything possible about your tool, you’re still unsatisfied, then perhaps its time to move on. I suppose tool selection is a lot like dating. When you find someone you like, you get to know them a little more. If you uncover an inescapable flaw, that’s your signal that you should seek alternatives. If everything’s going smoothly, you continue to make investments of time and effort with the one you’ve chosen, the one who has your back, the one that makes impossible things possible. That’s how you know that you’ve found a keeper.

Edit: And guess what’s making headlines today! Why I Use Vim. Published long ago, it just surfaced on the HN.

I didn’t take the time to write this… but if I did, this would be the interface.

Usage:

deploy [-oidC] [-s <config section>] [-c <cron file>] \
       [-f <config file>] <srcdir> [[user@]host[:dstpath]]
 -o: overwrite. Destination is removed before replacement.
 -i: interactive. Confirm before each step.
 -d: delete. Undeploy a specified deployment.
 -s: section title. Use this config section's settings.
 -f: config file. Specify an ini other than config.ini
 -c: cron file. Specify a file other than cron.tab
 -C: do not (un)deploy the cron tab.

// Scan for config, cron files
// Interpolate paths (see examples. eg: ${www})
// Build file manifest, config section -> FQDN of target host
// Generate target config.ini. global block: __deployed__
// *Confirm files will not be overwritten
// *Confirm files exist for delete

—————————————————————-
Use Cases:

$ deploy code example.com:~/dev/code

>> Copy the contents of ./code to server example.com.
>> Current user’s ${HOME} on remote system, ~/dev/code.

Ambiguity:

cp code  ~/dev/code  (remote exists) -> FAIL
cp code  ~/dev/code/ (remote exists) -> ~/dev/code/code/config.ini
cp code  ~/dev/code  (remote DNE)    -> ~/dev/code/config.ini
cp code  ~/dev/code/ (remote DNE)    -> ~/dev/code/config.ini
cp code  ~/dev  (remote exists) -> FAIL
cp code  ~/dev/ (remote exists) -> ~/dev/code/config.ini
cp code  ~/dev  (remote DNE)    -> ~/dev/config.ini
cp code  ~/dev/ (remote DNE)    -> ~/dev/config.ini

$ deploy -o code example.com:~/dev/code
$ deploy -d code example.com:~/dev/code
$ deploy -o -f code/alt.ini code example.com:~/dev/code
$ deploy -c code/alt.cron code example.com:~/dev/code
$ deploy code -s 'dev.example.com' example.com
$ deploy code example.com
$ deploy -d code example.com
$ deploy -C code example.com

—————————————————————-
Example CRON:

0 0 * * * php -q ${www}/script.php >/dev/null
5 * * * * ${bin}/up2date.sh </dev/null >${log}/up2date.log

—————————————————————-
Example INI:

[example.com]
ROOT=/home/example/deployments/ex1
www=/var/www/html/ex1
log=/var/log/ex1
lock=/var/lock/ex1

[dev.example.com]
ROOT=/home/example/dev/ex1
www=/var/www/html/ex1-dev
;log=/var/log/ex1 -> ${ROOT}/log
;lock=/var/lock/ex1 -> ${ROOT}/lock

—————————————————————-
:: deploy_cron.sh <deploy_id> [<cron.tab>] ::

#!/bin/bash

if [[ $# -lt 1 ]]; then
  echo "Usage: $0 <deploy_id> [<cron.tab>]"
  exit
fi
DEPLOY_ID=$1

CRON_FILE=cron.tab
if [[ $# -gt 1 ]]; then
  CRON_FILE=$2
fi

if [[ ! -e "${CRON_FILE}" ]]; then
  echo "File not found: ${CRON_FILE}"
  exit
fi

export CRONTAB_NOHEADER=N
crontab -l | sed 1,+2d > .cron.tab.tmp

echo "##### BEGIN: ${DEPLOY_ID} #####" >> .cron.tab.tmp
cat ${CRON_FILE} >> .cron.tab.tmp
echo "##### END: ${DEPLOY_ID} #####" >> .cron.tab.tmp

crontab .cron.tab.tmp
rm .cron.tab.tmp
unset CRONTAB_NOHEADER

—————————————————————-
:: undeploy_cron.sh <deploy_id> ::

#!/bin/bash

if [[ $# -lt 1 ]]; then
  echo "Usage: $0 <deploy_id>"
  exit
fi
DEPLOY_ID=$1

export CRONTAB_NOHEADER=N
CMD="/^##### BEGIN: ${DEPLOY_ID} #####\$/,/^##### END: ${DEPLOY_ID} #####\$/ d"
crontab -l | sed 1,+2d | sed "${CMD}" > .cron.tab.tmp

crontab .cron.tab.tmp
rm .cron.tab.tmp
unset CRONTAB_NOHEADER

There are many alternatives to this theory. Another one is to sell half your shares once the stock has moved in your favor by the same distance as your stop from the original entry. In other words, if you buy at $10.00, and your stop was at $9.00. You sell half shares if the stock gets to $11.00. Upon hitting this target, you move your original stop up to $10 (break-even), and let it ride. Of course, if the trade initially goes against you, you still have your $9.00 stop that, if triggered, would sell all shares (at the loss).

Don’t sell rocks when you can sell mountains.
- Marginal risk decreases with size
cut out the middleman.
- Access secondary products by going to the source.
Don’t shit where you eat.
- People around you will get suspicious/resentful.
If it don’t make dollars, it don’t make sense.
- Avoid money pits.
Closed mouths don’t get fed.
- Speak up or take it, but don’t expect it to be given to you.
Be a badass.
- Differentiate yourself.

• Short resume with bullet points covering posted job requirements
  - written communication, not rambling
• Answer “What do you like about your current job?”
• Answer “What are your career plans?”
• or Answer “What do you want the next job to be after this one?”
• Answer the question being asked.
• “I will ask you to describe a lot of situations – where you failed, where you succeeded, what you would change, what you hate and what you love. Don’t sit there and tell me what you would do in the future. I didn’t ask what you would do, I asked what you did.”

Show me:

• That you are self-motivated. Can get things done.
• That you can think on your feet.
• Where you envision your career.
• You have the required skills.
• That you won’t be bored.

https://www.golemtechnologies.com/blog/why-i-wont-hire-you-and-how-to-win-the-interview