iovrthoughtthis

feel the authors pain

everytime i sit down to give rust a try i get catapulted down some esoteric rabbit hole about conceptual abstraction over computer memory that rust invented for my safety that isn't fully fleshed out conceptually or in implementation

all my rust programs are provably safe though, because i never finish them and no one ever uses them

im not certain why any of that is at odds with providing secure secret management to employees

it's already a part of secret management for machines in secure cloud environments

this is somewhat a pipedream

orgs should support what people do

i didn't see the words "it depends" anywhere in this

thats the whole point of engineering, picking/building the right solutions for the problems and context

some stuff just needs a vps, a php file and an sqlite db and it will scale

other stuff might need container orchestration or anywhere in-between (or beyond). it should depend on the context though and we should be prepared to change strategy as needed

you sound fun

this is the best way. everything else is incredibly over complicated and magic

you still have the previously valid tree because the parsing is incremental

i suspect it's tree sitter under the hood

we're trying to draw really well defined lines between very fuzzy concepts

interested to see when the pendulum swings back on this

the premises and all good to know sections are useful. the other sections are too prescriptive as to other peoples behaviour to be useful.

it reads more like a guide on working for you, less a guide for working with you.

these should give people the context and "why" of working with you, not the prescriptive steps required.

the use of "we" everywhere is the tell here. the readme is about you, not me.

i have no idea why we include these in code reviews tbh

this sucks :(

why does anyone forget?

"if you cared, you'd remember"

glad you have this experience, i dont think all of us do. i care deeply but seem to forget people exist and that makes me sad and dislike myself. i wish i could just remember. id still have so many friends if i did.

i think people who take amphetamines every day also know how exhausting it can be.

must be nice to be able to take a break and not have your entire life fall apart.

it's hard to answer comments like this cordially.

good for you i guess but i've spent enough of my life self-flagelating, pretending everything is my personal failing thanks.

quite thankful i can ask for help, be heard and see improvement.

people need a "how to work with me guide".

If you're an employer reading this and thinking "how can i help make my company adhd friendly" then i highly recommend you check out the welfare pack from adhduk [1].

i had a chat with the ceo of the charity when i got diagnosed to see if i could help and he is one of the few people i've spoken to in the space that is actively considering adhd in the workplace.

my favourite parts are:

- before criticising timeliness, ask if timeliness is critical to the role. if it isn't, have a policy of flexible time, make it ok to make up lateness later. if it is, find ways to make it less so with scheduling and partnering

- hot desking / open offices: make provisions for people to have quiet and uninterrupted work environments. perhaps that is alternate office space, providing noise cancelling headphones.

- meeting timeliness: fully integrate calendar and reminder systems. for many with adhd something not in the calendar may aswell not exist.

there are loads more but most of the key point boil down to: stop immediately thinking that every time someone doesn't meet your expectations, that it's a personal failure of theirs. start considering how the environment (physical, social, technological, conceptual) might be an impediment to them. start questioning your assumptions around what is "actually" necessary for a role and what you think is necessary.

my personal addition to this is: lots of the ways in which i disappoint people ultimately derive from an innate fear of disappointing people. the irony is not lost on me. the answer, ive found, is to create for myself an environment in which a) my colleagues can separate their disappointment in my actions/ outcomes from me. b) where i can communicate my issues / worries as and when they arrive without fear.

my favourite one has been telling people that a particular task will be far to boring for me to do alone and being able to partner up with someone else to get it done. or that asking me to remember to do something in prep for a meeting is a bad idea and to either pop it straight into my calendar, do it now or make some time during the meeting to do it. that last one is basically the amazon meeting agenda policy where the start of every meeting is reading the notes for the meeting, it's adhd dream.

i am reminded to leave this caveat: yes, these are problems we all face, the questions is: do the problems cause a material impact on your life (lost jobs, failed relationships (love/friends), missed opportunities, states of being that you cant escape). the difference between having adhd and not is whether the problems cause disorder in your life currently, and have done so for much of your life.

1]: https://adhduk.co.uk/adhd-and-work/

Just wanted to say that the authors libraries, especially ROM [0], are incredible and have played a huge influence on me as a developer. I learned a lot using and diving through the code.

[0]: https://rom-rb.org/

i think thats a reasonable opinion in the context of say, language implementation.

for the relatively simple case of parsing cli arguments i would want an equally simple api. "is this string a valid representation of a number?" and "what number does this string represent?" should be separate apis.

even in language implementation, i'd want the identification of number tokens to be separate from the parsing of those number tokens. i would then have another, separate api for "where does the first number end in this string?" which would probably more likely be "return to me the next substring from this string that represents a number"

but this is not a appropriate place for that functionality.

yeah, welcome it and ask "hey, thanks for popping by. why are you here though? im not sure theres anything i need protecting from, so what are you trying to protect me from?"

our discourse often seems to lack the nuance, that two opposing ideas can (and should) be held in our heads at the same time.

that we should hold ourselves in unconditional positive regard and that we can strive for more

imo, this article is attempting to push the pendulum back towards the positive regard as, and i would agree, the author feels that were too far into striving

> At the same time, I think there are demographics in this country that are more likely to abuse the system or display behavior that make one a little more suspicious of them in principle.

i want to gently point out, without implying intention, that this is, in it's self, a racist belief

i find it useful to develop my own internal model of the goals and direction of a project and lay peoples (including the higherups) "opinions" against that.

if they match, it's probably on point

if not, its probably not worth it

sounds like you were just promoted to manager

i joke, but the experience you had would usually have been buffered by your manager, whos job it is to communicate with you about requirements and feedback from above

youre work does not define you. be careful letting these comments impact your perception of your self. equally, mine it for ways you could improve (if thats a goal of yours), raw feedback is the best feedback but accepting it is a muscle you have to work on slowly

have fun installing and managing widevine!

i was so surprised by how hard it was to step outside of the walled garden

perhaps both! i'm currently exploring gabor maté's theory that it's a combination of genetically predisposed sensitivity and insecure modes of parental attachment

well, executive function issues are quiet heritable

i wouldn't be surprised if causation were reversed and children who have slower executive function development drink more ssb's

is caffeine controlled for?

you should be able to apply the same principals you picked up from developing in Java/Closure

node/js applications tend to be a bit more home grown than more traditional, convention driven ecosystems

for architecture: my "advice" would be to start with a single file, add things until you start to find friction (having multiple windows of the same file open is a good sign, constant searching too), break things into separate files based on your preference, folders and directories along the same lines, be consistent

your knowledge and opinions about errors/exceptions is valid here too

nodejs is fast but its not so much a performance focussed platform so ime, tuning options are lacking. there is an eco system of tools for managing stuff but it bleeds into the environment a lot more e.g. process management, ops and infra