dunnhq.com
Love cooking my friends, software development, and grammar.
Maintains Vogen
https://dunnhq.com/
@stevedunn on Twitter but I don't go there much now
167 posts
658 followers
1,234 following
Regular Contributor
Active Commenter
comment in response to
post
Wossat?
comment in response to
post
Amazing. And don't even think of buying a new car with their extortionate 'first year ' or 'premium' tax. If it's old and thirsty, then it's probably polluting less than a new and less thirsty model. It's not about pollution, no more than it was about "roads" when it was called road tax!
comment in response to
post
I've been used to some quite archaic things dating back to original ASP (where you could append a URL with :$$data and actually get the page source!). Since then ASP.NET, MVC, PHP. I'm mainly backend, and so Blazor fits nicely with its mixture of back and front end.
comment in response to
post
I've found the complete opposite. I suppose it depends on what you're used to.
comment in response to
post
You can also mark them as UsedImplicitly. Or PublicApi.
I often create a DtoAttribute which uses the MeansImplicitUse attribute. All from Jetbrains.Annotations
comment in response to
post
Why are they unused?
comment in response to
post
What will they discuss down the pub after?! There's nothing left in software for me any more!
comment in response to
post
Like he did with his Tweet "Now is a great time to buy" (in between the pretend sanctions (and probably seconds/minutes after whatever private groups he's profiting from)). There's a name for this... 🤔
comment in response to
post
Interesting, what is their commission? I do feel like Stripe is an ecosystem that's hard to break out of. But saying that, I've also felt it was a fairly painless API. Granted, the Products and Prices components felt like overhead, but has made me think more about my system
comment in response to
post
I did a Triple O (Old Old Old) game in Blazor WASM. I was thinking of doing it Rust WASM...
github.com/SteveDunn/Pa...
Play it here...
stevedunn.github.io/PacManBlazor/
comment in response to
post
Do you think 3.14 is discriminatory?
comment in response to
post
Great work! A clean architecture includes absolutely no Primitive Obsession. Get that smell away from your code! github.com/SteveDunn/Vo...
comment in response to
post
I think Realist (with experience) covers it. But yeah, I know what you're saying!
comment in response to
post
It's a crazy crazy world.
comment in response to
post
More fool them for remaining in such a toxic environment
comment in response to
post
.net runtime I think
comment in response to
post
Pretty good mate (relatively speaking) 😁
comment in response to
post
I try to keep away from this shitshow, but I guess Shorting was involved somewhere along the line. Like the vultures that capitalised on #Brexit
comment in response to
post
Maybe just on Linux?
comment in response to
post
It helped me by having the scope be from the Inception of the command and shared amongst all the handlers. It also meant I could get rid of repositories which I've never been a fan of
comment in response to
post
I hope this means the end of the dreaded 'project skipped' issue in visual studio. I've encountered that a fair bit recently when working with old and dusty .net 4 solutions
comment in response to
post
I use mediator for commands that take part in a unit of work flow. Actually works quite nicely
comment in response to
post
... and I just remember I did something similar many moons ago, called TreeTrim - which chained commands, e.g. 'trim => zip => email'
code.google.com/archive/p/tr...
comment in response to
post
Nice! I tend to do a `git clean -xdf` when I want a 'deep clean'.
comment in response to
post
Congratulations, well deserved!
comment in response to
post
Me and Dave down the pub sorted it. No agreement, so came down to a game of pool. Then best of 3. Then 5. Can't remember the outcome.
comment in response to
post
You could've worn something!
comment in response to
post
Nice to see you here!
comment in response to
post
Word
comment in response to
post
And a backlink to the previous version and the repository for release notes. Maybe a shoulder.dev hook too