Profile for zlatko
About zlatko
Fields
- website
- https://zlatko.dev
- some photos
- https://pixelfed.social/zlatko
- some more photos
- https://photos.zlatko.dev
- 52frames photos
- https://52frames.com/photographer/20340
- Gravatar
- https://gravatar.com/zladuric
Bio
According to some, I'm avant-garde ;)
I try to stick to software development and engineering topics, often related to application development, but I also shitpost random stuff, occassionally about photography, (usually not more then) react to politics or economics.
My website is https://zlatko.dev but I less completely-infrequently post a photo or two to my photo gallery https://photos.zlatko.dev.
I also used to post at https://pixelfed.social/zlatko, and https://programming.dev/u/zlatko, and I'll occassionally swipe here and there.
Stats
- Joined
- Posts
- 2311
- Followed by
- 161
- Following
- 316
So you're saying Rust isn't the fastest?
AI can't generate images of a stopwatch with hands at 0:00 or sand clock with sand expired.
Decissions, decissions
#filmPhotography #analogPhotography #photography #film #ilford #kentmere #kodak
Kudos to this guy Brian on youtube explaining something about a camera: "If you'll forgive state of the art graphics that I use on my channel, nonetheless, this should be sufficient. I don't know why everybody spends so much money on these g-whiz graphics for their youtube videos" and proceeds to draw in his notebook.
I mean, he did try to explain an analog, film camera viewfinder, there's no easy way to record this. But his explanation with pen and paper and the camera itself worked beautifully.
After surveying the whole mountain, I AltGr finally found the rune, now he can go put down that Moder forsaken!
I am so used to CSS resets that I never learned that H1 gets" bumped down a level" (but only visually not semantically) for each <article>, <aside>, <nav> and <section> it is nested in.
But it's fine living in ignorance, since they are removing it.
#css #html #h1 #toNestIsTheBest
Funny thing at work, I was handling some legacy users - we need to make sure that on the next login, if they have a weak password, they have to change it.
So the whole day I'm typing "123" as a password, 123 123 123 123 all good. So finally I'm done and now I'm testing it, and accidentally I type 1234 instead of just 123. Doesn't really matter, either is "weak", so I just click "Login".
Then goes Chrome, "1234 is known as a weak password, found in breaches, you should change it".
So TIL 123 is still good.
Screw writing tests, I'm just gonna go and delete half my code. I'll continue doing so, to just binary-tree my way to the bug I'm trying to figure out. It'll be fast.