Thomi Kamilla’s Post

Why read if you can listen? Here I read a paragraph from my latest post. With a tool I just discovered on Substack. The full post is here: https://lnkd.in/duqhisti

This is a little blog post I wrote on the small yet intricate process of what happens when you type “google.com”

When you see stack overflow questions, you should not only look at the answers 🧐 Instead, look at how they arrived at their problem, then see how they break down and arrive at the answers. This will help you manage other similar questions in the future! 💫

This post will automatically share

The latest MIT Technology Review takes a closer look at Marietje Schaake’s #TheTechCoup and #TheVentureAlchemists, bringing a critical lens to how both books debunk myths about Silicon Valley’s most influential entrepreneurs while challenging us all to rethink their dangerous impact on democracy. #BigTech’s rise to unprecedented power isn’t just about innovation or higher profits — this review argues it’s about the individuals behind it, the choices they’ve made, and the costs we’ve paid as a society. If you want to understand how we got here (and how we might begin to take back control) then this review is a great place to start:

Resolutions? Maybe We’re Doing It Wrong. Why do New Year’s resolutions feel more like chores than fresh starts? Read more on our substack. Link in the comments.

Very concise, and I pretty much agree as a rule of thumb. It does seem like, though, that many folks have gone too far in the anti-DRY direction. Seems like a pendulum/faddish type thing to me—and it’s less effort to not even try to think through if DRY is appropriate. That is, it is tempting in the wrong way to embrace a carte blanche to just code away solving the immediate problem in front of one’s nose with little thought for the future. I also think that the longer you make software, the better you get a sense of when an abstraction is more or less likely to serve you/the organization, even if no duplication exists at the moment. Nobody bats 1000 in such prediction, but it can be worth it to invest in it up front when the spidey sense tells you it’s probably a good idea to potentially save high cost refactoring/redesign later. It depends on perceived future impact/cost vs added near term dev and complexity cost. DRY is still a valuable principle. Just don’t overdo it or default to always making abstractions. Personally, I’ve run into far more messy code that is painfully resistant to maintaining/updating in the needed way than I have run into “over-engineered” or needlessly abstracted code. YMMV, but I recommend avoiding being dogmatic either way. https://lnkd.in/e-kegrcd

Two books explore the price we’ve paid in handing over unprecedented power to Big Tech—and explain why it’s imperative we start taking it back: https://trib.al/d0FtUYG

Check out this 5 Star Google review!

Half baked idea: Chaos Doc Below is a link for a mostly blank Google doc. Anyone can view, anyone can edit. If this is like most of my posts, this will get 5k - 25k views. Go in and put whatever you want random people to see. Use it for whatever you want. https://lnkd.in/gRWMtYp3