HackerTrans
TopNewTrendsCommentsPastAskShowJobs

nmat

no profile record

Submissions

Does working from home kill company culture?

economist.com
3 points·by nmat·w zeszłym roku·1 comments

[untitled]

1 points·by nmat·2 lata temu·0 comments

How encrypted messaging apps conquered the world

economist.com
2 points·by nmat·2 lata temu·0 comments

London Squat Parties – A Short Documentary [video]

youtube.com
1 points·by nmat·2 lata temu·0 comments

Fear of Fashion by Derek Guy

thepointmag.com
2 points·by nmat·2 lata temu·1 comments

A golden age for stockmarkets is drawing to a close

economist.com
5 points·by nmat·2 lata temu·0 comments

Another America – AI-Generated Photos from the 1940s and 50s

lensculture.com
1 points·by nmat·2 lata temu·0 comments

Forty days lost in the rainforest: Colombia's miracle rescue

theguardian.com
2 points·by nmat·2 lata temu·0 comments

Large-scale pancreatic cancer detection via non-contrast CT and deep learning

nature.com
2 points·by nmat·3 lata temu·0 comments

‘It was as if my father were texting me’: grief in the age of AI

theguardian.com
2 points·by nmat·3 lata temu·0 comments

What makes something an heirloom?

putthison.com
80 points·by nmat·3 lata temu·75 comments

comments

nmat
·w zeszłym roku·discuss
To be honest I was expecting the article to focus primarily on internal docs, meetings, long Slack posts, etc. Staff engineers spend a relatively small percentage of their time writing code. A lot of what it takes to be successful is knowing how to communicate with different audiences which AI should be really useful for.
nmat
·2 lata temu·discuss
And do you go back and update all documents whenever something changes? If you’re swapping people around every month I agree that you must keep everything written down, happens a lot in projects that bring consultants in. But if you have a core team of people and you get 2-3 new people per year then you should be more relaxed about it.
nmat
·2 lata temu·discuss
I strongly believe that proactively keep documentation up to date is not worth the effort. Here is what I recommend in my teams:

- There’s an onboarding guide that is usually only updated when new people onboard. If something is not right they raise it and their onboarding partner fixes it.

- When someone shares a technical document/RFC we add it to a central repository with a creation date on it. These are point in time and usually not updated but still useful for new hires.

- We sometimes do onboarding sessions to walk through the architecture, these are recorded and added to the central information repository.

Note that in the things I wrote above there’s a mix of up to date content and slightly outdated content, ultimately the code is the source of truth. It’s not worth spending time writing docs that no one is gonna read.
nmat
·2 lata temu·discuss
Face to face communication is very underrated nowadays, probably because of the negative connotations associated with meetings. Talking to someone is by far the fastest way to convey information. I often prefer a quick chat than spending 30 minutes writing Slack messages back and forth. I agree that writing has other benefits and it's better in certain cases but we need to get out of the mindset that writing/async is always better.
nmat
·2 lata temu·discuss
Australia participates in the Eurovision Song Contest.
nmat
·3 lata temu·discuss
And YouTubers should make content for free?
nmat
·3 lata temu·discuss
Reminds how US centric a lot of crypto companies are. An advantage of crypto that often comes up is “instant and cheap money transfers”. In the UK, I transfer money to my friends instantaneously and for free using just my bank account.
nmat
·9 lat temu·discuss
This reddit thread has more information on the bug https://www.reddit.com/r/sysadmin/comments/7nl8r0/intel_bug_...