Full Width [alt+shift+f] Shortcuts [alt+shift+k]
Sign Up [alt+shift+s] Log In [alt+shift+l]
47

BSL is not good, it's great

from Ognjen Regoje • ognjen.io [alt+shift+b] in programming

Another day, another project adopted BSL. Another day, another round of outrage from people harping on the difference between Open Source and open source. Another day, another inferior fork of a product due to a technicality that has nothing to do with the product itself and that will not impact the vast majority of users. Another day, another business built on a platform they don’t control with no contingencies should that platform become unavailable. Is it outrage purely on principle? Is it really useful to fork a project and have it perpetually limp behind the original but with the one true licence? Is it genuine surprise that re-packaging a product that belongs to someone else might not be viable long-term and needs contingency planning? I don’t know. I do know, however, that BSL is not good. It’s great. It’s helping keep open source projects alive and providing a way for its creators to move from being just “indie open source devs” to successful business owners. New open source software is probably being made right now, specifically because if it becomes popular the creator knows they might make a business out of it. BSL makes open source a viable career path. What’s not to like? What’s there to be outraged about? BSL is not good, it's great was originally published by Ognjen Regoje at Ognjen Regoje • ognjen.io on September 02, 2023.
1st Sep 2023

Stay updated

Get a weekly newsletter with the top 5 articles worth reading every week.

More from Ognjen Regoje • ognjen.io

All conference talks should start with a small technical glitch that the speaker can easily solve

At a conference a while back, I noticed a couple of speakers get such a confidence boost after solving a small technical glitch. We should probably make that a part of every talk. Have the mic not connect automatically, or an almost-complete puzzle on the stage that the speaker can finish, or have someone forget their badge and the speaker return it to them. Maybe the next time I, or a consenting teammate, have to give a presentation I’ll try to engineer such a situation. All conference talks should start with a small technical glitch that the speaker can easily solve was originally published by Ognjen Regoje at Ognjen Regoje • ognjen.io on April 03, 2025.

2nd Apr 2025 • 51 votes
A review of the blog in 2024

I didn’t write much this year. The projects that I worked on (at work) used up most of my creative mental capacity leaving little for writing. The backlog is brimming, however. Targets for 2024 ❌ Publish at least 40 posts 11 ❌ Reach at least 200k readers Don’t have an accurate number ❌ Have at least 6 posts on the front page of something Probably would have met this if I had posted more – I had one successful post on Jan 14, which is encouraging ❌ Make at least $50 from writing. Nope, did no monetization whatsoever Breakdown Some stats: Number of posts: 11 Total word count: 3125 Longest post: When am I “allowed” to quit and not be labeled a quitter? (630) Shortest post: Speaking at Hasso-Plattner-Institut (0, because it’s just a link to a LinkedIn post) Breakdown by category: business: 1 startups: 1 ethics: 1 robots: 1 architecture: 1 interviewing: 1 productivity: 1 selenium: 1 doctolib: 1 No trend there. Feedly still reports 18 followers - no movement. But it also marked the blog as inactive which is a shame. Targets for 2025 I would like to commit to writing more in 2024, but I’m not very confident that I will have the time. Regardless, the 2024 goals were quite lofty but achievable so it makes sense to try them again Publish at least 36 posts (3 per month) Reach at least 200k readers (not sure how to track this accurately since I’m not keen to add analytics and GoAccess doesn’t seem to be super accurate) Have at least 6 posts gain traction (front page of HN, 10 reactions on LinkedIn, etc) A review of the blog in 2024 was originally published by Ognjen Regoje at Ognjen Regoje • ognjen.io on January 01, 2025.

31st Dec 2024 • 102 votes
Green flags for investable founders

Here are a few things I’ve seen founders do that made me confident in their ability and dedication. Elevator pitch in LinkedIn tagline A founder who is all in is constantly selling. That means their tagline will: a) be for their company, not for them b) be the sales pitch, not a vague aspirational vision Value proposition keeps getting more specific If every time you talk to a founder and their value proposition is more and more specific to me indicates that they’re learning more and more about their USP, about their target customer, about the market. The opposite of this is a company that pivots every six months. No short stints in the CV Building a startup is decidedly a marathon. I think it takes about 4 years to make real progress in a startup. Folks who jump positions every year are chasing a career and are unlikely to want to slog through for such a long time. Not that there’s anything wrong with that, it’s just not the right profile. Worked at companies of different sizes A founder who’s seen multiple stages of a startup is more likely to be successful. While they might not have been in the top leadership positions they would have seen the challenges the organization faces, especially during the transitions. Worked in different industries, or not There is a difference between the technical and the business founders. The startups I’ve seen where the business founder was part of the industry for a while worked well. But I’ve also seen them get so focused on how things are that they can’t see how things should be. For technical founders, on the other hand, I think it’s a clear advantage to have been in different industries and seen different approaches. Switched to full-time as soon as possible It might be obvious but the sooner the founder goes full time the more skin in the game, but also belief in the business, they have. They’re that much more committed to it. The opposite of this is founders who are simultaneously CEOs of multiple companies. I don’t think that can ever work – least of all for startups. Don’t succumb to the hype The founders who aren’t always talking about how they’re going to incorporate the latest hype in their product seemed to get more accomplished. Founded, or was an early employee, of a startup that raised a round or two I think this is probably the biggest indicator. Having done the early stages, seed and maybe series A, eliminates A LOT of uncertainty. At least the company won’t fail because the founders aren’t competent at running a business, since they’ve done it before. I’d even be biased toward someone who did a startup over someone who’s been employed at a name-brand unicorn simply because the skill set is not at all equivalent. Green flags for investable founders was originally published by Ognjen Regoje at Ognjen Regoje • ognjen.io on January 03, 2024.

2nd Jan 2024 • 38 votes
A review of the blog in 2023

2023 was a busy year so I did not spend a lot of time blogging, unfortunately. It was only in December that I had meaningful time for writing. In the 2022 review I set a few targets for the blog in 2023: Targets for 2023 ❎ Publish at least 40 posts 14 ✅ Reach at least 150k readers With a couple of viral posts this is very easily achievable. I’m at 180k even though I only had a few posts. I will include a target for the number of posts as well. ❎ Get at least 10 posts professionally? publicized I was thinking of hiring someone to help me distribute the content, but a) I didn’t produce much of it and b) I didn’t hire anyone. ❎ Build an audience (recurring readers, Twitter, newsletter?) Did not do this at all. ❎ Publish something on at least two other sites Did not do this. And I think I will not focus on this going forward. Quantity I published 14 posts, totaling approximately 9700 words. The average blog post length is 695 words. Working on legacy code is the longest post at ~729 words, followed by Lie still in bed with 679. The sample size isn’t sufficient to comment on whether the average length is adequate. Popularity Lie still in bed was the most popular substantial article. That’s encouraging because it’s not about tech, it’s just generic advice. MIT No AI was fairly popular but got flagged on HackerNews which killed it. It was also very quick to write. Interestingly Reddit’s disrespectful design and Big tech should help tackle misinformation on smaller platforms made a comeback. I don’t have detailed tracking anymore, it’s all based on server logs, so I can’t dig deeper into where the traffic is coming from. Editing the source markdown of a generated static site in the browser had some traffic as well which is interesting. It’s probably the most interesting post I wrote in a long while. Feedly reports 18 followers. Up three. What I’ve learnt I think I got better at writing more clearly. I’m more comfortable, at least at the moment, with publishing posts and not worrying too much about whether they’re perfect. I think that’s at least partly because I wrote so many posts in December. I made one pass with the rough draft. Then another pass that finalized the content. Then a final one where I didn’t change the content but just proofread and ensured clarity. Then I published the post. I took to heart the 2022 objective to frame posts positively more positively and have done that for several of them. Targets for 2024 Publish at least 40 posts Reach at least 200k readers Have at least 6 posts on the front page of something Make at least $50 from writing. I’m not sure if this is a good objective but maybe it might motivate me to think of monetization alternatives. A review of the blog in 2023 was originally published by Ognjen Regoje at Ognjen Regoje • ognjen.io on January 01, 2024.

31st Dec 2023 • 38 votes
Not wanting to work remotely is now a competitive advantage

As much as working remotely is a competitive hiring advantage again, not wanting to work remotely is now an advantage for getting hired. A lot of companies are mandating returns to the office. Many more are scrapping fully remote positions, with some even rescinding fully-remote offers. So, for better or worse, not wanting to work remotely is now a competitive advantage. If that’s not one of your requirements you’re likely to pick up more offers. Not wanting to work remotely is now a competitive advantage was originally published by Ognjen Regoje at Ognjen Regoje • ognjen.io on October 15, 2023.

14th Oct 2023 • 41 votes

More in programming

George Dryden

Reading my recent computing retrospective, I realised there was a big section missing: the people in my life that made an impact and helped shape my career. Outside my immediate family, one person made an outsized contribution, and I’m fairly certain that without his influence my life would have taken a very different path. The fact that I’m still here in 2026, still writing code and being fortunate enough to have a career in something I love is testament to him. So I’d like to take a few moments to talk about my old secondary school teacher, George Dryden. Denied Back in 1995, I had a problem. I knew I wanted to study computing at university and build a career out of my passion, but there was a snag. For those unfamiliar with the UK schooling system, when you’re 15-16 you take a set of GCSE exams in a broad range of subjects. After that, you pick around 3 subjects to really focus on over a period of 2 years. These are called A Levels, and they are a big step up and are meant to prepare you for a degree-level course at university. Admission to university is also governed by these results - if you want to study computing, you’re going to need a computing A-Level, and most universities will only accept you (or “make an offer”) if you achieve a certain grade. And whilst I had taken computing at a GCSE level, my school did not offer a computing A-Level course. I instead had to settle on “Design & Technology”, which just didn’t inspire me. Instead of working on my portfolio and projects, I spent most of my time daydreaming and writing code on the Acorn Archimedes computers that were the staple of every 90s UK school. No disrespect to the teachers - they were all awesome - but it just wasn’t for me. I was miserable, and by the end of my first year, I was well on my way to failing outright with my entire future plans seemingly going up in smoke. Someone noticed That’s when George stepped in. He’d taught me computing right the way through my GCSEs, and with no A-Level course on offer, that was officially where his involvement was supposed to have ended. It didn’t. He had noticed my constant presence in the computing labs - before and after school, during lunch breaks, free “study” periods - working on some little pet project or digging into RISC OS internals. I remember him as warm, with a wicked, dry sense of humour, and a refreshingly spiky attitude to authority - I always got the sense he’d worked out for himself which rules were worth taking seriously and which ones weren’t. And he always had time for me. I spent years pestering him with questions that had nothing to do with anything on the syllabus, and he’d always find a way to answer them that actually made sense. He was just as supportive of my odd little obsessions. At one point I’d got deep into the BBS scene, which I thought was the coolest thing ever, and decided what the school really needed was an internal BBS running on its own network. So I wrote one. It was deeply cringeworthy, obviously - but George helped me put posters up around the school advertising it, and even gave it a mention in assembly one morning. I think about five people in total ever checked it out. It didn’t matter: a teacher had stood up in front of the entire school and treated my weird little project like it was worth something, and that was a hugely validating moment for me. Off the books He recognised the passion, and eventually he made a suggestion: What if I quit the Design and Technology course, and instead attempt the A-level course myself? Personally, I also suspect he was enjoying himself. There was some internal school politics behind why computing wasn’t offered at A-Level in the first place - I never knew the details - and I think the prospect of one of his students simply going out and getting the qualification anyway appealed to him on two separate levels. It would get me where I wanted to go, and it would wind up exactly the right people. It wouldn’t be easy, he warned. The school would be against it, plus it was a two-year course which I’d have to cram into one year. I’d have to do it all myself - studying, lesson planning, coursework - he couldn’t help me in an official capacity, but he said he’d advocate for me and help where he could. If I had assignments, he’d send them off to be graded and would give feedback in his own time. He’d enter me in for the exams and also gave me a set of keys to the computer lab so I could use it whenever I needed. It was the first time anybody outside my own family had really shown faith in my abilities and encouraged me to take a stand. It was a pivotal moment for me - I realised if I wanted something badly enough I would have to fight for it, but I could still make it happen. I didn’t have to take “NO” for an answer - a lesson I think I picked up from watching him as much as from anything he ever actually said to me. After a few weeks of dithering, I took the jump. I remember a few awkward meetings with the school administration but thanks to his behind-the-scenes work, I was soon following my dream. An intense year And yes, it was bloody hard work. I had to condense an entire two year course into under a year, be disciplined enough to produce my own study plan, and be critical enough of my own shortcomings that I could focus my study where it was needed. I pretty much lived and breathed it for months straight and was more-or-less a permanent fixture in the labs or school library poring over my course books. I’d make lists of questions and chat to George over lunch, and he’d provide guidance and encouragement. It was a lonely way to learn with no classmates to compare notes with, no lessons to turn up to, and right up until the end I had no real idea whether any of it was good enough - but bit by bit, it started to feel like something I could actually pull off. And sure enough, in the late spring of 1996, I sat down in an exam hall with my fellow students, the only one with an A-Level computing question paper in front of me. The final exam went by in a blur - I can only remember a few of the questions now (and a peculiar obsession with the Pascal language) - but I do remember the euphoria as the invigilator called “time’s up, pens down, close your papers NOW”. I had done it. A few nerve-wracking months later, my Mum drove me into school to pick up my results. I ripped open the envelope and saw it - I’d passed with an A grade! I literally ran up the stairs to George’s office next to the computing labs to thank him personally. I’d taken my camera into school to take a few last photos for memory’s sake and snapped this photo of him before I walked out the school gates for the last time: A different path Because of him, I managed to get into my university of choice, studying computing with a focus on networks. Because of that, I landed my first job working as a “webmaster”, and my career since has been one of the highlights of my life. All these years later, it’s a real privilege to be able to get up each morning and actively look forward to working in an industry I love. Without George stepping up for me and encouraging me to believe in myself, none of that would have happened. I wouldn’t have had the career I have, and I wouldn’t be where I am now. I met my wife when we both worked at a software company - she sat at the desk behind me - so even my home and family life can be traced back to that spring of 1996. And the A-Level itself was only half of what I took away from that year. The qualification opened the door to university, but the lesson that came with it was every bit as important: that a “no” isn’t always the end of it, and that sometimes the answer can be argued with. I’m so proud of what I managed to achieve all those years ago, and even more thankful to have had someone like George in my life to put me on the right track. Mr. Dryden I did see him again after I left. He drank in one of my local pubs - a pub I’d been going to for a good while before I was technically old enough to be in it - and I’d say hello if I spotted him in there, mostly in the months before I moved away to university. After that it was only a handful of times. For years I’d find myself scanning the room whenever I was back home and in for a pint, half expecting him to be at the bar. At some point I stopped seeing him altogether and eventually moved across the country. The trouble was I never really knew how to talk to him outside of school. He was always Mr. Dryden, or just “Sir”, I don’t think I ever once called him George to his face! I was (and still am if I’m honest) fairly socially awkward, and I never worked out how to phrase the thing I actually wanted to say: that he had changed the entire direction of my life, and I wasn’t sure he knew it. So instead I’d say hello, and ask how he was, talk about nothing much, and go back to my friends. Epilogue Sadly, 3 years ago now, I opened the latest issue of my old school alumni newsletter to read that he’d passed away. The photo at the start of this article was taken from his obituary article and I read that he’d had a long illness and had suffered from dementia at the end. I did write to him years ago by email - I don’t know if he ever got it, or was in any capacity to understand what he’d done for me, but I hope so. There’s an old saying by one of my favourite authors (Terry Pratchett) that “no one is finally dead until the ripples they cause in the world die away”. In one of his books, a character keeps the memory of his son alive by passing his name along a series of telegraph towers. It’s in that spirit that I’m writing this post - I debated it for many years as it’s very personal to me and I also have no contact with any of George’s family so I have no idea what they would make of it all. But even though it’s 30+ years ago now, I will never forget him or what he did for me - and at least now, if someone searches his name it’ll be recorded here for as long as I’m alive and running this site. Thank you, Sir. George Dryden 1942-2023

8 hours ago • 1 votes
How Copy-on-Write Works with Memory-Mapped Files

Let’s step inside the kernel and understand how it implements copy-on-write and what are its implications for the performance of user-space systems

8 hours ago • 1 votes
If we do not stop to help each other, what do we become?

Yesterday, I received this email as a response to You Can't Vibe Code Love. It's such a remarkable and powerful statement that I asked permission to share it here, in its entirety, with personal information redacted: Hey Jeff, Hope you and your family are doing well.

2 days ago • 1 votes
You are still valuable

A frustrated Reddit post about being a condom between an AI and production made the rounds in our team. Here is why I think the opposite is true and what it means for how we review code, plan work and think.

3 days ago • 2 votes
A Short Update on Designing for Foldable Devices

And here we are three years after I wrote about the Google Pixel Fold being announced, followed now with the announcement of the iPhone Duo...(I have questions about the naming by the way). Four years ago I was talking about web primitives in the platform for the Surface Duo. My how time flies. There are CSS media features, a Viewport Segments API, a Device Posture API but Chromium based browsers are the only ones currently supporting these things. I haven't been able to find any signal yet on whether Safari will support these things in the web platform as the developer docs focus on application development. If you're interested in trying out the platform features, you can emulate the Surface Duo and Galaxy Z Fold in the developer tools. And if you're thinking, do I really have to have my website adapt to two screens? The answer is no. Adding a design to an application or dual screen makes sense if you have an experience that has two simulataneous contexts that are useful e.g. a list of email messages/inbox on one screen, an open message, email thread or email composer on the other. Here's one of my talks from 2022 if you're interested in learning more about what's available in the browser for dual screen/foldable devices. Happy building :)

3 days ago • 1 votes
📚 BoredReading

You seem to be enjoying this.

Join free to unlock everything.

Create free account

Already have an account? Sign in