bgxor

My experience is that a11y is often not a priority and then one day it is suddenly the highest priority. It is not fun to have to drop everything you are doing and retrofit and/or redesign to avoid a lawsuit or losing a big contract.

The easiest thing you can do is run a linter with an a11y plugin to make sure you cover the basics. It can be annoying at first, but you'll get used to it.

A tool like axe (https://github.com/dequelabs/axe-core) is good for checking your work and/or automating away some of the less obvious stuff. It provides both a Chrome plugin and an automated checker for CI.

Getting comfortable enough with this stuff that it no longer requires a ton of work is definitely a good goal. Your users will have a better time overall and you'll have peace of mind.

I sent you a more detailed email, but basically it is preposterous to assume a "very experienced" senior engineer in ANY part of the United States is going to be happy with making $65K.

Those salary modifiers are atrocious. Their range in my city for a senior, very experienced engineer is comparable to what most entry level jobs actually offer around here.

I 100% think you are on the right track. The only people from my area that would take a GitLab salary just can't get a job elsewhere.

First and foremost, be nice. Secondly, you should assume that anything you "need" will not be built by anyone but you. If you end up with a "showstopper" in OSS, it is time for helpful contributions. Either that or you should find a different solution. A helpful contribution might including opening a civil dialogue about a feature. "Is this a feature that the project could consider within scope? How could I go about adding that feature?" Ask for guidance; don't demand solutions.

I would really encourage you to give it a try. The "jQuery mimicking" is actually not even its best feature. I didn't think much of it at the beginning, but it pretty much makes React's test utils really pleasant to work with. All in all, it basically codifies and gives a reusable api to most of what you say in your gist.

I appreciate the apology. My advice would be to take introductions from qualified applicants seriously. I do understand that you are a very busy person, but you should either hire someone to handle the hiring process or take the time to respond to with a simple "We went with someone else."

1. I had a video technical interview and it went well.

2. The interviewer said I would make a great fit and tried to introduce me to the CTO.

3. I introduced myself to the CTO and received no response.

4. I contacted the interviewer a week later. He apologized and tried to contact the CTO again.

5. I contacted the interviewer another week later. He apologized and tried to contact the CTO again.

6. I contacted the interviewer another week later and he said something along the lines of "We filled the position, sorry we are unprofessional."

Just a quick warning: these guys wasted a lot of my time.

In this "growth above all else" ecosystem, do you think profit sharing could possibly be just as bad? I'm not sure how those deals are usually set up, but unless you set aside a portion of revenue to share I could see people losing out here too.

Do you know of good examples of this working? I'm interested in how it might work with a typical startup.

I find it really hard to believe that anyone can actually "work" for 80 hours a week. Especially in mentally taxing work like designing and implementing software. That is something close to 9am-9pm 7 days a week. You pretty much have to be heavily medicated to even make it out to the other side if that. Maybe it's possible if you simply spend several hours a day in meetings or wasting time, but that is another issue altogether.

I have a sneaking suspicion that these 80 hour work weeks people brag about actually boil down to an anecdote about a terrible week they once had when they needed to get the job done quickly or lose their company. People that don't really understand what this kind of work entails just perpetuate these ideas because of some perverse idea of work ethic they get from reading about irrational people like Elon Musk.

I've got some breaking news for this "CEO" if he is for real and actually thinks an 80 hour work week is in any way a decent idea; the thing you are creating is not that important. You might think it is, but you are wrong. That is the hard but certain truth, and I truly hope you learn that in the least painful way possible.

If the Earth was suddenly going to be destroyed by an asteroid in just a few weeks, you'd be right to sacrifice the physical and mental well being of your brilliant team in ways like this to stop it. Even at that point you'd be better off with rotating fresh minds to figure it out.

Long story short, you are lying or just kidding yourself. Either way, you are doing a bad thing for the world.