adam_ellsworth

The premise of this is that I feel people are pinched for time and need space to work – yet when they come back from their coding mode the answers team members provide seldom respect the depth, severity, or nature of the queries which are posted while people are focusing on dev work and, in some cases, simply delay the discussion of it until the next weekly/in-depth check in.

I've been thinking about this a lot lately, and while daily meetings are nice, once you start to go beyond the bounds of "yesterday I was working on ... and today I'm working toward ... could you provide a bit more help and/or context on <such and such> ..." the discussion balloons beyond a reasonable check-in limit with regard to time.

The properties of communication in remote work seem very hard to crack and I'd like to know if this problem is something your team has succeeded at – and, If so, how?

Edit: To be sure, I'm not talking about alerts/system critical stuff. Additionally, I work in a small company, so maybe there are safeguards for this kind of predicament in larger orgs.

Thanks

Today I was considering how organizations such as bitly, imgur, reddit, and even github handle hash collision prevention.

While for GH it (seems) easier as commit hashes are sufficiently long/unique, for others with character hashes that only span ~6 chars or so, there's bound to be instances where hashes conflict from a statistical standpoint. (iirc reading an article on a hash collision in GH a few years ago here on ycomb)

To my mind these orgs have to have a suite tools/algos requesting information from multiple services, checking whether or not a hash has been taken – and those processes have to optimize for time. (e.g. when a user makes a post, what's a reasonable time to do a lookup?)

So, what are the considerations which need to be made algorithmically to check such collisions while keeping runtime to an acceptable minimum?

I started my job search about 8 months ago, and while I've had a few interviews, I feel like my CV is hindering my prospects.

Ty.

I've found over the past few years that I've gotten into some unfortunate patterns. I basically need to re-write what it means to be healthy for me but am uncertain what new habits I should be considering and/or nurturing. What are your practices/habits day-to-day while WFH?

I was a Frontend Developer for 7 years and, under a new title, FE Product lead on most of our internal client-facing applications for 3 years and find myself interviewing for positions in FE while also attempting to relate both abilities and it's not gone well recently.

(To my mind I can't just hop in as PM at a new company as there's an entire Dev culture for those prospective employers which I should understand from the ground up.)

This post is very poorly worded and omits so many of my thoughts on DevRel/DevOps, but I've found myself recently describing to interviewers why I want to work in Dev (ground-floor dev work to get a good understanding of the dev needs of those prospective companies) as well as trying to establish why I have the capacity to be a good fit for Product Management for them in 3- to 5-years time.

At this point should I even be looking into FE jobs or should I seek out PM? What intermediary steps am I missing (certifications, job titles, etc)

Basically title. I got rid of my copy of Rosen's book after undgergrad but am not keen on enduring it again. However, I'm also in need to reflect and refresh on the topics discussed therein. Thank you.

I've been studying the AWS Certified Developer - Associate Guide for the past few weeks and would like to know if it's up-to-date with AWS.

The book in question is a Packt edition, published May, 2019 (Tankariya/Parmar, Second Edition)

If it's outdated what new resources should I look to? (The book originally cost about $40+, and am not keen on paying for it again if AWS docs can fill in the blanks)

Thank you in advance.