I used to be just like you.
My email was a goddamn nightmare. Sure, it started off simple enough, but over the years it evolved into something else — something messy and complicated. There was no real structure, no rhyme or reason. The unread messages started to pile up. It became problematic to find the messages that I needed to respond to in an endless sea of crap I had allegedly signed up for. Opening my inbox was a source of stress. I had to disable notifications on my phone because of the constant irritation. The hundreds of unread messages started reaching into the thousands. My friends, family, and work partners couldn’t rely on a prompt response from me. It was getting worse, and there was no end in sight.
(or: “Things I really wish I knew when I was getting started with this”)
Diving into Angular? That rabbit hole runs deep.
It’s fantastic and confusing and amazing and complex and straightforward and kind of feels like voodoo, but overall I like it a lot.
My project involves an AngularJS frontend that consumes a Laravel API backend. These two technologies can definitely play nice together, but it’s taken me a LONG time to get there, especially when you throw best practices into play. After banging my head against my desk for a week or two, I finally have something that seems like some sort of “good code” (gasp!) that I’m not embarrased to share with the public.
Your online security sucks. I know, you think it’s good, but it’s not. But, all hope is not lost! Follow me down the rabbit hole, and I can show you how to fix everything much faster than you ever thought possible.
More of a reference for me than anyone else, but I use these shell commands quite frequently.
Google Chrome is a great browser. One of the more powerful features that I use extensively is the built-in search engines. If you know how to leverage these, you can use the address bar as a command line of sorts. You can access your engines by right-clicking the address bar and selecting “Edit search engines”, or by visiting chrome://settings/searchEngines (which you will have to copy and paste, as Chrome will not let you access addresses beginning with the chrome:// prefix). They are listed by name, command, and query string. Typing the command in the address followed by a tab or space will engage the engine, and whatever you type after this will be passed as a parameter to the query. To customize your engines, the parameter is represented by “%s”, allowing you to carefully craft your query strings.