How to learn and three projects to try - 123dev #7

Posted on September 12, 2021 • 2 minutes • 419 words

a frame of a car is replaced in commercials with real looking production cars

Comments

Company presentations and movie magic

I often watch conference talks from companies that appear to be complete internal products, but behind the scenes are more like the blackbird car in the gif above. Companies have high performance, purpose built solutions they create and then present them as the answer to everyone’s problem. This isn’t always a negative thing. You should be aware that their Ferrari may not have a windshield or AC.

Learning one thing

The problem with big projects is they require learning a lot of things and have low probability of being completed because staying focused to overcome all the barriers is hard. When implementing a big idea the key to success is learning one thing at a time.

If you try to implement a big idea all at once you’ll have too many things to learn. If you can find one thing to learn and pick a smaller project to teach you that you can build up the skills to implement the big project before you realize.

Links

This talk was so well done. Not only was the editing and diagramming cool, but the tool they built — gcploit — has scary potential.

Compromise any GCP Org Via Cloud API Lateral Movement and Privilege Escalation: Blackhat/Defcon 2020 — www.youtube.com In this Blackhat/Defcon talk, we detail ways to exploit GCP service accounts, and go over some tools to defend against these exploits such as org policy and …

Even with prices available via an API it’s still difficult to estimate costs of projects and changes. This CLI looks like it’ll be handy for personal and work projects.

GitHub - infracost/infracost: Cloud cost estimates for Terraform in pull requests💰📉 Love your cloud bill! Cloud cost estimates for Terraform in pull requests💰📉 Love your cloud bill! - GitHub - infracost/infracost: Cloud cost estimates for Terraform in pull requests💰📉 Love your cloud bill!

Writing tests is not something I’m great at. I never had great intuition on how to write testable code and it always felt like a waste because most of my projects only involved one or two people. I’ve been trying to write more tests in go lately and testify seems like it might help me write them.

GitHub - stretchr/testify: A toolkit with common assertions and mocks that plays nicely with the standard library A toolkit with common assertions and mocks that plays nicely with the standard library - GitHub - stretchr/testify: A toolkit with common assertions and mocks that plays nicely with the standard library