On Sharing Code…

By Deane Barker
AI Summary

This post explores effective methods for sharing code on LinkedIn, highlighting the importance of clarity and audience engagement. The author provides practical tips on formatting and context to enhance visibility and encourage interaction, ensuring that shared code resonates with both technical and non-technical followers.

Original Location
This content was originally posted to LinkedIn. Link to Original Content

There’s a tendency to get really weird about sharing code, which prevents people from doing it. I’m trying to get better about this.

The average programmer will be writing something handy, and they’ll think, “I should publish this…” But then they get freaked out, because it has to be… better. It needs to be extensible, and they need to cater to every possible use case some random, theoretical person might have.

They want to look smart and responsible to people they don’t know, and they think they need to create a “formal” project with source code and tests and packages and everything so they look like a Professional Programmer™… so they don’t publish it. Too much work. Too much stress.

I’m trying to avoid this. So, here’s some code. It’s not perfect, and it’s not extensible, but it’s documented to a reasonable level and you can do whatever you like with it. It’s highly… disclaimed (?).

(Also, I kinda suck at JS. I have no ego in this. If you see something egregiously wrong, let me know.)

I feel like developers should publish more and worry less.

Simple code to enable mouseover tooltips

Simple code to enable mouseover tooltips. GitHub Gist: instantly share code, notes, and snippets.