As some of you know, I am an avid homebrewer. And, I love my IPA’s and Pale Ale style beers. Sadly, they’re often high in ABV (alcoholic content), and as I get older, I want to appreciate what I drink and not have to worry about the hangover the next day if I have too many.
That is where my interest in non-alcoholic beers came from. Not wanting to compromise on taste and mouthfeel, I set out to see if brewing a low-alcohol beer (<0.5%) without compromise was possible.
Being a remote worker, a good tech setup is essential. A comfortable chair, nice desk, well-positioned monitor and a keyboard and mouse you love. Then there are the other parts that people don’t think about as much: webcam and microphone.
Before buying the Microsoft Modern Wireless Headset, I was using an AT2020+ microphone on a boom arm, which I use for streaming and other purposes. Then I got the Blue Yeti X, a great microphone, my primary one. It’s a great microphone, but I have to adjust the audio levels with it through my interface routinely.
Australia is a technology backwater, so we are no strangers to being left behind when it comes to the latest in wireless standards and internet speeds. Specifically, 5G promises to be bigger and better than 4G and the other protocols that came before it. I don’t know about you and whether disappointment is a global phenomenon, but I have found 5G quite disappointing.
With 5G, we’re talking about potential speeds of up to 10 Gbps, compared to 4G’s maximum theoretical download speed of 100 Mbps in the real world. That’s a significant improvement, but real-world speeds will vary based on several factors. The reality is nobody is getting anywhere near 10 Gbps outside of a lab.
I was really rooting for Microsoft with its ChatGPT integration into the Bing search engine. You might have seen the hype, including the hilarious controversy around Bing’s ChatGPT threatening journalists and being easily provoked.
After a few weeks of closed access and insurmountable hype, Microsoft has opened the floodgates to many more people, and Bing’s ChatGPT integration is a dismal disappointment.
Perhaps the passive-aggressive and threatening nature of Microsoft’s ChatGPT integration forced their hand. Still, after trying it for a while, it’s clear it isn’t a rival to the original ChatGPT anymore. Despite having access to up-to-date information, it has been dumbed down as it’s obvious Microsoft has cut both legs off to get it under control.
I have been dual-booting Ubuntu Linux on my main desktop PC for development. Docker on macOS and Windows with WSL suffers from severe I/O performance issues for “reasons”. Docker is infuriating to use outside of Linux, so I started looking for alternative builds.
My primary 3900x gaming PC feels a little sacrilegious to use as a dedicated Linux machine to run some virtual machines and a Webpack server. I am not solving cryptographic problems here, so I just primarily need storage and ram; a decent CPU helps.
The PlayStation VR 2 is Sony’s second attempt at a virtual reality headset. The PlayStation 4 had a PSVR headset, but it was marred by screen door, performance issues, a cacophony of cables and dildo-like move controllers with a convoluted tracking process. The PSVR 1 had some great titles but never felt like an adequately supported device.
My first foray into the PSVR 2 as someone experienced with virtual reality headsets was enjoyable. My point of reference is my HP Reverb G2 headset which is similar in specs to the PSVR 2 but is frustrating to use as I have encountered numerous problems with Steam VR and Windows Mixed Reality software. The PSVR 2 is comfortable, and getting lost for hours is easy.
When hiring front-end developers, there are many ways to evaluate candidates’ skills and abilities. However, some assessment methods can be exclusionary, while others may not accurately reflect the type of work the candidate will do.
In this article, we’ll explore some efficient ways to test front-end developer hires without relying on coding puzzles and algorithms and how to be mindful of inclusivity.
I come from a self-taught background, a time when self-taught invited increased scrutiny because being self-taught in the early to mid-00s wasn’t as common as it is now. We have numerous online courses, boot camps and other resources. When I learned to code, these thick phonebook-like books that came with one or more CD-ROM discs with software and code examples were how many learned.
If you’re distributing a package, say a plugin, you may want to test it against multiple Node versions (especially if you’re using Jest for tests). In my situation, I have a popular plugin for Aurelia called Aurelia Google Maps. It’s for Aurelia 1, but many people use it, so I wanted to test it against the LTS of Node and the latest version.
name: Node.js Jest Tests on: [push, pull\_request] jobs: build-and-test: runs-on: ubuntu-latest steps: - uses: actions/checkout@v3 - name: Use Node.js ${{ matrix.node-version }} uses: actions/setup-node@v3 with: node-version: ${{ matrix.node-version }} cache: 'yarn' - name: Install dependencies run: yarn install - name: Run Jest tests run: yarn test strategy: matrix: node-version: [18.x, 19.x] You will want to save this file in your .github/workflows directory at the root of your project. You can save it as whatever you want: run-tests.yml
I hate to be “that guy” that publishes a blog post and says, “Stop using X” and “Why you should be using X instead”, but after a recent situation in some code I wrote ages ago and updated, I felt it was worthy writing a blog post about why you should use globalThis instead. That’s not to say if you’re currently using window that you’re wrong (because globalThis aliases window in a browser context). However, by using globalThis, you can save yourself a lot of trouble, especially in unit tests.
If you have an application that has HTML imports like this import template from './my-component.html and then attempt to test this code in Jest 28+ (or previous versions, for that matter), you will get a syntax error similar to this one:
SyntaxError: Unexpected token ‘<’ HTML
Fortunately, there is an easy fix. Firstly, you need to install the package jest-html-loader. npm install jest-html-loader -D. Then you need to configure your Jest configuration as follows.