Vikram Saraph / is on Nostr

Somewhere between software engineer and researcher. Brown CS PhD/math MA and Notre Dame math/CS, interested in all things math and software, and using social media for good. he/him

Last Notes

2024-08-19 16:57:24

Current distraction. I think I’m looking at a trefoil knot.
https://media.mathstodon.xyz/media_attachments/files/112/989/740/762/792/427/original/7e08ef024f66edda.png

2024-08-19 16:57:24

Current distraction. I think I’m looking at a trefoil knot.
https://media.mathstodon.xyz/media_attachments/files/112/989/740/762/792/427/original/7e08ef024f66edda.png

2023-08-27 21:11:47

- reply

@npub1z2q…3yuf @npub1zsm…wvua I 100% believe this number is irrational, but what would a proof of this look like?

2023-05-25 23:14:14

- reply

@npub1a4c…t2kf I have personally observed software development being slowed down by throwing more bodies at problem. I am admittedly only looking at the Wikipedia summary of the book (don't have the book itself on hand; I have read it though), but it states:
> Software projects are complex engineering endeavors, and new workers on the project must first become educated about the work that has preceded them; this education requires diverting resources already working on the project, temporarily diminishing their productivity while the new workers are not yet contributing meaningfully.
It's the diversion of senior engineers' time towards knowledge transfer to new engineers that, in my experience, can slow things down, since this (1) takes time away from contributing themselves or (2) providing direction to less experienced engineers. This cost can be reduced with good documentation and on boarding procedures in place, but sometimes a project isn't so fortunate to have this.
There is also this:
> Communication overhead increases as the number of people increases. Due to combinatorial explosion, the number of different communication channels increases rapidly with the number of people.
Which I have also observed in practice. If good communication practices aren't established before new engineers are brought on, people's attention can be unnecessarily wasted with too many channels. This also hurts productivity.
I don't know if you're an outlier, but I am also not sure whether your career experience would necessarily be representative of the average/median software engineer.