Skip to content

2024

Impatience

A great temptation to get the Mac, because it resonates like it "just works". But it is not true first of all, and this approach encourages sloppy mind.

Maybe the thing about sloppy mind should go as "first of all". You want some new tech toy, but you don't want to make an effort to find the best one for you.

What's the fun then? Unless you trying to find something to get the job done right now - take a time, do the effort. Practice some patience and thoroughness.

Yusuf Dikeç

If you see "install IDE 'fancyshit'" as a prerequisite to any coding tutorial, most likely this is a shitty coding tutorial. Vim, gedit, notepad - any of this is sufficient to write the code. IDE has very little to so with coding per se but in tutorials derails understanding of essential concepts. I do not want automated project structure creation, automated imports, fucking tips. I want to learn why the structure is like that, where that method comes from, what are the dependencies.

Yusef Dikeç at the Olympics 2024

diary record

Si te sientes como un idiota, significa que estás en el camino correcto y debes seguir a pesar de todas las dudas. También podría ser que eres un idiota.

diary record

I listened today to one data scientists' job interview. While answering on how to deal with LLMs' hallucinations, he put it like actually all these models do is hallucinate, and occasionally their hallucinations coincide with reality. That was a good one. AI in a nutshell.

diary record

Ayer fue un dia libre, y pasé enfrente de ordenador solo una hora. El dia sin ordenador - una sorpredamente buena experiencia.

How to ask questions

Bookmark: How To Ask Questions The Smart Way

Before You Ask

Before asking a technical question by e-mail, or in a newsgroup, or on a website chat board, do the following:

  1. Try to find an answer by searching the archives of the forum or mailing list you plan to post to.
  2. Try to find an answer by searching the Web.
  3. Try to find an answer by reading the manual.
  4. Try to find an answer by reading a FAQ.
  5. Try to find an answer by inspection or experimentation.
  6. Try to find an answer by asking a skilled friend.
  7. If you're a programmer, try to find an answer by reading the source code.

diary record

When I was a student, I have written a little program to model a glissade of a descending plane, as a part of some study task. Not a rocket science, still involved an itty-bitty pinch of differential equations, required some effort (and was not fun). That resulted with a thin white line on a black screen.

Anyone seeing it shrug their shoulders, like "ok, nice".

Also I was interested in graphical effects, and I can tell you that modelling flame is a basic arithmetics. Initialize a bottom of your display matrix with random (or you can play with it) colors, then go over every pixel calculating average of values of surrounding ones, and put that result one pixel higher. Looks awesome. Anyone seeing result was like "wow, you're a hacker man!".

Here probably should be some kind of morale but to be honest, I love that flame effect better myself.