Live data from Hacker News

GitHub Arctic Code Vault: Tech Tree

github.com

101–105 of 105 posts

Re: GitHub Arctic Code Vault: Tech Tree

#101
post #72

Earlier quoted context omitted.

The core of the project is written in English, which is the current lingua franca of the world. If the purpose of the archive is for future scholars to have a corpus of knowledge from our time, then limiting it to one language maximizes the probability that the entirety of the information stored there will be recoverable. Including texts in Finnish and Hungarian almost ensures that parts of the archive will be lost 1…

Being trained as a historian, the idea of throwing away original texts in favour of translations because they're not in « the right language » is hurting my soul. If a text is lost because it's only written in Hungarian, it means the Hungarian language is lost. And that means not enough texts written in it were kept. See the problem ? Keeping as much linguistic data as possible is beneficial. Intentionally curtailing…

>Being trained as a historian,

Can we kill this fucking meme? The fact that you spent $150k to be told to read books is irrelevant.

Re: GitHub Arctic Code Vault: Tech Tree

#102

Earlier quoted context omitted.

Except the World Series is named after the original sponsors of the competition and is not meant to infer worldwide participation. I'm not from the US and I am not from somewhere that plays competitive baseball and I know that,therefore I assume in the competitive baseball world this is known widely enough.

Nah, it being named after the New York World newspaper is just the sports blogger equivalent of an old wive's tale. It really was built off of the US exceptionalism of the gilded age with the idea that nobody could beat the US at it's own game anyway so why bother inviting them. https://www.npr.org/templates/story/story.php?storyId=467571...

The New York World story even has its own Snopes page: https://www.snopes.com/fact-check/world-series/

Re: GitHub Arctic Code Vault: Tech Tree

#103

Earlier quoted context omitted.

That is some classic feminist irony right there. If I were a woman, I would hate that shit but it seems like most people who comes up with and support ideas like this are either too stupid or too ignorant to care.

> If I were a woman, I would hate that shit but it seems like most people who comes up with and support ideas like this are either too stupid or too ignorant to care. So if they don't do what you would prefer, they're too stupid or too ignorant to care? What about if they're perfectly smart and perfectly aware, and just aren't concerned with doing what you personally want? Maybe you feel differently from most people,…

If they actually care and does it on purpose they are simply sexist.

> And to be fair, you don't know how you'd feel about this as a woman, because you don't identify as one (presumably).

I would say that this is a fair point but by adding that if I simply would identify as a woman, my thinking is valid makes it laughable.

Ok, I identify as a woman today for the coming 4 hours. I still hate this shit. Check mate.

Re: GitHub Arctic Code Vault: Tech Tree

#104
post #72

Earlier quoted context omitted.

Being trained as a historian, the idea of throwing away original texts in favour of translations because they're not in « the right language » is hurting my soul. If a text is lost because it's only written in Hungarian, it means the Hungarian language is lost. And that means not enough texts written in it were kept. See the problem ? Keeping as much linguistic data as possible is beneficial. Intentionally curtailing…

>Being trained as a historian, Can we kill this fucking meme? The fact that you spent $150k to be told to read books is irrelevant.

Sorry to disappoint you, I didn't spend a dime on education.

Re: GitHub Arctic Code Vault: Tech Tree

#105

Earlier quoted context omitted.

Usually when joining a fairly technical team, the team has put together "learn these things" to get up to speed. For example, on our team where I am currently, you should be fairly familiar with statistics and maths after the first year on the team.

Okay, so it's just an onboarding-type list but with "dependencies" to structure them like a tree?

For us it's less about onboarding to the team and more of what tech do we need to develop for this product to meet client spec. I'm using it more as an organizational tool to structure which tasks need to be done sequentially (i.e. the API needs to be complete before we can test it with the software) and the tasks that can be done concurrently (i.e. the hardware can be developed and tested the same time as the software, up to a point).

I think you could use a gantt chart to accomplish the same thing. https://en.wikipedia.org/wiki/Gantt_chart

And your comment about the dependencies is still accurate for my team since we have to be efficient about doing the concurrent parts together to make sure we get this product to our client on time.

It's been useful for me to visualize all the moving parts of my project and see options that I have in a way that is familiar to me.

Post reply on HN