Skip to main content

Book: The 4 Hour Workweek by Timothy Ferriss

The general idea of the book is protecting your time* - From meetings, overbearing bosses, and phone calls, something I can relate to.

I will be more receptive to you if you outline your ideas about the position in an e-mail rather than "hop on a call for a quick chat about this opportunity". I've taken to sending a link to this portfolio, a few relevant posts, and asking if this is in line with the position, and encouraging them to ask more questions.

I'm picking out the quotes that spoke to me. 

 "Risks weren't that scary once you took them."

It's true!

"It is far more lucrative and fun to leverage your strengths instead of attempting to fix all the chinks in your armor."

Struggling to drill down and use the Cybersecurity minor? Not for me. Security is to be respected and should be incorporated into new builds, and I will leave the CISSP to others and cheer them on.

 Learning, writing, and teaching? That's more my speed.

 "Most bosses are less than pleased if you spend one hour in the office each day..."

Because bosses and the entire workforce often operate by fear. 

Fear on the employee's side that you may become unemployed, so you play along.

Look for the company that lets you have a flexible working day where you become happy, relaxed, and civically engaged!

"Most people are fast to stop you before you get started but hesitant to get in the way if you're moving."

That's true!

"How has doing what you "should" resulted in subpar experiences or regret for not having done something else?"

I can tell you from experience; The "right" thing (college, certifications) have not helped me one iota. What society tells us is "right" is working for fewer and fewer people, and we should think more critically about following everything.

 Think about who benefits from us going to college initially; Between debt and underemployment - It's not us.

"Doing less meaningless work [...] This is hard for most to accept, because our culture tends to reward personal sacrifice instead of personal productivity."

See 'Most companies operate by fear' above.

The book surprisingly becomes outdated in ways it didn't anticipate; That you would have to wheedle your boss to support your remote work, as if they're the donkey and the carrot is more productivity. It still is a good framework on how to prompt for feedback and negotiate with people.

I'll leave you with my favorite quote - "Reality is negotiable."


*Also a lot of "taking advantage of the 'Global South'

Comments

Popular posts from this blog

Connecting IoT Devices to a Registration Server (Packet Tracer, Cisco)

In Packet Tracer, a demo software made by Cisco Systems. It certainly has changed a lot since 2016. It's almost an Olympic feat to even get started with it now, but it does look snazzy. This is for the new CCNA, that integrates, among other things, IoT and Automation, which I've worked on here before. Instructions here . I don't know if this is an aspect of "Let's make sure people are paying attention and not simply following blindly", or an oversight - The instructions indicate a Meraki Server, when a regular one is the working option here. I have to enable the IoT service on this server. Also, we assign the server an IPv4 address from a DHCP pool instead of giving it a static one. For something that handles our IoT business, perhaps that's safer; Getting a new IPv4 address every week or so is a minimal step against an intruder, but it is a step. There are no devices associated with this new server; In an earlier lab (not shown), I attached them to 'H

Securing Terraform and You Part 1 -- rego, Tfsec, and Terrascan

9/20: The open source version of Terraform is now  OpenTofu     Sometimes, I write articles even when things don't work. It's about showing a learning process.  Using IaC means consistency, and one thing you don't want to do is have 5 open S3 buckets on AWS that anyone on the internet can reach.  That's where tools such as Terrascan and Tfsec come in, where we can make our own policies and rules to be checked against our code before we init.  As this was contract work, I can't show you the exact code used, but I can tell you that this blog post by Cesar Rodriguez of Cloud Security Musings was quite helpful, as well as this one by Chris Ayers . The issue is using Rego; I found a cool VS Code Extension; Terrascan Rego Editor , as well as several courses on Styra Academy; Policy Authoring and Policy Essentials . The big issue was figuring out how to tell Terrascan to follow a certain policy; I made it, put it in a directory, and ran the program while in that directory

Building, Breaking, and Building A CRM with Retool

 I like no- or low-code solutions to things. I've often wanted to simply push a button or move some GUI around and have the code implement itself.  I've thought about building something that's like a customer relationship management (CRM) system for keeping up with my network better than my little spreadsheet where I click links and then go like something. The general idea in this CRM Development is:  To have a GUI to add people to a NRM (Network Relationship Management).       Attach it to a database (MySQL is what I went with eventually using Amazon Relational Database service, but you can use PostGRES, and probably others).     Make sure components are connected to each other in the retool interface. This video is a good start. Watching the tutorial video, heard some SQL commands and went 'Oh no 😳" before going "Wait I know basic SQL", which is good, because you'll see.  When you get set up, there's a plethora of resources you can use -- Incl