Nick Taylor nickytonline

How to Leverage Devin — A Practical Guide

Since you're already familiar with concepts like context rot, MCPs, skills, and RPI, this guide skips the basics and focuses on actionable strategies to get the most out of me.

1. Prompt Engineering for Devin

The single biggest lever. My success rate scales directly with prompt specificity.

You're right — that first list was the Code summit, not Europe. Here's the actual AIE Europe speakers from schedule.json:

Adrian Bertagnoli — Founding Engineer, Callosum — (no X) — linkedin.com/in/adrian-bertagnoli-bb3467178
Adrien Grondin — iOS Developer, Locally AI — x.com/adrgrondin — (no LI)
Alessandro Cappelli — Co-founder & CCO, Adaptive ML — (no X) — linkedin.com/in/alessandro-cappelli-aa8060172
Alex Cheema — Co-Founder, EXO Labs — (no X) — linkedin.com/in/alex-cheema
Amy Boyd — Microsoft Foundry DevRel Lead, Microsoft — x.com/AmyKateNicho — linkedin.com/in/amykatenicho
Andreas Kollegger — Director Applied AI Research, Neo4j — x.com/akollegger — linkedin.com/in/akollegger
Ara Khan — Fou

Goose Subagents Recipe Collection

A curated collection of powerful Goose recipes for code analysis, testing, documentation, and research.

📚 About

These recipes are specialized configurations for Goose subagents that help automate common development workflows. Each recipe is designed to be reusable, parameterized, and production-ready.

🚀 Quick Start

Beast Mode

Beast Mode is a custom chat mode for VS Code agent that adds an opinionated workflow to the agent, including use of a todo list, extensive internet research capabilities, planning, tool usage instructions and more. Designed to be used with 4.1, although it will work with any model.

Below you will find the Beast Mode prompt in various versions - starting with the most recent - 3.1

Installation Instructions

Go to the "agent" dropdown in VS Code chat sidebar and select "Configure Modes".
Select "Create new custom chat mode file"

On implementing a client for feature flags in your UI codebase

This document isn't an explainer on Feature Flags, you can find that with my amateur writeup, or literally hundreds of better writeups out there.

This document is also agnostic to the choice of service you'd use: LaunchDarkly or split.io or optimizely or whatever; that's orthogonal to this conversation.

Instead, this document is a list of considerations for implementing a client for using Feature Flags for User Interface development. Service providers usually give a simple fetch and use client and that's it; I contend that there's a lot more to care about. Let's dive in.

To encourage usage, we'd like for the developer experience to be as brutally simple as possible. So, this should be valid usage:

docker kill $(docker ps -q) to kill all running containers
docker rm $(docker ps -a -q) to delete all stopped containers.
docker volume rm $(docker volume ls -q) to delete all volumes.
docker rmi $(docker images -q) to delete all images.

Run all commands:

docker kill $(docker ps -q) && docker rm $(docker ps -a -q) && docker volume rm $(docker volume ls -q) && docker rmi $(docker images -q)

For fish shell, remove the $:

MOVED TO https://github.com/CodeMouse92/DEVModInACan

#BEGINNERS TAG REMOVALS

Non-Beginner Article

All articles on #beginners should be written for those new to programming, development, networking, or to a particular language. These posts should also require little to no prerequisite knowledge. If you wish, you may rewrite your post to meet these requirements, at which point you may request that the tag be added back. Otherwise, just use the appropriate technology tags. (Read more about the tag rules here.)

	import "https://deno.land/x/dotenv/load.ts";

	const response = await fetch("https://www.getrevue.co/api/v2/issues", {
	headers: {
	Authorization: `Token ${Deno.env.get("REVUE_API_KEY")}`,
	},
	});

	const issues = await response.json();