Skip to main content

LinkedIn's Web Redesign Is..."Modern" (Nov. 2020)

I'm not here to take a dump on the hard working web designers who brought their ideas to life because there are good things, and things that need just a smidgen of improvement.

One day in November 2020, I opened my LinkedIn to see this:




Pictured: Rendition of me opening Linked In to see the layout change, but the phone is a laptop, my pillows have Pokemon covers on them, and I am a black woman.

A positive: While it is bright, the icons are not sending me to primary color hell. I call it "Fischer-Price-ification" on Twitter, where major tech companies like Google are changing icons to be very bright, childish colors.

It changes on occasion. I like the Easter and Halloween ones!


Feedback: It's SO bright. It almost overwhelms the icons, especially the "Job" one. Let's give it a change.



I see why Google and Microsoft lean toward those color schemes.

This might be a great opportunity to give us themes.



There needs to be starker contrast between the colors of each icon.

Feedback: The background...the grey. It does not contrast enough. 


 Too intense.


 Better.

You can change the button, but it shares the same properties as the IN logo up there and inline links


A positive:

I like the additions of more rounded edges. As far as I remember (and I could be faulty), they were limited to the Activity section, and the "⬆ New Posts" one was the most prominent.


That dark green is kind of an odd choice. It's darker than the post options.

A positive: I like how the icons change depending on where you are!


(The gif is about 28 second long)


Overall, it's more based upon aesthetics than a total reworking of the website, as far as I can tell.

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 ...