More from Ognjen Regoje • ognjen.io
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.
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.
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.
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.
More in programming
Google told K-12 schools they could turn off AI, but only if they gave up search too. That isn’t integration. It’s holding education for ransom.
Once a year at my church, I usually give one sermon. I was asked to tie the theme to a young adult retreat we had taken to the Sunshine Coast. My first experience giving a sermon was many years ago at my old home church in El Monte, California. It was a Vietnamese-American church, but…
Practical tools for design engineers to explore possible futures through speculative design
As with my last post on AI, let me open with a statement: Just because most people hold AI a certain way, doesn’t mean that we always must, either now or in the future. As I noted in that piece, and my shades of gray post, I am well aware — and agree with — … Continue reading Must we always use LLMs this way? →
The CSS Working Group resolved to use cursor: pointer for buttons and other clickable form controls in the new appearance: base styles. That happened on October 21, but I posted about it yesterday and, uh, people have feelings about cursors. I wrote about buttons and cursors back in 2022, when a post titled "Buttons shouldn't have a hand cursor" was making the rounds. I admitted I didn't have a strong opinion either way, then argued that not using the hand cursor had become the new anti-pattern anyway. The web isn't an operating system, and people expect clickable things to show a hand. The issue is Cursors For Base Appearance in CSS Forms Level 1. The group adopted the rules from this comment, and the part that's triggering half the Web is: select, option, input[type=checkbox], input[type=radio], button, input[type=button], input[type=submit], input[type=reset], input[type=color], input[type=image], ::file-selector-button { cursor: pointer; } It seems like we have a tabs vs. spaces sort of debate. Again. Nicole Sullivan pulled cursor data from a bunch of design systems and, in September, 27 of the 33 systems that set a cursor used pointer. After she added more systems, it was closer to a 50/50 split. Elika Etemad made the usability case in the meeting. Per the minutes, she said the hand "makes it clear, as soon as you're hovering an interactive control, you're supposed to click on it," and called it a "usability benefit even if not historically done on some platforms." "But the hand means it's a link" Haz had an interesting reaction: The debate is over, and evil has won. His point is that he can't tell whether ⌘-clicking something will open it in a new window anymore. He feels more confident clicking a button when he knows it won't change the URL, like when it just opens a popover or a panel. He's not wrong about that.* I replied that I've been on team evil since 2022 (albeit without a strong opinion, just following what users seem to expect). Touch screens don't have a cursor at all, and on desktop, browsers show a link's URL in the corner when you hover it. That's some type of hint, at least. Haz pushed back that he'd have to watch the bottom-left corner with his peripheral vision, which is fair. He also said he never cared which cursor buttons got, he just wanted links to have their own. I can appreciate that. "But desktop apps don't do it!" Jacob Paris liked the standard cursor on buttons because it makes web apps feel more like desktop apps than websites. My opinion hasn't changed, though. People have already learned that a hand cursor means clickable on the Web. It's by no means mandatory, but it's familiar and satisfying, so it stuck. Either way, nothing changes today. The resolution only covers appearance: base, which browsers haven't shipped yet. Buttons and selects still use appearance: auto, and their cursor is still default. If your CSS reset, design system, or web components already set cursor: pointer on buttons, keep it. When appearance: base ships, controls that opt in will get the same cursors by default. But remember, these are only defaults! You can still add whatever cursor you want to whatever element you want. Nobody's gonna stop you. In 2022, I said I'd keep changing the cursor on buttons until there's a good reason to stop. In 2026, I still haven't found one…and neither has the CSS Working Group. *Thinking about this more, if 50% of design systems opted to add cursor: pointer to buttons already, isn't this already a moot argument? **In general, I think the Web should be more personal and expressive so who even cares about a default? This is especially true for personal and fun sites. Just don't go too crazy, especially when it affects accessibility and the overall user experience.