Can we please all collectively agree on the number of `~` that wrap a string of text to induce strike-through?
~like this?~
~~or this?~~
~~~or, I suppose, this?~~~
I am tired of guessing and having to edit or delete/repost.
| Github | https://github.com/armahillo |
| Tech Blog | https://armahillo.dev |
| All My Links | https://aaronh.me |
Can we please all collectively agree on the number of `~` that wrap a string of text to induce strike-through?
~like this?~
~~or this?~~
~~~or, I suppose, this?~~~
I am tired of guessing and having to edit or delete/repost.
https://dev.to/mame/which-programming-language-is-best-for-claude-code-508a
Awesome to see Ruby cruising in at the top of all of the tests performed for this experiment
For comparison, if someone who never did carpentry watched a video about building a house, followed that process, and built a house with no professional oversight — would you live in it?
Experience matters
I find it funny how every post I see about “i built this amazing thing with an LLM and it did the whole job and made a working app” also never seem to post the code.
I’ve seen the kinds of stuff even paid plans generate.
It’s mid at best. People need to up their standards.
(reminder that moltbook is the latest vobe coded app to be riddled with security issues).
Has anyone at AWS considered making AWS less fucking complicated to do basic tasks? eg.
🤖 AWS. To use AWS CLI install this app that we host
🤷 Me. <i install the app>
🤖. OK now login using `aws login`
🤷. <command not recognized>
🤖 OH, you need to be using >= v2.32 to do that
🤷 But you gave me....nm OK where can I get it?
🤖 ...
🤷 ...
🤖 How about you create an IAM SSO! Look here for the guide!
🤷 <I click the link, 404>
PSA: The ActiveRecord Boolean value casting method does not cast `nil` to a boolean value!
```ruby
[8] pry(main)> ActiveRecord::Type::Boolean.new.cast(nil)
=> nil
```
If you are writing web copy that involves a call to action link:
❌ Don’t: “You can verify your appointment by clicking on {this link}”
❌ Don’t: “Click {here} to verify your appointment”
✅ Do: “{Verify your appointment}.”
✅ Do: “Be sure to {verify your appointment} before SOME DATE”
Its not the 1990s anymore. Make the hyperlink itself describe the action, not be a document artifact.
> According to the redacted portion of the civil suit, revealed through copying and pasting into another document,
If you hire people based on competency, not loyalty, you can often avoid bush-league errors like this.
If Metabase could do a little less science and a little more "figuring out my query" I think it would probably respond more quickly.
/s