ingemar's latest activity
- 9mo ·
-
Public·
-
ruby.social
@searls “a@b” is a valid email address according to URI::MailTo::EMAIL_REGEXP. Just sayin’…
…See more
@searls “a@b” is a valid email address according to URI::MailTo::EMAIL_REGEXP. Just sayin’…
See less
@searls “a@b” is a valid email address according to URI::MailTo::EMAIL_REGEXP. Just sayin’…
@searls “a@b” is a valid email address according to URI::MailTo::EMAIL_REGEXP. Just sayin’…
…See more
See less
- 12mo ·
-
Public·
-
ruby.social
@tenderlove happy birthday
…See more
@tenderlove happy birthday
See less
@tenderlove happy birthday
@tenderlove happy birthday
…See more
See less
- 1y ·
-
Public·
-
ruby.social
@nateberkopec yes! I used sed it today in favor of “.any?”
…See more
@nateberkopec yes! I used sed it today in favor of “.any?”
See less
@nateberkopec yes! I used sed it today in favor of “.any?”
@nateberkopec yes! I used sed it today in favor of “.any?”
…See more
See less
- 1y ·
-
Public·
-
ruby.social
{"p":"","h":{"iv":"ROXSYW+cfvEbFHu5","at":"ocxplSQjdRC3tXEtB/9/wg=="}}
@nateberkopec I detest GraphQL. It always ends up with a mess. No one dares to touch anything already in there because "it will break the front end".
…See more
@nateberkopec I detest GraphQL. It always ends up with a mess. No one dares to touch anything already in there because "it will break the front end".
See less
@nateberkopec I detest GraphQL. It always ends up with a mess. No one dares to touch anything already in there because "it will break the front end".
@nateberkopec I detest GraphQL. It always ends up with a mess. No one dares to touch anything already in there because "it will break the front end".
…See more
See less
- 1y ·
-
Public·
-
ruby.social
{"p":"","h":{"iv":"ROXSYW+cfvEbFHu5","at":"ocxplSQjdRC3tXEtB/9/wg=="}}
@nateberkopec If that is done once, at app initialization, it can't be a problem, can it?
…See more
@nateberkopec If that is done once, at app initialization, it can't be a problem, can it?
See less
@nateberkopec If that is done once, at app initialization, it can't be a problem, can it?
@nateberkopec If that is done once, at app initialization, it can't be a problem, can it?