Skip to main content

Business Bonus: LinkedIn down, Internet Clowns

 

When the world's .... strangest networking site when down on Feb. 23rd, people were quick with the jokes.

Some of my peers find value in LinkedIn; After 4 years, I see it as a soundboard for everything wrong with the modern workforce, a giant conference for people with no empathy, wearing 16-hour workdays as badges of honor.

Besides their abysmal censoring of black professionals and the rampant bigotry of the userbase, LinkedIn (Owned by Microsoft), have been posting more articles that empower the jobseeker. 

And, slowly, people on the site have been changing too - For the better. They're being deprogrammed, learning that their job doesn't really warrant a 40-hour week, that their company could absolutely pay them the same for less hours, that they too can have a happier, more balanced life if they push for it.

But we still had THE JOKES. 

Only my tweets are directly embedded; If you see yours here and would like me to embed them, contact me on Twitter.

 

 



Some tweets reminded us that people use it for jobseeking and genuinely need it. If someone is waiting on a message, I sympathize with them. 

I have so many ill feelings toward the site, I'm trying not to let it color this article (so far, so good).


As of about 4 PM on Tuesday, the site was operational again.

 

For 6 hours, it was nice to have a site where people justified broken hiring practices not work.

 

  It reaffirms that a lot of us just don't mesh with people on the thought leader capital of the world. Despite that, I'm glad apparently enough people find value in the site enough to miss it.


Now Paypal needs to hire their software devs to fix their currency conversion glitch.

Comments

Popular posts from this blog

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

 If you're seeing this post, I'm helping you, and you probably have LI presence: React and share this post to help me in return.   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

Create a Simple Network (Packet Tracer) + A Walkthrough

Again; I've done this, but now there's so many new things, I'm doing it again. The truly new portions were...everything on the right side of this diagram; The cloud needed a coax connector and a copper Ethernet connector. It's all easy to install, turn off the cloud (Weird), install the modules. Getting the Cable section of Connections was an unusual struggle - The other drop down menu had nothing within. It required going into the Ethernet options and setting the Provider Network to 'cable', which is the next step AFTER the drop-downs. The rest was typical DHCP and DNS setups, mainly on the Cisco server down there. The post is rather short - How about adding a video to it? Find out what A Record means - This site says 'Maps a name to an IP address', which is DNS. So it's another name for DNS? You can change them (presumably in a local context) to associate an IP address to another name.

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