pod network | Competitive salary + equity | Remote | Multiple roles

We’re an early stage blockchain startup building the next generation of decentralized financial infrastructure. Our novel architecture provides more than 10x better performance than competitors while completely avoiding any centralised party (or leader) having an edge over other participants, eradicating MEV issues and enabling more fair markets.

Backed by a16z crypto and 1kx.

Hiring: Backend Engineer (with trading systems experience), Business Development Lead, Content & Growth Strategist

Apply here: https://pod.network/hiring

just a pedantic detail, strings are passed in javascript by reference, they are just immutable

I just went down the rabbit hole of reading this post and the entire thread. As someone who has been looking for a junior job, it's probably the most depressing thing I've ever read. I've been on the market for over 6 months, I've sent countless resumes out and tried various techniques, but I'm not even getting a nibble.

I guess technically it's passed the reference to the string right, so if I say a = "stringA" there is a reference to "stringA" and that is assigned to a if I then say a = "stringAA" there is another reference created for "stringAA" and assigned to a, while "stringA" is sitting around somewhere waiting to be garbage collected in a few milliseconds - that's way complicated to think about and not sure if I haven't messed it up.

Easier to just say pass by value and forget about it. OR make all your variables consts and then it don't matter.

No, thats not correct. Value and reference assignment behave the same way for = (well, reference is hiding the fact that it’s not the literal string/object but a reference to it, a number is just the number).

Where it matters is in passing arguments to a function call. If you pass 42, it’s not mutable so incrementing, or doing anything, will not modify the original variable you passed-in. For a reference, using = will assign a new value (not change the original) but modifying the referenced object like, say a.b = 5 WILL change the original object.

It’s not really “pass by reference” that a C/C++ developer would understand but it seems to be the term that has stuck.

>= (well, reference is hiding the fact that it’s not the literal string/object but a reference to it, a number is just the number).

>For a reference, using = will assign a new value (not change the original)

what I wrote was regarding only strings, so I'm not understanding - it seems you are saying the same thing I said? But maybe I'm wrong about how the actual strings are stored.

Sorry to get a bit nerdy here, but in JS, neither pass by value nor pass by reference make sense as it’s not defined by the spec and much less followed by the implementations. Strings can be pointers to buffers or ropes, numbers can be values (NaN-boxed or otherwise) or pointers depending on a number of conditions, it all depends. However, from what’s observable in the language, all variables are pass by value. There’s no way to pass anything at all by reference, primitive or not, i.e. you can modify a field of an object you were passed but you can’t change the object.

Hashtable of all strings made in program.

Doula (δουλα) in modern Greek is female slave.

I didn't know there was an English version of the word (until I read the article ofc) so I assumed that that was also the English meaning.

Wikipedia: "Socialism is a political, social and economic philosophy encompassing a range of economic and social systems characterised by social ownership of the means of production and democratic control or workers' self-management of enterprise".

Which is not "...characterised by government giving handouts".

But isn't that implied by 'social ownership'? That means, society owns production and thus decides who shares in it? That's where they get conflated, I think.

It does try to convey something in words in the next chapters, no?

Yes, but the intention of the text isn't to explain what Dao is and how to live according to Dao. It clearly says that's impossible, and even calling the concept 'Dao' is counterproductive to a full understanding.

So the text is meant to do something else, like help others start thinking and learning for themselves.

Well it tries yes.

I felt the english version was ambiguous so I read the original finnish version. It says that press reports that the trial is aborted earlier than planned is false, and for the time being there is no decision to extend it.

Yea, it does seem interesting looking at the differences. And it isn't like I know Finnish, I used google translate but even just the bolded intro is different

English: There have been incorrect reports in the media about the Finnish experimental study on a Universal Basic Income. The experiment will run until the end of 2018 as planned.

Finnish[1] (in English): In many international media, information has been published that Finland is going to suspend a baseline experiment. However, the experiment will continue according to the original plan until the end of 2018.

[1] http://www.kela.fi/ajankohtaista-henkiloasiakkaat/-/asset_pu...

> Yes, I am aware that this is likewise no accident.

What do you mean by more than 100% margin?

If you sell something for 150$ and it cost you 30$ your gross margin is (150-30)/150=80%.

I'm assuming the grandparent meant to say "mark-up" rather than margin.

EDIT: And I just saw the comment below yours pointing out the same thing.

The problem is not if someone merges a PR before you push, but if someone branches off of the current tip of master, works on it, you remove that tip, and your colleague now is based on a history that doesn't exist, has to resolve your conflicts.

They're the same conflicts they'd have to fix if I pushed a new commit or merged a PR; assuming I made the same changes to code when I force pushed.

And Google participating in EU market is voluntary. If it doesn't like the laws or the power of the EU investigators, it can choose to take its business elsewhere.