DEV Community: TreeZone

Why Node Are Publishing A New Code Library And Your Business Needs It

TreeZone — Sun, 17 May 2020 17:45:04 +0000

There's a very complex and intricate law to the internet. One of the rules of this is: if you can bring in a code library, it stops you having to write code.

No matter how many problems the code library you bring in causes you, it's better than learning the language yourself.

If you think otherwise consider: yes, sometimes it really is better to bring in a code library. Maybe it's a tiny library that cleverly wraps something notoriously confusing up in a package that makes things so much easier. Maybe it's doing cryptographics that you will never in your life have the time to learn the mathematics to do properly.

Or many it's a random library you brought in because there was buzz around it without really knowing why, and some idiot thinks it's just garbage. What's their deal? Maybe they think you're bringing in moment.js to format a date that's now native to the TypeScript compiler you're using just because you don't know any better. Resist these people.

Who cares if 90% of imports into a package.json are not needed. Or 99.2% of useless dependencies are created by people with loads of experience who should know better about these problems but are too jaded to care about the issues they create. The point is if you're senior enough to fix these things but don't want to, it's not your problem. If you're a junior, who the hell cares what you want, just do what they say for the lord's sake.

Personal Programming Blogs Are Wonderful

TreeZone — Sun, 17 May 2020 17:29:44 +0000

Have you ever wanted to write a personal programming blog? There are lots online.

Generally you'll need to have one of the following elements:

Some memes.

A semi-obscure programming concept that is taken just so far; there's no real idea at the end what it might be used for, but if you managed to cope with it you did something difficult, so pat yourself on the back.

The syntax for a code library you've never heard of until now (but is defo amazing). It does things you'd be far better placed to code yourself, if you actually knew how to program.

An edge-case optimization you'll never use for anything practical.

A hello-world that gets you so far and then doesn't really elaborate on why you just did that, which is covered by the official documentation.

A hello-world that's probably actually trying to do something useful, but missing so many steps, or has so many platform specific steps, you're essentially going to have to piece things together using the entire internet.

Random code snippets from a freelance job you were doing.

Something about php.

Wonderful stuff.

Adopting Map and Compass: A New Route Down an Old Road

TreeZone — Sat, 16 May 2020 15:41:44 +0000

A couple of days ago I wrote a short piece about our company's journey adopting new practices, like a map and a compass. Though the names could clearly be interpreted as languages, frameworks, or many other computer science related things (MongoDb's Compass database management tool comes to mind as well as at least a dozen different things that do 'mapping'), the details are entirely fictional and are certainly not intended to refer to any one thing. Here goes:

"What if you were in possession of a map and compass, in a place where maps are not used? Perhaps they are not understood at all, or perhaps they are mistrusted because some previous maps showed an incorrect version of the landscape or the compass was not correctly calibrated. Maybe they were not known about at all. Perhaps there are other reasons. The essential point is that maps are not used.

Each day you embark on an expedition. Many days you blunder into swamps, or stumble blindly toward forests and ravines. To begin with you believe your map and compass are the solution. You speak to many people on the expedition about these items. You show them tests and explain how they work. Some people suggest that though they do believe these things work, nothing has been proven on this expedition, and probably they are more aimed at other people. Others say there are so many different ways you could read a map and compass, it would be difficult to know which to choose. Some become annoyed at your constantly mentioning the same two things, over and over. They tell you that you've become hung up on a triviality and you must focus back on the expedition.

Sometimes meetings are called. At one meeting it is suggested that after all, we may want to consider the map and compass. Significant objections are raised. What if the map gets wet? Another takes up their point: if the map gets wet and the ink is smudged it will lead us in all the wrong directions. Furthermore, either of the two things may get lost and the one is close to useless without the other. It is decided that though the idea might be good in theory, there are too many unknowns.

Instead, the group focuses on the overcoming of obstacles as they always have done. One person is very good at swimming, so whenever the group becomes lost in a swamp, she walks ahead first, then if she falls into water she swims out, doubles back and tells the group what happened. Another is good at climbing trees, so when they are in the forest he climbs up to the top of one and calls out to tell people which ways to go. This seems to work OK in the main…

You almost forget all about the map, but whenever someone trips in the forest and twists their ankle, or shivers a little at night after falling into dank water, you think of it a bit. Sometimes you bring it up again, in passing. What if we try the map, you say. Yes that is an interesting idea. I think you probably should ask a question about it to someone. Perhaps we should have a meeting to discuss...

Eventually you come to reconsider your perspective. Did we really need a map, you ask yourself. Doesn't it seem like things are fine as they are. I should spend more time learning to climb trees and swim better.

Over time you think that probably you were wrong about the map and compass. It was your arrogance and vanity that made you believe in them as of some vast importance to the expedition. While you suppose that in some ways your solution was best, you start to reason that climbing and swimming and mountaineering are all excellent for building stamina, and for overall health. While no-one mentions it explicitly, you think it is probably really for this reason the group do not use the map and compass, or some other similarly important reason, probably something complex you don't fully understand.

As you accept this way of thinking you become more accepted as a part of the expedition. You still hear from time to time of other expeditions in other places, who have a map that works. When this happens you feel a deep, subtle sadness that seems to pervade your being. Yet it is better now that you no-longer believe in maps and compasses. It is better now. It is definitely better.

One night you go wandering a fair distance from where you were camped, following your map. Several hours later you return. You followed every direction on the map and it led you exactly where you needed to go. Probably there is very little to be gained from telling anyone about this."