Nikola Đuza Avatar

Nikola Đuza

GitHub pragmaticpineapple.com

Sneaking custom HTML & CSS in to your GitHub README

Nikola Đuza lays out a way you can customize your README to stand out from the crowd:

GitHub supports adding HTML in Markdown, but it is pretty aggressive when removing HTML that can be potentially dangerous to users. Things like scripts, iframes, and similar will get removed or “silenced” to avoid malicious content from being served to users.

Luckily, there’s one way to sneak in some HTML (or a web page) inside the README. You can do it via SVG and foreignObject SVG element.

Sneaking custom HTML & CSS in to your GitHub README

tmux pragmaticpineapple.com

Gentle guide to get started with tmux

We’ve all heard tmux is a great tool to have in the command line. But I never wound up learning it. Last week I found time and sat down to finally apprehend it.

In this blog post, I describe how to easily get started with tmux and what to look for. It is a great guide for beginners (like myself), but also for advanced users who want to refresh their knowledge of tmux basics.

Vim pragmaticpineapple.com

Improving your Vim workflow with fzf

Did you know that this fuzzy finder - fzf, can do a lot more than you thought? Oh yeah, the fuzzy search is just the tip of the iceberg here. It is like wine; the more you leave it on your computer, the more flavor and sweetness it accumulates from that command-line. Let’s dive in and find out how you can increase your productivity with fzf inside Vim.

Vim pragmaticpineapple.com

Why learn Vim in 2020?

Nikola Đuza makes a compelling case for the powerful text editor that developers love (or love to hate):

What Vim is excellent at is navigating, making some changes, and repeating the process. The process most call editing (not to be confused with writing). Most developers tend to overlook this fact, but this is one of the strong selling points of Vim. Developers are more prone to reading code, jumping from file to file, making small incisions in the code, and writing code all the time.

JavaScript pragmaticpineapple.com

Don't follow JavaScript trends

How’s the saying go? Choose well-understood, “boring technologies”…we often reach for the new and shiny just for the joy of tinkering with something.

Psst, I have invented the time machine (don’t tell anyone)! Let us quickly travel back in time to 2016. SWOOSH! We are there. JavaScript landscape looks like this:

If you are using a JavaScript framework or want to use a framework, Angular.js is probably something you would choose. But, the news about Angular 2 that will make you rewrite almost everything is just around the corner. Also, this new kid on the block - React.js is coming up and getting ripe. Of course, Vanilla JS and no-framework-folks are there. Not using a framework is still a popular opinion in 2016, but is slowly fading.

Knowing all this, what would you do? Which path would you choose and why?

Player art
  0:00 / 0:00