Eric Hendrickson shikari7

The C Shell isn't bad.

The C Shell is one of the most reliable Shells I ever worked with. The C Shell inherited features from and is the only continuation on the Thompson Shell and Mashey Shell (the Shells included with Research Unix and PWB Unix, respectively). Erroneously, the C Shell is regarded as bad and glitchy. I beg to differ, though. Due to its "limitations", the C Shell is one of the most reliable Shells to work with. I added some comments on this Perl developer's complaints on the C Shell, in the hope it'll serve as a guide on how to adequately write scripts, as well as to encourage people on not giving up.

The power of a system comes more from the relationships among programs than from the programs themselves.

By following this principle, it's possible to get many interesting things out of Shells and any program at all. Control structures (namely, if/else) can be replaced wi

👋 Hi, I'm Geoff. I stole off all your NFTs.

I respectfully ask that you don't quote me as “$company person Geoffrey Huntley said” – if I speak for a company, I will publish on its channels. My full name is "Geoffrey Huntley" please use that and not "Geoff Huntley".

website: https://ghuntley.com/
newsletter: https://ghuntley.com/newsletter
twitter: https://www.twitter.com/geoffreyhuntley.com
linkedin: https://www.linkedin.com/in/geoffreyhuntley

No, your cryptocurrency cannot work

Whenever the topic of Bitcoin's energy usage comes up, there's always a flood of hastily-constructed comments by people claiming that their favourite cryptocurrency isn't like Bitcoin, that their favourite cryptocurrency is energy-efficient and scalable and whatnot.

They're wrong, and are quite possibly trying to scam you. Let's look at why.

What is a cryptocurrency anyway?

There are plenty of intricate and complex articles trying to convince you that cryptocurrencies are the future. They usually heavily use jargon and vague terms, make vague promises, and generally give you a sense that there must be something there, but you always come away from them more confused than you were before.

tmux shortcuts & cheatsheet

start new:

tmux

start new with session name:

tmux new -s myname

	git clone [email protected]:alastorid/Solaar.git
	cd Solaar
	sudo pip install ./
	sudo ./rules.d/install.sh


	# this script uses syntax for bitbucket server.
	# For bitbucket cloud see https://confluence.atlassian.com/bitbucket/use-the-bitbucket-cloud-rest-apis-222724129.html
	#
	# Note: replace username, password and PROJECTNAME with your values
	USERNAME=xxxx
	PASSWORD=xxxx
	PROJECTNAME=xxxxx

	# jq syntax helpful links:

	## One line per log entry with merge graph
	## (--decorate is implicit for newer git versions?):
	#git log --graph --oneline --decorate

	## \|
	## Add --branches --remotes --tags --merges to see entries for all of the
	## corresponding refs, not only commits (--all for all refs).

	## Format output with --pretty=tformat:'<format>'
	## Interesting placeholders for oneline <format>: