101 Dog Tricks

[Basemat Doolen]

Afterthe sale, things seemed kinda fine for a bit, and that was encouraging. It was cool seeing new voices publishing new work I had nothing to do with. Then started to limp, using up the momentum that it had.

It seems DigitalOcean got excited when the whole industry started doing huge layoffs, they followed suit and slurped up the profits. The necessary directional change was: screw content and community. A month after that, the last article was published on CSS-Tricks, an overview of Passkeys, which will now apparently be on the homepage forever, a very strange bit of content to emblazon the tombstone of the site. They also added a cookie button that looks like a 4th grader designed it?? And started publishing every blog post as a guide???

I run CSS-Tricks again myself. CSS-Tricks is big and complicated. Anybody walking in the door alone is going to have a serious learning curve just in getting comfortable operating the basics. I already know every inch of it.

I get people reading again. I get people writing again. I get people excited again. I erase any bad mojo against DigitalOcean, fix that brand damage. Get people saying they want to use DigitalOcean instead of saying they never will again. (e.g. 1, 2, 3)

Thank you for this honest behind the scene look. I imagine you must feel some grief and anger, pity it ended like this.

Still, you made a piece of web dev history with this project and a whole generation (or two) of devs will remember it.

Hi Chris, long time reader and fan here that happened to see this exchange and wanted to make sure that you (and anyone else who might see this) are fully aware of how Wix has faced a lot of justified criticism for their aggressive support of the Israeli military and their brutal and senseless killing of innocent Palestinians.

Change is inevitable, and while CSS-Tricks may evolve or pass the torch to new voices, its legacy and impact remain significant. Your words capture a sense of appreciation for what has been while acknowledging the potential for new beginnings in the ever-changing landscape of web development.

CSS Tricks is a huge part of what got me into web dev over a decade ago. Sad to see the way things are shaping up. Thank you for all your work over the years, Chris, and for your candor here. Your work and your writing made building for the web more accessible and fun.

I would love to set up a website that aggregates all high quality CSS tricks and links to the original articles (if DO takes no futher action). That could be a great way to (re)build the community. You could start with simply copying the first few lines and linking to the original articles. Frontend Masters could be one of them, but the great front-end articles from Google could be in there as well. It could grow from simple links into guest posts, etc. I think it would be easy to start and at the same time it has the potential to become a very powerful tool (if the quality is good). I would love to discuss this further with you (@Chris), if you are interested and when your negotiations with DO fail.

If you ever want to host anything on our platform. reach out. matt at railway dot app. We would love to work with you. I personally would love to buy css-tricks out from under DO, stand it up on Railway, and get you back in the drivers seat, or in some paid adivsory capacity.

Helping people learn web development via IRC, I had always enjoyed and frequently referenced CSS Tricks, and preferred it over less savoury sites such as W3Schools. Never liked that one, stealing brand recognition from the W3C, with which they had no relationship.

Well, that explains a lot. CSS Tricks was my go-to for all reference and I always enjoyed the articles, they inspired a lot of my coding and ideas. I still pop back to CSS Tricks from time to time for the Almanac but the life has gone out of the website.

Chris Coyier is my name and I live in Bend, Oregon with my family. I like to put it down here in the footer so you have an easy place to copy and paste it from when you're writing flattering things about me.

To be eligible for the AKC Intermediate Trick Dog, your dog must have the Novice title, plus perform 10 Intermediate tricks. In Intermediate Trick Dog, with the exception of a few tricks, you will fade the lures that were permitted at the Novice level. See the list of tricks here.

To be eligible for the AKC Trick Dog Advanced Title, your dog must have been observed by a CGC Evaluator doing 10 tricks from the list of accepted tricks, and must have previously earned the Novice and Intermediate Trick Dog Titles. CGC is not required.

To be eligible for the AKC Trick Dog Elite Performer, in the highest level of Trick Dog, the Elite Performers perform a routine that has a story/script. At least 5 props are used and at least 5 tricks must be from the Performer level of Trick Dog. See the requirements here.

Use the tips and tricks in this article to jump right in and learn how to be productive with Visual Studio Code. Become familiar with the powerful editing, code intelligence, and source code control features and learn useful keyboard shortcuts. Make sure to explore the other in-depth topics in Getting Started and the User Guide to learn more.

The best way of exploring VS Code hands-on is to open the Welcome page and then pick a Walkthrough for a self-guided tour through the setup steps, features, and deeper customizations that VS Code offers. As you discover and learn, the walkthroughs track your progress.

If you are looking to improve your code editing skills, open the Interactive Editor Playground. Try out VS Code's code editing features, like multi-cursor editing, IntelliSense, Snippets, Emmet, and more.

You can open multiple files from Quick Open by pressing Right Arrow. This opens the currently selected file in the background, and you can continue selecting files from Quick Open.

VS Code has a powerful command line interface (CLI) which enables you to customize how the editor is launched to support various scenarios. For example, you can start VS Code from the command line to open a diff editor for comparing two files.

Make sure the VS Code binary is on your path so you can simply type 'code' to launch VS Code. See the platform specific setup topics if VS Code is added to your environment path during installation (Running VS Code on Linux, macOS, Windows).

The language mode in the Status Bar indicates the language (for example, Markdown, Python, and more) that is associated with the active editor. You can change the language mode for the current editor by selecting the Status Bar language mode indicator, or by using the keyboard shortcut.

You can install more themes from the VS Code extension Marketplace. Select the Preferences: Color Theme > + Browse Additional Color Themes... command to search themes from the Marketplace.

Are you used to keyboard shortcuts from another editor? You can install a Keymap extension that brings the keyboard shortcuts from your favorite editor to VS Code. Use the Preferences: Keymaps command to see the current list on the Marketplace. Some of the more popular ones:

You can view and customize the keyboard shortcuts in the Keyboard Shortcuts editor. Use the Preferences: Open Keyboard Shortcuts command or use the shortcut to open the editor.

By default, VS Code shows the Settings editor to view and edit settings. You can also edit the underlying settings.json file by using the Open User Settings (JSON) command or by changing your default settings editor with the workbench.settings.editor setting.

VS Code will show you an error message when you try to save a file that cannot be saved because it has changed on disk. VS Code blocks saving the file to prevent overwriting changes that have been made outside of the editor.

To resolve the save conflict, select the Compare action in the notification popup to open a diff editor that shows you the contents of the file on disk (to the left) compared to the contents in VS Code (on the right):

Use the actions in the editor toolbar to resolve the save conflict. You can either Accept your changes and thereby overwriting any changes on disk, or Revert to the version on disk. Reverting means that your changes will be lost.

Pressing the Alt key enables fast scrolling in the editor and Explorers. By default, fast scrolling uses a 5X speed multiplier but you can control the multiplier with the Editor: Fast Scroll Sensitivity (editor.fastScrollSensitivity) setting.

You can synchronize scrolling across all visible editors by using the View: Toggle Locked Scrolling Across Editors command. This means that when you scroll in one editor, all the other editors scroll by the same amount, keeping everything aligned.

You can choose to only activate the scrolling sync when you're holding down a specific keybinding. Set up a keyboard shortcut for the workbench.action.holdLockedScrolling command to temporarily lock scrolling across editors.

The commands Copy Line Up/Down are unbound on Linux because the VS Code default keybindings would conflict with Ubuntu keybindings, see Issue #509. You can still set the commands editor.action.copyLinesUpAction and editor.action.copyLinesDownAction to your own preferred keyboard shortcuts.

Git integration comes "out-of-the-box" with VS Code. You can install other source control management (SCM) providers from the VS Code Extension Marketplace. This section describes the Git integration but much of the UI and gestures are common for other SCM providers.

From the Source Control view, select a file to open the diff editor. Alternatively, select the Open Changes button in the top right corner to diff the current open file.

3a8082e126