Neil Barnwell

@raygyli Interesting that you think vibe coding is the "norm". You think that the majority of software developers on planet Earth are now just typing (or speaking) AI prompts and just trusting the output?

it always takes a while for ppl to accept new generations of tools. for example, it took a really long time for ppl to realize the potential of vibe coding (which is now the norm). gaming studios initially rejected the idea of using game engines, preferring in-house tech, which resulted in slower development time and lower quality. early adopters of new tools win.

@okyrylchuk Mostly I wish C# would stop adding more and more idiosyncratic features like this for me to memorise, that don't actually add much to the language, they're just aimed at reducing typing. I was happy with C# 10 years ago, tbh.

C# 14 in the preview introduces the field keyword. It lets you write a property accessor body without declaring an explicit backing field. The compiler will replace the field keyword with a backing field. What do you think about this improvement?

@mischavdburg I was 1, I tried 2 and loved it until MacOS updates stopped, effectively bricking my £2500 2012 MBP. I became 3 when I tried reviving it with Linux and it's been utterly miserable (e.g. x11 vs. Wayland). I want a tool, not a pet I have to nurture. My next laptop will be Windows.

Poor people accept whatever operating system comes installed. Rich people pay $3,000 for a Mac to escape Microsoft. Smart people learned Linux in a weekend and haven't paid for an OS in 15 years. Which one are you?

@git_fork I don't know if you have a better place to submit feature requests, but just wanted to say that if the Sort topologically/by-date option were a toggle button on the main toolbar in addition to being hidden in File->Preferences, that would be wonderful.

It's been years since I built it, but even though I'm five-nines sure no-one but my company is using it, I've finally actually done a proper readme for my Event Sourcing library, Inforigami.Regalo. Someone new on the team had questions and this seemed the best solution. :)

@beckiandchris Saw your video. Just relieved to see you're both present and okay. You've made a body of work to be proud of, and while I'd love to see the helicopter come home, just focus (no pun intended) on yourselves. Nothing lasts forever - look forward, not back, to your next adventure.

@beckiandchris Glad to hear it, and that you're taking some time for yourselves for a bit. I'm looking forward in particular to the Millenial Falcon coming back, but I've long since "hit that notification bell" so I won't miss it. Ta-rar for now.

@beckiandchris are you guys okay?

@Pinterest Your search is broken. Google Chrome. Searched "scout", got "Sorry, we couldn't find any Pins for this search." Private browser window looked promising but then went into a mad refresh loop. I guess I'll look elsewhere.

@ashic "Just following orders..."

It's quite telling that the narrative on twitter from the right wing has shifted from "Elon didn't do a Nazi salute" to "Nazis weren't really that bad" within a period of 10 days.

@80s_Kidz "OK, Boomer..."

"Can I have your Wi-Fi password?"

@SimonCropp Microsoft.Extensions.Testing.Assertions...

@SimonCropp On the other hand, the ability to test that *unexpected* things *didn't* happen, in addition to checking that desired things did happen, has lots of value, too. I'm on the fence, clearly. Apologies for the stream-of-consciousness.

@SimonCropp I also don't really want to be forced to use a plugin/extension so that I can see why a test fails. A stack trace with a line number of the failed assertion is pretty hard to beat IMO.

Hot take: FluentAssertions is borne out of the manic drive to have the fewest lines of code or characters on a line, and pushes code outside what would be considered idiomatic for the language IMHO. There is more value in consistent use of language idioms than reduced LoC.

@tomwarren That's great but no matter what settings I've chosen, drivers updated, etc, Win11 refuses to recognise my 2020 PC as being suitable. So I have to buy at the very least a new mobo and give up an afternoon rebuilding the damn thing? Poor show, very poor show.

Microsoft would really like you to stop using Windows 10 this year. It's calling 2025 the "year of the Windows 11 PC refresh," and it thinks refreshing a Windows 10 PC will be more important than buying a new TV or phone theverge.com/2025/1/6/24336…

@electrician_247 I don't get the point of this device. Considering a) where my consumer unit is, and b) that with the exception of the fridge I don't have individual devices wired directly to it, implying c) I never want to turn entire circuits off and on remotely.

Cool way to control electrical equipment and lighting with Shelly devices. What are others using?

@ResisttheMS Incandescent bulbs are fine. They work. They produce a nice, even light. The problem is they are less efficient than LED bulbs, so cost more (and use more natural resources at scale), yet are complex and not always well made and so don't last like they should.

NEW: Senator Mike Lee advocates for the return of incandescent light bulbs under the upcoming Trump administration. Do you agree?

@VaughnVernon Yep. To me, the Outbox's job is only to be an outbox. If it were a tray on my desk, when the office post trolley comes around and takes it, it's not in my outbox any more. If I wanted permanent copies I'd make my own and put them somewhere with a relevant retention policy.

@neilbarnwell Which means you delete (hard/soft) rows from the Outbox table, and you don't have long-term storage of events. That confirms my point, thanks.

This weeks' Design Accelerator: Why I Hate the Outbox Pattern and Why You Should Hate It Too Watch now: youtu.be/3nZLU3b47iU

@krzyzanowskim I remember the Microsoft coding style guide used to say two chars or less would be upper-case (i.e. userID) but more would be title case (i.e. userId or userSsn). Personally I only ever use the title case variety for abbreviations, and sometimes I don't abbreviate at all.

what's correct: userID or userId

@VaughnVernon But for the outbox itself, it's really just a technical detail to avoid distributed database transactions - it's emptied once the message is known to have been handed to the messaging system (yes, consumers still need to be idempotent).

@VaughnVernon For long-term (even permanent) storage I'd probably have an auditing service subscribe to all messages and put them somewhere, or use Event Sourcing for the entity storage.