JohnCurran
Joined 6 years ago
Joined 6 years ago
This is good advice and I agree with it. I just wish it wasn’t the advice we had to give
In any case. This seems like a continuation of the never ending quest for people to sacrifice themselves for the betterment of a corporate profit they will never see.
I’m not interested in eliminating the ceiling - I want to raise the floor. Having a “side hustle” shouldn’t be a requirement to get by.
I am frustrated that the USA’s money advice largely comes from billionaires. They’re not like us. That’s OK. There’s a lot of room between millions and billions
I think, and am basing this off of nothing objective, but it feels like the vast majority of content today is written by people who spend, frankly, too much time online. I think the fact I’m writing a comment about this says that I, too, spend too much time online.
The bubble that the tech world and this website in particular differs so much so from reality that I don’t know what to make of the articles that front page here.
All the twitter doomsaying, trump will never be president, all entirely wrong. I don’t know what to make of it - maybe I should log off for a while
http$
.pipe(
map(res => res['payload']),
catchError(err => {
console.log('caught mapping error and rethrowing', err);
return throwError(err);
}),
finalize(() => console.log("first finalize() block executed")),
catchError(err => {
console.log('caught rethrown error, providing fallback value');
return of([]);
}),
finalize(() => console.log("second finalize() block executed"))
)
.subscribe(
res => console.log('HTTP response', res),
err => console.log('HTTP Error', err),
() => console.log('HTTP request completed.')
);
Once you see the output it begins to finally make sense but intuitive it is notI have such an issue with this response because it just seems like “you’re holding it wrong” a la the iPhone “scandal” where apple attempted to blame an engineering flaw on its users
I would imagine most people’s use case (mine certainly is) for RxJS boils down to “call a JSON API and receive a response”. That shouldn’t be a hard problem
Imagine if someone complained about the complexity of Git and the answer was to “write your own DVCS”
The entire point of abstractions is that I don’t need to understand what’s going on underneath them
These are two common scenarios I see:
- Two employees at the same level on the same team. One is paid $X higher than the other. Employee one asks for raise based on the fact they do the same job as employee two
- New hire is paid $X more than member of team who has been there receiving meager raises yearly. They can point to the new hire and request $Y more due to their experience
That said, this is conjecture and not backed by anything. Are there published works on salary transparency = lower pay for employees?
It’s a loosely collected group of mentors and mentees with a small dedicated group of full-time learners on a stipend program
The #1 challenge, by far, faced by the org is hiring and placement into companies for cohort graduates and mentees.
If you’re able, consider posting job listings in the UD slack
*I am part of the group as a mentor and its been on the whole an incredibly positive experience
Johnelmlabs.con