Article 13
This is actually a good use for generating images. For goofy, "fun" throwaway pictures - not for anything real.Is it worth the compute and environment-torching? No, but I guess if this is happening on...
View ArticleArticle 12
That said, plopping slop images into your writing seems like one of those things that feels like it makes stuff look more prop, but just doesn't and makes it worse.And: removing people from photos is...
View ArticleArticle 10
Oh no, why did they do a chatbot? We don't need gasoline pasta. I feel like this bit about OpenAI just let a lot of air out of the room.This is just the worst of “A" “I”#WWDC
View ArticleArticle 8
XCode with Apple Intelligence:"Looks like you are creating a useful error message. Might I suggested replacing it with 'try again later’?”#WWDC
View ArticleArticle 7
The Apple "AI" feature that I use the most—that already exists—is when Fastmail's app just dies trying to send. In this mode you can read your email, it's not been saved as a draft, but you can't...
View ArticleArticle 6
Two OO ways to design something, curious what everyone's thoughts are? This is w/out context of a framework, just purely OO perspective.Option 1 - Stateless object w/ Rich ResultOption 2 - Stateful...
View ArticleArticle 5
Stateless code seems easier to test and operate, since it's basically just a function. Certainly, it can affect the world around it (e.g. in a database), but it's a long-lived object that performs a...
View ArticleArticle 4
Stateful, on the other hand, keeps all concepts together: the operation and its possible results are all in one class, which feels cohesive and easier to manage/evolve the code.The downside is that the...
View ArticleArticle 3
The "lazy mode" of these approaches is woerth considering:lazy devs applying the stateless approach will use boolean return value, which sucklazy devs using the stateful approach will overload existing...
View ArticleArticle 2
Of note, this is why OO books like POODR leave me wanting. The examples are so trivial and unlike anything resembling real code that they fail to give true insight.You can retcon any set of objects to...
View ArticleArticle 1
Related to my previous question: return values from methods in RubyThe new pattern-matching stuff does seem to have a theoretical advantage that you can simply return anything and use case to branch on...
View ArticleArticle 0
Thus, if you have something likecase foowhen Bar if foo.invalid? # ...when Widget # ...endi.e. you expect either an invalid Bar or a Widget to be returned.If neither happens, you cannot debug this...
View ArticleArticle 10
This is an amazing rant. Top quality.https://hachyderm.io/@kstewart/112662638223105523
View ArticleArticle 9
I know this toot is about not using JS to achieve the given design. I 100% agree that you should not use JS if you need to build this sort of design.That said, I really do not like form elements that...
View ArticleArticle 8
Devs are in a tough spot sometimes, because we have to build what designers ask for and can't always push back. It's also not always easy to advocate for a less fancy design that is more obvious. The...
View ArticleArticle 7
MelangeCSS ( https://melangecss.com ) is more like Tachyons than Tailwind. Melange as a design system and is OK with you extracting stuff to CSS. Here is one way, where duplicated styles are...
View ArticleArticle 6
And for fun, I added back the labels.https://codepen.io/davetron5000/pen/PoveRENLabeling form elements is great! You can:• know what the element is for• referr to it in words for e.g. documentation or...
View Article