kkard2

joined 1 year ago
[–] kkard2@lemmy.ml 8 points 1 year ago

i would personaly advise against running thru crossings (you become less predictable if you run)

[–] kkard2@lemmy.ml 46 points 1 year ago (2 children)
[–] kkard2@lemmy.ml 16 points 1 year ago

oh it's x, not x... i hate our timeline

[–] kkard2@lemmy.ml 19 points 1 year ago

clearly needs a green top

[–] kkard2@lemmy.ml 4 points 1 year ago (1 children)

you don't need visual mode for that, use _f(ci(foo

[–] kkard2@lemmy.ml 1 points 1 year ago

nope, don't miss it at all after i got used to vertical

[–] kkard2@lemmy.ml 11 points 1 year ago (5 children)

i still can't believe people think it's A

[–] kkard2@lemmy.ml 23 points 1 year ago* (last edited 1 year ago)

Just started learning C++ :)

my condolences

[–] kkard2@lemmy.ml 3 points 1 year ago (3 children)

everything is a bucket

[–] kkard2@lemmy.ml 5 points 1 year ago (1 children)

i never thought about that, it makes a lot of sense

[–] kkard2@lemmy.ml 2 points 1 year ago

if i write a date on paper i tend to go with 2, but yes

[–] kkard2@lemmy.ml 14 points 1 year ago* (last edited 1 year ago) (5 children)

to make things as not confusing as possible, my rule of thumb is:

  • yyyy-mm-dd (yyyy instead of yy ensures that it's not mistaken for dd-mm-yy) (hyphens can be replaced with underscores)
  • dd.mm.yyyy (yyyy same as above) (really dislike using for filenames, sorting doesn't work)
  • mm/dd/yyyy (only if there is no other choice) edit: mm/dd/yyyy vs mm/dd/yy doesn't matter because both make 0 sense already edit2: i forgor to say that yyyy also avoids y2.1k and subsequent issues
view more: next ›