Developed.be (Uitgewerkt) Archives - developed.be

If you use the debugger in PHPStorm, there will be browser icons in the top right corner of the code editor. I found these distracting and unnecessary.

To remove them:

  • Go to menu File > Settings > Tools > Web Browsers
  • Uncheck “Show browser popup in the editor”
  • Click “Ok”

The dutch tv-documentary Digital Memory Loss (Tegenlicht, Digitaal geheugenverlies) handled some interesting topics concerning the loss of libraries and internet data.

To sum things up:

  • Because of budget cuts, the dutch government destroys some of its own libraries. The information in these books (some of which are centuries old) gets lost.
  • The counter argument is that “everything can be found on the internet”.
  • But what will be saved on the internet? Every day petabytes are uploaded in the cloud. What will we keep in the future? What if a server crashes or the cloud goes down?
  • Big parts of the internet (1995 – 2002) are already gone. A lot of sites (like fansites) are already offline. Pages are edited or removed in 2 month spans.
  • Initiatives like archive.org try to save the old internet. Archive.org also tries to have a copy of every book every published.
  • Companies like Google also try to scan every book but keep them behind a paywall. Google can remove that archive any time they want without any consequences.
  • Software updates happen constantly; old software gets lost. Data that can only be read by old software gets lost as well.
  • The readers of old data-carries (large floppies, microfilms) are getting very rare. This means that the data on these carries gets lost as well.
  • Digitalizing doesn’t mean it is saved for the future. Digital archives get outdated as well. Once you start to digitize, you will have to perform constant updates to keep the archive alive.

http://www.npodoc.nl/speel.program.44238920.html

That’s cool ey, making websites! Think twice! And if you’re planning to make a career-switch to webdeveloper, consider what you need to know before you can call yourself a webdeveloper. I started this list 5 days ago and new things still pop-up in my head.

Edit: update april 2017. I wrote this post 4 years ago. Things have changed of course. I added some stuff that you now need to know _as well_.

To kick off, you need to know:

  • HTML, well obviously. But there isn’t just HTML there’s also:
    • XHTML
    • HTML5 (please don’t tell me you don’t use <article>)
    • HTML for IE
    • HTML for everything but IE
    • Word HTML ®
    • Any DOCTYPE variation and their behaviours
  • Even if you’re not a frontend-dev you at least need to know some:
    • javascript
    • jQuery
    • jQuery-libs (version 1.7 of course not compatible with 1.3)
    • CSS
    • CSS 3
    • CSS for IE
    • JS Frameworks! Hurray! There’s Bower, grunt, node and other new kids on the block.
      • All you need to do is node install  (so they say)
  • Basic Photoshop knowledge (you will need to alter images some time)
  • Know all about usability
  • But we haven’t talked about the actual specialty: programming!
    • All basic program structures (sequences, iterations, classes, inheritance)
    • Keep CPU, disk iops and RAM in mind. Performance is very important.
    • A handful of design patterns
    • And of course some UML or other analysis tools
    • You shouldn’t, shall never and won’t use any goto’s
    • You must master the tools you have to program with.
    • Separate concerns
    • You are able to arrange cultural settings (the current time is: Mercredi octobre 19 22:05:12:4854 +05:00 GMT with daylight saving time)
    • Know regular expressions and how they don’t behave the same in every language.
    • Character encoding (UTF8, ascii, Unicode, Latin-types, url-encoding, html-encoding)
    • Encryption algorithms
    • Refactoring “a monster”.

Continue reading “What you need to know to be a webdeveloper, and how crazy you must be”…

When installing the combo php5-fpm together with Nginx or Apache, you might run into this error:

[error] 4942#0: *1 connect() failed (111: Connection refused) while connecting to upstream, client: 127.0.0.1, server: example.com, request: “GET /phpinfo.php HTTP/1.1”, upstream: “fastcgi://127.0.0.1:9000”, host: “example.com:80”

This is actually not an nginx error but a php-error. Nginx tries to contact php5-fpm, but fails in doing so. This is because it’s probably not running, or because the configuration is wrong.

Check if it’s running

To troubleshoot this, test if fpm listens on 9000. You can do this with telnet.

telnet 127.0.0.1 9000

Alternatively:

sudo netstat -tlpn | grep :9000

Telnet should return “Connected to 127.0.0.1”

Netstat should return a line starting with “tcp” and ending with “LISTEN”

Troubleshoot

If it doesn’t return anything or if it returns an error, it’s because fpm is not listening on port 9000. To solve this:

sudo gedit /etc/php5/fpm/pool.d edit

edit the line that says “listen = ” to:

listen = 9000

Then restart fpm:

sudo /etc/init.d/php5-fpm restart

You don’t even have to restart apache or nginx. It should work right away.

This blog has been renamed to developed.be.

I was looking for an English translation for my blogs’ name, but the literally “worked out” or “working out” is more associated with sports than with developing. Another translation “finished working” doesn’t cover it either.

But here’s the thing: the English translation was so, so, so evident I was unable to see it.

DEVELOPED! And the domain name for Belgium was still available. Hah!

All links to uitgewerkt.be will keep working.

I used to blog on Uitgewerkt.be since 2004, but unfortunately it got in the hands of a domain pirate when I was no longer interested. Seems now that the pirate has given up, so the domain was back for sale. Instead of paying a greedy wolf hundreds of euros, I paid €6.05 to an honest domain agent.

Back to the Minibits-theme

I searched through hundred lists of “best minimal WordPress themes” but couldn’t find a theme that met my expectations better than Minibits by the Italian creativebits.it, a theme which I’ve been using ever since. I tweaked it a bit, and it will continue to be the template for this blog.

To turn this all into the following tech related article: