WordPress, Ads and Yak Shaving

Since I started blogging 1,5 years ago, I have been struggling with the WordPress.com platform I’m using. The main reason for this is that it injects ads you have no control over if you are using the free plan.

People who follow me and read my stuff know that I am very critically against ads and the whole attention-based industry and this attitude has been reinforced during the past years. In fact, I highly suspect the way ad-driven platforms like youtube or facebook are built support and even encourage radicalization, therefore adding to the growing toxicity, hate-speech and even hate-crimes of our time.

Nonetheless, I had no clue where this blog would lead me to when I started and I am generally rather hesitant to spend money on media and tech (sounds strange, but that’s me).

There are also some minor things that annoy me once in a while, though for most things I have found workarounds meanwhile.

I read some things about static site generators during the last year and the possibilities and advantages really made me curious. It promised more flexibility, more customization, learning opportunities for modern tech tools and also a possibility to get my values more in line with my actions: avoiding advertising.

However, moving a blog to a static site is a huge amount of work and there are many very convenient things I’d lose or have to invest even more time and work to get them back.

Continue reading

#100CodeExamples – Test updatable views with utPLSQL Cursors

We already looked at utPLSQL’s cursor comparison with user-defined types. If we have to deal with updatable views, we can use an even simpler approach and create nested table collections from %ROWTYPEs.

The scenario is similar to the previous one: we have a number of planets with or without garrisons. Now we want to be able to update the view with a garrison-ID which then automatically creates a new garrison-entry.

Continue reading

#100CodeExamples – Constants in PL/SQL and SQL

We often deal with the same things in several places of our codebase, be it names, IDs, codes or something similiar. Problems arise when we write them slightly different, which we often don’t notice because it won’t create a compiler error.

Additionally, these things should often not be changeable once set, therefore most programming languages provide CONSTANTS.
PL/SQL does so, too, but to get these constants into SQL can be a bit tricky.

Continue reading