Think about it this way: I am in the top earning 2%. It is only possible to buy such a home if you have a partner, who makes similiar numbers and then together decide to dedicate your life to it. The 98% of the rest cannot do it. Ergo I am either not earning enough or we have to accept, that you cannot really buy property within a top-tier city in Germany. In the end the whole debate turns into young vs. old and heri…
But would the situation be better in the US where you might get 2x the salary but rent and housing prices are also 2x the German level?
US is generally cheaper to buy a house based on income. Too lazy to google the graph.
We don't teach pass by reference these days. Anyone you find in the real world under ~30 years old may not even be aware that you can pass a reference and modify it directly without having to make a method return a value. It's super cool to have someone explain to you side effects yet you show them a method with a null return and run it for them showing that the value has changed and they are mesmerized.
What are you on about? Java, Python, Ruby, C#, JavaScript, most languages used to day have reference semantics for objects.
I don't think any of the languages you mentioned support true pass-by-reference. (maybe C# and Java, but it's not common) I've heard what you're describing as "pass-by-value-reference" Go, however, supports pass-by-reference which allows you to write a function like this:
func swap(x *int, y *int) {
var temp int
temp = *x /* save the value at address x */
*x = *y /* put y into x */
*y = temp /* put temp into y */
}
> Are my compensation expectations high No... You really don't wanna work for less than $150k at a startup, at least on the west coast.
I have in the past 10 years worked at about 3 startups where I was making way less than $150K, and the most recent one where I was making right about $150K. In a couple of those cases I was willing to accept low pay because the work/field was a lot of fun and/or it seemed like a socially important project if it succeeded (alternate energy in one case) and I knew that their funding was very tight.
Thank you for sharing, and that makes sense.
That said, you yourself described this as "low pay".
My comment was in response to the GGP's desire to calibrate their salary expectation level.
> In the past I've never interviewed with more than 2 or 3 before getting an offer. I know this is incredibly privileged. I'm not sure why you are saying this. You're in a rough spot and you're human. You don't have to qualify your struggle, even a universal one or one you do slightly better than others. The truth is that it shouldn't take interviewing with 28 companies to find a single offer. Interviewing at a handf…
More of this
We got to stick up for one another and lift each other up. We're in the same tribe, even if we don't know it.
Technical jobs available at Actian!! If you know anyone looking for a job send them the links below. Actian has several open positions in Engineering, IT/DevOps, Finance, Marketing, Sales, and Support.
And what is it that you want to do remotely? Sell nuts and bolts? It’s unlikely someone would read your post and think “oh yeah, you’d be great for our company working remotely”. You didn’t outline a single capability other than selling nuts and bolts.
Resume tip: "x years of experience working at the hardware level. Implemented stacks and queues on bare metal."
What are you on about? Java, Python, Ruby, C#, JavaScript, most languages used to day have reference semantics for objects.
I don't think any of the languages you mentioned support true pass-by-reference. (maybe C# and Java, but it's not common) I've heard what you're describing as "pass-by-value-reference" Go, however, supports pass-by-reference which allows you to write a function like this: func swap(x *int, y *int) { var temp int temp = *x /* save the value at address x */ *x = *y /* put y into x */ *y = temp /* put temp into y */ }
Sure, you can't have the same code for Python, for instance, even if it was using objects, but you can have the same effect using a hack by copying the __dict__ from one object to another. However, you are still passing the object to a function by reference because the function can mutate the object and the object that the callee passed will also be mutated the same way, i.e. mutable objects are passed by reference, and values are passed as values. Which is how python, javascript, Java and the rest work. Obviously, you don't get to change what the reference is pointing to in most of these languages, but you can change the value that is being pointed to.
I'm in my late 50s. When I hear about the salaries that much younger folks are pulling down in the FAANG companies I'm generally pretty shocked - I've never made anything close to that and don't have any expectations to. My expenses are way lower than most of the younger folks in tech because my house is paid off (will be in about a month), we drive 20 year old cars and we're quite frugal. For most of the past decade…
I wouldn't say so....90k is low for someone with a lot of experience. New grads expect more than that.
The skew for pay in the dev industry is weird. When I graduated with my BS (2008) I was happy enough to find a junior position in game dev on the west coast at 40k. Mind you that was during a lovely market crash, but after 4 years in game dev my pay didn't increase very much (but my profit sharing did /eyeroll). Fast forward to the present, I work non-FAANG at a 210k salary and am only required to do dev work with no management silliness and no required overtime. My company hires juniors straight out of college at around 100k... this blows my mind.
Why do so many people think this? Conditioning via plutocracy?
I am not in the US but where I am from the contract usually says you are not allowed to work for another employer unless approved by your current employee. All the stories of overemployed get me kinda envious because I would never dare to try it myself.
Ok. I’ve done it, and the money is nice. However it is a bit stressful and you’ll pay thru the nose in taxes, so I wouldn’t recommend long term.
I've been doing this for 30+ years, and I've found the same. It's not just whether the candidate can answer correctly, but how they answer. Back when I was doing C/C++ interviews, I'd ask questions like: What's the difference between single and double quotes? A meh candidate answers something about you need single quotes for just a single character. A good candidate answers about how the data type for a double-quoted…
Completely off topic, but I wanted to see if your bio could be parsed for an email with chatGPT - since I thought yours was the most interesting I've seen in some time. Turns out cgpt is quite clever: What's the email address: To email, send to the domain [redacted], using the mailbox "[redacted]". In general, email addresses consist of a username followed by the at symbol (@) and the domain name, such as [redacted]@…
as the person you're talking about - I just up-voted you anyway, just because this is interesting :)