Let's just ask it.
🧔🏻♂️ You: How can software engineers make the best use of generative AI technologies?
🤖 ChatGPT: To make the best use of generative AI technologies, software engineers can:
| // Testing State Setters | |
| // const [payload, setPayload] = useState({}) | |
| it('can update the number of times to loop', () => { | |
| const mockSetPayload = vi.fn() | |
| const mockPayload = { | |
| timeOfLoop: 0, | |
| amount: 0, | |
| units: 'hours', | |
| exitCondition: { | |
| groups: [], |
| eval "$(/opt/homebrew/bin/brew shellenv)" |
| // https://stackoverflow.com/questions/55187563/determine-which-dependency-array-variable-caused-useeffect-hook-to-fire | |
| // https://github.com/simbathesailor/use-what-changed/tree/master | |
| // https://dev.to/vsramalwan/ways-to-handle-deep-object-comparison-in-useeffect-hook-1elm | |
| import { toJS } from 'mobx' | |
| import { useEffect, useRef } from 'react' | |
| import type { EffectCallback } from 'react' | |
| export interface Update { | |
| oldValue: any |
| import { renderHook } from '@testing-library/react-hooks/dom' | |
| import useDebounce, * as allDebounce from 'hooks/useDebounce' | |
| describe('debounce', () => { | |
| it('calls as expected', () => | |
| new Promise<void>((done) => { | |
| const callingArgument = 'debounce it!' | |
| const debounceCallback = (value: string) => { | |
| expect(value).toBe(callingArgument) |
Having fellow developers check your code (and checking theirs in turn) helps eliminate mistakes, clean the codebase, and share knowledge across the team. Code review is a purely human communication process. And a good way to approach humans (especially the ones you need to work with) is with empathy. This includes the obvious: politeness, kindness, and respect. But you can go a step further and remember that when you're assigning reviewers to look through your code, you're requesting another person's time and energy. Therefore, it's nice to make the process easier for them, and doing so will probably result in a more efficient code review. So, keeping empathy in mind, let's discuss some practical tips that can make your code reviewers happier.
The branch name is your first opportunity to give your task context. In case your reviewer decides to check the code out locally, they will need to find that branch among many others. Prefix the br
| import type { PlaywrightTestConfig } from '@playwright/test'; | |
| import { devices } from '@playwright/test'; | |
| /** | |
| * Read environment variables from file. | |
| * https://github.com/motdotla/dotenv | |
| */ | |
| // require('dotenv').config(); | |
| /** |
| <div className="flex gap-3 justify-between"> | |
| <div className="animated-label w-full"> | |
| <fieldset> | |
| <input | |
| defaultValue={user?.FirstName} | |
| id="first-name" | |
| name="first-name" | |
| type="text" | |
| autoComplete="given-name" | |
| className={`${inputStyles} ${hasError['first-name'] && 'border-red-500'}`} |
| # Game of Life | |
| ffmpeg -i audio.wav \ | |
| -vsync vfr -filter_complex "life=size=1920x1554:mold=10:rate=60:random_fill_ratio=0.1:death_color=#ff32ff:life_color=#33feff[left]; \ | |
| [0:a]showspectrum=mode=separate:slide=scroll:color=rainbow:scale=cbrt:size=1920x1554[right]; \ | |
| [0:a]showwaves=size=3840x606:mode=p2p:rate=30:colors=0xff32ff|0x33feff[bottom]; \ | |
| [left][right]hstack[top]; \ | |
| [top][bottom]vstack[out]" -map "[out]" -map 0:a -c:v libx264 -profile:v high -bf 2 -g 30 -crf 18 -pix_fmt yuv420p -c:a aac -b:a 384k -r 48000 -shortest -movflags +faststart -threads 0 | |
| # Cellauto | |
| ffmpeg -i audio.wav \ |
Some notes for working on and with the Tascam 414 Portastudio 4 Track Recorder deck.
The gap between Erase and Write is 0:00:245 in length at normal speed, 0:00:301 at slow speed.
This is a generic clear tape loop from WarbleLoopLab. The tape has a particular constant warble, to the point a clear sine tone cannot be read out enough to get an exact key difference. The BPM difference is also impacted by the extreme warble, where it will skip ahead or completely stop on occasion.
