dmkirwan

Not yet - I'm going to add one to the homepage this week and also support a free trial.

I totally agree with you. Some of the content there seems relevant to CS in general, but I hate the fact that you need to study content that you won't use on the job in order to pass an interview. It doesn't make sense to me. I've seen new grads perform as well as senior engineers with these Leetcode-style questions so I've stopped using them to assess engineers. Further, I know we're specifically trying to assess technical ability in an interview, but that's not the whole picture for an engineer. They need to be able to take feedback well and provide good mentorship also. I think we miss this.

Inspired by some realistic interviews that I did recently, I've been working on something[1] that aims to equip companies to hire engineers using realistic assessment methods. It scales like Hackerrank, but I think it's fairer.

[1] https://devscreen.io/

The only true measure of your market value is what people are willing to pay you.

32k seems a bit low for central Europe but it's difficult to say without a more precise location.

There are easier (and less accurate) ways to assess your value.

1: Next time you hear from a recruiter, ask them what a rough range is for the role. If they won't tell you, try to gauge their reaction to your salary expectations. Say, when they ask, if you tell them you expect 50k and they are still willing to proceed then you can be sure that you can get a lot more than 32k.

2: Look out for salary surveys from your country (here's one from Ireland that's pretty good: https://www.morganmckinley.com/ie/ireland-salary-guide-calcu...).

3: This is probably the least accurate; look at salaries at companies that are transparent about compensation, like Buffer: https://buffer.com/salaries.

While the tech is constantly advancing, I have yet to use one in anger that fully solved my problem outside of giving me information that's already easy to find.

I think the only place it makes sense is in very very specific use-cases. Think about, say, a dental clinic. I would guess that if you put a human on chat support for a year in that setting, you'd see common themes emerging in customer problems. Maybe you develop a good library of canned responses and you find they work for 70 - 80% of queries, great. Then you could probably build a good chat bot to handle questions and handle cancelling/rescheduling appointments.

There is evidence that traditional software engineering interviews[1] assess a candidate's ability to perform under pressure better than their ability to do the job. I find it crazy that you need to spend weeks studying leetcode-style problems after doing the job all day in order to prepare for an interview.

Coincidentally, I've started working on a product to help this[2]. The general idea is that tasks like pull-requests, bug fixes and realistic take home projects are a better way to test candidates. Everything is done using Github, the tasks are all realistic and candidates can use their own laptop and development environment. It's not fully ready yet, but if anybody wants to chat about it just use the info@ address for the site.

[1] https://www.sciencedaily.com/releases/2020/07/200714101228.h... [2] https://devscreen.io/

Funnily enough, there's another web page on the NASA domain that outlines the "longer path" or "equal transit" theories as the correct cause of lift on an aircraft wing: https://www.grc.nasa.gov/www/k-12/UEET/StudentSite/dynamicso...

When I was studying for my PPL, they taught us using the equal transit theory, though the instructor couldn't help himself from telling us that it was a simplification. This video from Cambridge University illustrates what happens to the airflow over an aerofoil: https://www.youtube.com/watch?v=UqBmdZ-BNig

I was referring to the current controversy with licensing of co-pilot code and them serving ICE customers.

That's interesting. Was Github Enterprise too expensive or was there another reason you didn't use it? What advantage did partially moving to Gitlab bring? This question is coming from a genuine place of curiosity, in case that's not coming across via text.

Ethical concerns aside*, I far preferred Github to BitBucket. Bitbucket has been incredibly unstable for the last few years that I've been using it at work. I regularly see the "We're experiencing issues..." banner when I review pull requests. We don't use bitbucket pipelines, but they seem to be the most unstable part of the product. I haven't used Gitlab in years so I can't give any up-to-date commentary on that as a solution. I've never had issues with Githbub and I quite like their UI so that will be my preference for the foreseeable future.

*I appreciate this is a big caveat

Apologies if the title seems click-baity. It would have been too long if I included the new principles in there.

The new principles:

* Strive to be Earth’s Best Employer

* Success and Scale Bring Broad Responsibility

I don't work at Amazon, but it's my understanding that they take their leadership principles seriously and use them as they make decisions every day. They do not live up to these two new principles today, but this does seem like a significant step.