AngeloR

What always bothered me about DE&I initiatives is that they are trying to wring diversity out of their existing hiring pool.

If your indeed job posts didn't bring diverse candidates then, why do you think it would now? Because you added a "Please apply if you're DiVeRsE" line to it? Don't be ridiculous.

If you want diversity of candidates you can't keep going back to the same talent pools. You have to diversify where you're drawing talent.

If your college program is primarily getting white/asian males, you can't suddenly expect it to start throwing in women & poc as well. You can't suddenly expect it to start giving you LGBTQ+ candidates.

If you want diverse candidates, you have to look at diverse hiring pools. Look at the bootcamps that focus on diverse groups you're targeting. Look at schools that focus on diverse groups you're targeting.

If you're really interested in diverse candidates, you can't keep expecting them to just show up if you add a "We want diversity!" to your job description - you have to change where you look for them.

If you have the option of having dual-language queues then you can also opt to the secondary language which generally has fewer callers than the primary. So you get to the front of the line faster, and they also tend to speak the primary language.

I think this is just the start for some bad things are patreon...

This video of execs at Patreon apparently turning a blind eye to employees calling out patreon users that were selling images of underage children: https://twitter.com/TizzyEnt/status/1315626557688483841?s=20...

They also laid off their ENTIRE security team: https://techcrunch.com/2022/09/09/patreon-security-layoffs/

I haven't dug into Alpine.js, but I've been messing with HTMX on some personal projects for a few months now and am really pleased with it. It's honestly made it a pleasure for me to return to front-end work.

Wow sounds like exactly what happened at a $previousCompany-1 and exactly what prompted me to leave.

I think at the moment blockchain is synonymous with "crypto".

Imagine you fell for a ponzi scheme. Now imagine you knew where the person who ran that ponzi scheme was.

The remark is a bit flippant (and feels grammatically incorrect) but the sentiment remains.

Lots of people view crypto as a get-rick-quick scheme on both sides. Even after warnings of "don't put any money in that you aren't comfortable losing" people put in money that they aren't comfortable losing. Coupled with the fact that most of these crypto projects maintain very high levels of community involvement (normally through discord/twitter). Sometimes when people lose a lot of money they lash out at the systems they lost money through. So they turn on the devs of whatever chain/token they gambled on.

The characters are selected because they possess specific characteristics that make them ideal to handle various cases.

p possesses maximum "descent" for a character (the bit below the baseline on a font).

É not only meets the traditional "ascent" but exceeds it since diacritics normally extend past the traditional ascent on a capitalized letter.

These aren't the only characters that possess these values (although, I assume some selected code points are unique), but just ones that do.

Are the keyboard mounts purchasable through Dygma as well? I've been looking for decent chair-based split keyboard mounts and am having a hard time. I found some mouse-stands that attach to chairs, but they end up being a bit too small in all the wrong places.

(Canada Specific) There can be additional tax implications depending on if you're contracting under your own name vs. a company. Using materials supplied from the companies you're contracting from can get you labeled as a Personal Services Business and not a corporation essentially treating corporation income as your personal income. This means you'd be subjected to personal income rates vs. corporation.

It's important to note it's not just this one thing that can do it, but there's a collection of things that can get you labeled as a PSB.

This is 100% a side-effect of GitHub. Open Source used to have the additional barrier of mailing lists to detract from "drive-by PRs". The side effect, of course, is that it made it much harder to get involved. GitHub really brought a lot of new eyes on open source software and lowered the barrier to contribute exacerbating (an argument could be made for creating) the drive-by PR problem.

I've been thinking about code reviews a lot.. and I think a big problem with existing code reviews is that for most orgs, code reviews were a way to move planning to the end of the development process instead of keeping it up-front.

I think the foundation of the pyramid (API and Implementation semantics) is often discussed in code reviews when it should have almost no place. By the time you get to the code review not only should these have been ironed out and shared with the whole team. What you should be looking at is simply adherence to the plan, and calling out deviations.

I wrote about a small rat about this: https://xangelo.ca/posts/code-reviews-are-failure/

The only thing I've really found that works for me has been ilograph[1] that allows you to draw your diagram and then create different "views" into it depending on what the focus of the diagram is. Here's a wonderful demo of what it would look like converting some AWS architecture diagrams into ilograph ones[2].

I'm not affiliated with this project at all - I just really love it.

[1] https://www.ilograph.com/ [2] https://blog.ilograph.com/posts/fixing-aws-architecture-diag...

I have no idea what a full list looks like.. but the nginx:1.17.10-alpine docker image contains the following:

    / # nginx -V                              
    nginx version: nginx/1.17.10
    built by gcc 9.2.0 (Alpine 9.2.0)
    built with OpenSSL 1.1.1d  10 Sep 2019

I ended up remapping `jj` to `ESC`. I use vim+tmux and so I remapped Caps Lock to CTRL.

What sort of issues are you running in to?

I might be reading that link wrong, but it looks like it says that Variant 2 is a possibility, just not demonstrated yet. This may be preemptive on their end.. or maybe they were able to replicate it in-house.

Branch prediction is related to the Spectre attack. I believe AMD is only unaffected by Meltdown.

It depends on what you're currently using, how you're using it, and why. There are plenty of things from the easy but expensive (reserved costs) to the hard (rearchitecting). Depending on where you are in development and how much money you have there are plenty of things you could potentially do.

Ontario, Canada - Without traffic it's about an hour.. with traffic (which is what my commute is) it's about 1.5 hours there, and 2 - 2.5 back home.

I took a 1/3 pay cut to work at a startup because I believe in what the company is trying to do. That's the only reason I keep doing what I do, because the long term goal for the company is in line with my beliefs. Even though I commute for 2+ hours each way, work long hours, and am on call 24/7 for the last 3 years. At some point it may become too much, or another offer might be more interesting, but at the moment, I believe very much in what the company is trying to do.

> Is it just me, or is Javascript (and more generally, all front end technology) more susceptible to these trivial holy wars?

What constitutes holy wars are often the most accessible[1]

[1] https://en.wikipedia.org/wiki/Law_of_triviality

Instead of spending money on a vps for my last side project, I went the heroku route and it was even easier. I spent 7$ on a private github repo.. which synced to heroku. And a free CircleCI account that also synced up with everything. Then just pushing my branch meant, automated testing and with heroku pipelines, a PR meant automatic test env.

Just found out about it as well - and it seems way better than any of the others. It'll probably default to being my standard front-end framework. It abstracts just the right parts of things.

Could it have? Sure.

Is it probable that it would have been prevented? No.

Look at the number of open-source projects that have had vulnerabilities in them for years. Open Source does not translate to "we know exactly what's going on in this code", it just means the source is available. Open source is not some magic catch-all for shitty or purposely misleading code.

Like: Fogbugz (small-ish team), Trello (small team)

Don't like: Jira, Whiteboard (like.. literally a whiteboard)

Want to try: Zenhub

I've seen it in a lot of places - however, just because they sent you a contract does not mean you have to sign it - you are still in the negotiation period. This means that you can edit the contract as both parties see fit. Your best recourse is to just mention it to them and ask them to amend that portion.