Fredrik Sjöstrand
Fredrik Sjöstrand
@fronkan.bsky.social
Software engineering, ML and data in general, but python in particular! very occasional blogging at: http://fronkan.hashnode.dev. Storing code at: http://github.com/Fronkan.
69 followers142 following66 posts
While I built multiple applications and packages at home and work, this is the first time I pushed something to pypi!🥳 It was inspired by this episode of @pythonbytes.fm: pythonbytes.fm/episodes/sho... Where Michael said someone should build a package based on a blog post covered. Well here we go!
Testionary (test-dictionary) is a tiny package that provides a dictionary subclass that allow you to track which keys has been accessed and modified. Available on pypi.org/project/test... github.com/Fronkan/test...
Testionary (test-dictionary) is a tiny package that provides a dictionary subclass that allow you to track which keys has been accessed and modified. Available on pypi.org/project/test... github.com/Fronkan/test...
I think this is a really good point from @jamellebouie.net. I find outsourcing the formation of my view on a topic to an LLM a scary proposition. This is also why I'm a bit wary around coding assistants. When am I outsourcing so much of my thinking that it impacts my understanding of the problem?
i just find this so bizarre. searching through texts and doing the reading for myself is how i actually think through ideas! trying to put together a sentence is how i figure out what i actually want to say!
Here is an image of the editor I live coded in 7 minutes using #textual with it's own source code open.
A post based on a lightning talk I had at work a while ago at this point. I live coded a text editor with syntax highlighting in 7 minutes, using Python and Textual. fronkan.hashnode.dev/writing-a-te...
A post based on a lightning talk I had at work a while ago at this point. I live coded a text editor with syntax highlighting in 7 minutes, using Python and Textual. fronkan.hashnode.dev/writing-a-te...
Passing this note along for others. I wrote down some thoughts on how to write better workarounds through comments and tesring a couple of years ago, fronkan.hashnode.dev/tips-tricks-....
All "workarounds" in your code are potential Chesterton's fences. Comment them well or the next guy or gal will tear them down. This tweet as much a "note to self" as unsolicited advice.
Thanks to @willmcgugan.bsky.social and the textualize team for this time. Textual seems to be a TUI library that is second to none, python or otherwise. I'm sad that the company didn't work out, but glad that you gave it a go as textual made me fall in love with the terminal applications
Seeing PEP-735, Dependency Groups, included in the latest version pip makes me really happy! With both uv and pip supporting them I'm pretty sure I can move away completely from requirements.txt 🥳
I would generally agree with this perspective on LLMs. To me the aggressive stance against there usefulness looks more like a counter reaction against the hype. Are they as useful as the hype-side tries to tell you, absolutely not. Are they useless, also no.
There are a lot of critiques of LLMs that I agree with but "they suck and aren't useful" doesn't really hold water. I understand people not using them because of social, economic, and environmental concerns. And I also understand people using them because they can be very useful. Thoughts?
With everything going on and the virality of bad news it's easy to miss the progress happening. Like a person had a mechanical heart for 100 days as a temporary solution until getting a heart transplant. Even being discharged from hospital during that time 🤯 youtu.be/f7cuOS7nmDY?...
After listening to the latest episode of Developer Voices (pod.link/developer-vo...), I installed Nixos in WSL. It looks quite interesting. Also, I love how I can run both ubuntu and Nixos in WSL at the same time.
Been vim-curios for a while. Seems like #neovim with Kickstart(github.com/nvim-lua/kic...) is what I needed to get going😁
Fredrik Sjöstrand reposted
Fredrik Sjöstrand reposted
Fredrik Sjöstrand reposted
Hi everyone, Just to announce that the handle bsky.app/profile/nico... is not Bruno, but an impersonator. That account has already been reported. Bruno can be reached at bsky.app/profile/soli....
This is probably a pretty good tip for me 😅 Although I don't have nearly as much time to write nowadays, that draft folder has been growing. And published content sort of hasn't
Oh, I forgot to mention: lower your standards! Waiting until a piece feels as good as you can get it is a recipe for an empty blog and a huge folder full of drafts I try to hit publish while I am still unhappy with what I've written
I don't know if it's by coincidence or the all-knowingness of the algorithm. But this video popped up in my feed and I really resonated with it. "Complexity homeostasis" is an interesting idea and feels like a valuable concept youtu.be/czzAVuVz7u4?...
Fredrik Sjöstrand reposted
I just want to add that this doesn't make me a die hard fan of DRY (Don't repeat yourself). While generally pretty good advice, it can also lead to you implementing the wrong abstractions. This often manifest in functions with different modalities. I personally like WET (Write everything twice)
I will see how many days I will get through this year, I don't imagine it will be that many. But, I did the first day of Advent of code at least 😊
For anyone coming across the "ghost engineer" stuff, this is a great take on it. One key thing, currently there is no published paper on the actual ghost engineer things, only a code quality metric predictor thing that they seemed to use for it. Very important difference. youtu.be/_a_Vz2ytVCQ?...
While we need to wait for the paper to know what they actually did. It seems to use commits which can quite easily miss a lot of important engineering work. Also if they want to come at us with statistics lets throw this one back at them 😉 youtu.be/42QuXLucH3Q?...
@podsnack.se has now allowed @lawik.bsky.social to BEAM 🤭 elixir into my ears so many times that I can't resist the temptation. Don't tell Python 🤫