atomicmonks.com
Making software since the 80s, mostly business, some games. Unabashed JavaScript enjoyer. Childish taste in entertainment (explosions and cartoons). Probably on the spectrum. A fan of strange haiku. #dotnet #csharp #js #javascript #anime #dnd
75 posts
29 followers
69 following
Regular Contributor
Active Commenter
comment in response to
post
As a dude, I find it disturbing how few guys understand this. Not surprising, just sad and disturbing.
I'm sure it's completely unrelated that most guys have thought of me as "weird" my entire life.
comment in response to
post
Strong start, appropriate expletives, but a weak finish with "nincompoop". Might I recommend:
* soulless flap-mouthed varlet
* stinky codswallop
* witless wart
* canker blossom
More seriously, why don't we hear more about WHY due-process matters?
comment in response to
post
/5 Chrome spots the honeypot field and autofills it, leaving the real one alone.
Google, why am I having to resort to such shenanigans for this?
comment in response to
post
/4 The textarea was clunkier than I wanted to maintain. Where I finally fell was adding an additional text input between the label and the input I cared about:
<input type="text" style="width:0;height:0;padding:0;border:none" name="DummyUserName" />
comment in response to
post
/3 I had removed the "for" attribute on the label also, but no joy.
There was a pretty clever example of using a textarea, which doesn't get the autofill treatment, and using CSS to make it look the same and some JS to make it act more like a normal text input.
comment in response to
post
/2 The commonly listed advice of renaming the field to something other than "UserName" also did not work. After some experimentation it became clear that the associated label ("ID") was being spotted by Chrome's autofill service to populate the now renamed text field.
comment in response to
post
/5 Chrome spots the honeypot field and autofills it, leaving the real one alone.
Google, why am I having to resort to such shenanigans for this?
comment in response to
post
/4 The textarea was clunkier than I wanted to maintain. Where I finally fell was adding an additional text input between the label and the input I cared about:
<input type="text" style="width:0;height:0;padding:0;border:none" name="DummyUserName" />
comment in response to
post
/3 I had removed the "for" attribute on the label also, but no joy.
There was a pretty clever example of using a textarea, which doesn't get the autofill treatment, and using CSS to make it look the same and some JS to make it act more like a normal text input.
comment in response to
post
/2 The commonly listed advice of renaming the field to something other than "UserName" also did not work. After some experimentation it became clear that the associated label ("ID") was being spotted by Chrome's autofill service to populate the now renamed text field.
comment in response to
post
comment in response to
post
I don't think enough consideration is being given to the irrationality of hiring. LLMs don't have to have the capabilities of junior devs, they only have to seem "close enough". Managers making all the money will move on before the damage becomes evident.
comment in response to
post
Quick logical lesson: how do you know someone is here illegally without due process?
Feel like this point doesn't get made nearly often enough.
comment in response to
post
I laugh at your so-called "pollen".
comment in response to
post
That's Mimas (moon of Saturn), for the curious.
comment in response to
post
It's probably mostly massive trades by Trump's favorites, particularly inside the white house. Like not generally the rank and fire govt. workers.
comment in response to
post
Sending them would be quite the feat, since the Cossacks are pretty much Ukrainian.
comment in response to
post
I do feel like I'd be spending less time outside by -20.
comment in response to
post
Yes it was. Still a lot of fires today but much less wind. Lots of dust and smoke still in the air. Not a fan.
comment in response to
post
Dude, didn't know you were over here! You showed up on my discover feed. 😆
comment in response to
post
Had my second monitor die yesterday and told work I'd be in late because I had to buy a replacement. Maybe I _could_ have worked but why would I do that to myself?
comment in response to
post
Half of us, apparently.
comment in response to
post
"Are you the big fish, or the little fish?"
comment in response to
post
Here, I just built this last month and it's been great:
pcpartpicker.com/user/Vraylle...
Sadly, it was about $400 less when I bought the parts.
comment in response to
post
"e̶n̶o̶u̶g̶h̶ anything"
Fixed that for you.
comment in response to
post
Yeah, loved this issue!
comment in response to
post
I think it's pretty clear they won't.
comment in response to
post
The REAL "write once, run everywhere".
comment in response to
post
Same, for work. Path of least resistance here, just went with VS Code.
comment in response to
post
Negative, not a bot, I am a meat Popsicle.
comment in response to
post
Dangit, Bobby!
comment in response to
post
Oh wow, had no idea this was a thing. May have to get a copy.
comment in response to
post
That's why I still have the 2nd Edition Revised and Expanded!
comment in response to
post
One of the best RPGs ever. Never should have gone d20.