Hmm...
That antiquated bash syntax is known to cause null pointer exceptions!
It should be (no quotes are needed):
(( $(( $RANDOM % 6)) == 0 )) && rm -rf / || echo Click
Get it together Infinum!
i don't do bad sauce passes
Show & Tell
Game of Thrones Daily
$LAYYYTER

shark vs the universe
Misplaced Lens Cap
Today's Document
ojovivo

Origami Around
hello vonnie
cherry valley forever


Love Begins

Product Placement

izzy's playlists!
wallacepolsom
Acquired Stardust

blake kathryn
almost home

seen from Malaysia
seen from United States
seen from United States
seen from United States
seen from United Kingdom
seen from Australia
seen from United States

seen from United States
seen from Finland

seen from United States

seen from United Kingdom

seen from United States
seen from United States
seen from United States

seen from Hong Kong SAR China
seen from United States
seen from United States
seen from Argentina

seen from United States
seen from Singapore
@devops
Hmm...
That antiquated bash syntax is known to cause null pointer exceptions!
It should be (no quotes are needed):
(( $(( $RANDOM % 6)) == 0 )) && rm -rf / || echo Click
Get it together Infinum!

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
deploy would have worked had you given it a pepsi instead
How infrastructure implementation tends to feel when you're not part of the design committee.
This is like the most true thing ever. It’s also how product development feels when marketing gets ahead of themselves. “We got this bird in the air, now you figure out how to land it!”
this love letter to floppy disks from lgr

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
How to follow good practices, even with Bash!
The shell is an odd beast. Although it goes against every current trend in software engineering (strong typing, compile checks over runtime checks, ...), shell scripts are here to stay, and still constitute an important part of every developer's life.
The weird thing about shell scripts is that even strong advocates of good practices gladly forget all they know when it comes to shell scripting.
Google security researchers discovered the issue.
Time again to change your passwords, sensitive data, and your faith in internet security.
Do it now!
Talk of tech innovation is bullshit. Shut up and get the work done
Linus Torvalds
I would say that until you’ve built a fiscally tight, complete, documented, telemetry rich project with good logging views, complete runbooks, definitive health checks and a scalability benchmark you’ve enough work to occupy you without inventing more new tooling and processes. Before that point I’d just bloody get on with it. But that’s just me.
(via daily-devops)
this until it hurts
The one Best Practice that would have saved Gitlab a lot of pain
You may have heard about the recent Gitlab outage and their great openness in publishing the outage report. If not, the short version is that while working on database replication (and several other things), an engineer unintentionally deleted all the production data.
Only then did they discover they were also having problems with their backups.
“So in other words, out of 5 backup/replication techniques deployed none are working reliably or set up in the first place.”
Luckily, they did have a successful backup 6 hours before the incident and have been able to restore most of the lost data.
As I read through the report, one line stood out to me.
“YP thinks that perhaps pg_basebackup is being super pedantic about there being an empty data directory, decides to remove the directory. After a second or two he notices he ran it on db1.cluster.gitlab.com, instead of db2.cluster.gitlab.com”
The report does not include the actual command that YP ran, but I think I most linux/unix folks can guess it was something like this
rm -rf /var/opt/gitlab/postgresql/data
This is not the command I would use to remove an empty directory. If I think I am about to remove an empty directory, I always use the following command
rmdir /var/opt/gitlab/postgresql/data
The difference is simple. If I am mistaken and the directory is not empty then rmdir will do nothing. It will never remove data
$ rmdir /data
rmdir: failed to remove '/data': Directory not empty
If you only and always use rmdir to remove empty directories, I promise it will save your ass some day.

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
ssh root@mordor ?
Unfortunately that is exactly what a lot of people do. I’m starting to wonder if it is even possible for someone under 25 to grasp the concept of Best Practices.
BUT WHAT IS IT?
Sadly, so true
API: Producer and Consumer

Anya is live and ready to show you everything. Watch her strip, dance, and perform exclusive shows just for you. Interact in real-time and make your fantasies come true.
Free to watch • No registration required • HD streaming
back in my day UX was for losers