Well, I love it.

After a month of coding in Go again, I realized that something has changed (everything changes at every moment) 🙏

Maybe I'm getting dumb from moving cards in Jira?

Maybe otherwise, and I've learned a whole bunch of thinking, but anyway, there's no way I will use Go as my general-purpose language.

The things I admired in the past now make me feel awful while coding, as if I am in a gnarly prison 😩

Well, then there is simply no choice except to get more furry, but not now.

Cos It will be much better to focus on one thing at a time (at least in learning), and become better in it.

Good evening, ladies and gentlemen.

I bring you some good thoughts on information (or data, whatever) redundancy,
and this is far from being about database denormalization.

Please take a peek and lemme know what you think about it in the comments.

Click me, come on!

Love you all 😊

Hello, everybody, everywhere!
I hope you’re all doing well and staying healthy.

Here is my fresh post about conditional statements, especially about how to write them less.

CLICK ON ME

Please, lemme know what do you think about it in the comments 🙂
Cheers 🙏

Check it out: https://www.philipzucker.com/state_o_knuck/

The dude is adopting Z3 solver for Python 🕺

So far, its quite promising.
Hopefully, it will continue to thrive 💪

🔤🔤🔤 🔤🔤🔤🔤❗️

What happened?

Why am I writing about soft skills?
Did I get bitten by managers?
Or was I always infected, because we’re all the walking dead already? 🔨

I don't know. It does not matter.

Well, the text is about being a precious, irreplaceable player.​

Read here. 🕵️‍♂️

Hello, hello!
Still alive, even after a 1.5-day local AI Hackathon I smashed on my head 🔨 (MVP is actually done, btw.)

I want to share a short note with you today about a terrible mental slippery slope that might just ruin any system if it’s not spotted soon enough.

The post also contains a hint on a great approach on how to spot it.

Happy reading, it’s short, really -> linky-linky 🔗

Good day, colleagues 😑

No one writes perfect code, especially the new o1 model 😳

Bugs have always existed,
dormant bugs are always lurking,
and they will be with us for some time in the future.

As well as debugging.
I wrote a bit about this -- feel free to read and enjoy, or hate, whatever 🌟

🔗LINK 🔗

https://fabric.so/ is complete dogshit 💩

The guys are drastically wanting your money and selling their product like a charming “one place for your notes and documents.”
Well, while they did a kind of good integration with some LLM for linking and summarizing your saved notes, documents, and links (linking “similar” stuff also works acceptably every other time),

I just encountered a horrible bug where the desktop Fabric app did not save my text note. 😢

I’ve been working on a new blog post for a couple of hours within its notes text editor, finished a big section, and boom, everything’s gone 🙂

Just becuase of that, no matter how good they integrated AI features - it is the dogshit 💩
Why? Because it is unnacaptable what such a critical and fundamental functionallity is not working propperly.

Well, at least they reacted pretty quickly to my bug report on Discord.

You know what? My note might not have been saved BECAUSE I DID NOT CLICK THE SAVE BUTTON INITIALLY, RIGHT AFTER CREATING THE NOTE!
Moreover, the developer mentioned that something similar happened to one of their team members a couple of weeks ago:

it does indeed sound pretty bad - the reason I asked about the Save button is it happened to somebody in the team a week or two ago, they did not click Save and so the content was wiped when they closed the modal; in which case it would be a UX problem more than a true bug (not sure what the case is for yours, and we are going to look into it)

They tried to restore something, but would it be surprise if I will say that nothing was restored?

lmfao