Details
Joined devRant on 3/11/2020
Join devRant
Do all the things like
++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatar
Sign Up
Pipeless API
From the creators of devRant, Pipeless lets you power real-time personalized recommendations and activity feeds using a simple API
Learn More
-
@lastNick 👍🏻 LinkedIn is definitely not a requirement for a manager role. Doesn’t mean it doesn’t help though
-
an up to date LinkedIn profile will mean a lot to certain hiring managers. at the most simple level it’s a way of showing that you want to exist in the professional world and are in touch
every time someone applies for a position i’m hiring for, i look if they linked out to a GitHub repo and then look at LinkedIn
my favorite thing to do on an interview is ask about code from a shared GitHub repo. immediate connection with the developer bc they know you cared enough to look at their work and it’s an easy transition into their thought process to get a feel for their skill set
if you are trying to get hired and move into manager roles, i’d say having a LinkedIn profile is more important. if you want to stay a dev forever, probably not very important -
just as a side note, anyone interested in seeing the power of graphql I’d suggest checking out hasura. very cool graphql engine
-
why is it not great for data pipelines? it does not allow streaming responses, so you must load everything and send it in one response. also, if you are querying multiple levels down, a simple implementation of graphql will most likely do a lot of individual additional queries (think about querying a collection of posts and the author. each N post returned will use its resolver and make a separate query for the author)
-
I’ve used graphql on 4 production products over the last 4 years
if you have devs who know what they are doing, it can be magical
I think if you have a good understanding of it, you can actually build your graphql implementation piece mail on top of the REST api if you need - I’ve done this for certain endpoints so the functional REST api is accessed and documented through the gql schema
I disagree that it’s great for data pipelines - it can be used that way but it excels in frontend applications where proper implementations allow for pulling only the data you need while going multiple levels deep
🧵 -
@scor I’m American haha I have no idea how European pay cycles are setup
-
3130€ / week?
-
😞@jonas-w
-
can’t you just track if a gift has a gifter and give them access to memberships they gifted? that doesn’t seem unreasonable - it’s like any group admin granting access to a subscription service then revoking it
-
“good” is relative to you so think about frustrations and enjoyment you’ve had in the past and ask pointed questions around those
for example, if you have strong preferences on being contacted outside of business hours, ask “how often do employees communicate outside of business hours?” or if you get caught up in how well defined tickets are ask “what is the process and expectations for defining tickets and handing those off to developers?”
those are 2 questions that the same answer could be extremely attractive to one person and a red flag for another, but everyone has different preferences so you need to think about that for yourself -
@nitwhiz "It's for big boi stuff". Not sure that really means anything
I've done consulting work for a lot of big bois (Fortune 500 companies) and all the ones that had Java apps seemed to be doing whatever they could to get off them
Sure, Java has it's place, but it's not the only reasonable solution for priority systems -
@karma Trying to avoid duplicate inputs so we don't end up with something like "Schwab" and "Charles Schwab" as options type thing. The options shouldn't change even annually, so for the use case it doesn't make sense to allow adding free input options
-
@karma no, they actually have been around for decades and are very successful