tonylampada

PR Review: Show annotation groups on Asset Library preview (DATAMAN-230)

Repository: roboflow/roboflow PR: #11061 Branch: dataman-230-show-annotation-groups-preview → master Author: @digaobarbosa Review Date: 2026-04-08

Summary

tonylampada

Video Script — "The System's DNA" (~3 min)

[0:00–0:30] The Problem (hook)

Have you ever looked at our codebase and wondered: "is it a Source or an Image? A Dataset or a Project? Why do we have both datasets[] and projects[] on the same record?"

These aren't just naming inconsistencies — they're symptoms of a missing piece. We never wrote down what our system actually is at the conceptual level. So over the years, storage details and legacy names leaked into services, routes, types, and UI code. And every new dev that joins has to reverse-engineer the domain from implementation artifacts.

[0:30–1:10] What This PR Introduces

tonylampada

Production Readiness Report - Support Debug Website

Author: Bar Shimshon (Support Team)
Project: roboflow-support
Review Date: 2026-01-26
Reviewer: Tony França / Jarbas (AI Assistant)

---

Executive Summary

tonylampada

#!/bin/bash

# Script to generate S3 signed URLs for image files in JSONL format
# Usage: ./generateS3SignedUrls.sh <s3-path> [output-file] [expiration-seconds] [parallel-jobs]
# Or with curl:
# curl -fsSL https://gist.githubusercontent.com/tonylampada/20b7bc984a455f53e2d07f88b33bf43c/raw/generateS3SignedUrls.sh | bash -s --  s3://bucket/path output.jsonl

set -e

# Check if S3 path is provided

tonylampada

a

tonylampada

Plumbing + Intelligence: A Practical Mindset for Software Architecture

1. Introduction

As I gained experience in building software, I realized a fundamental distinction between two types of code, which in my mind, I refer to as:

• "plumbing" code, vs
• "intelligence" code.

I want to explain this duality because I believe it assists in cultivating a programming mindset that tends to produce quality software (*).

tonylampada

Encanamento + Inteligência: um mindset prático para arquitetura de software

1. Introdução

À medida que eu fui ganhando experiência construindo software, percebi uma distinção fundamental entre dois tipos código, que, na minha cabeça, eu chamo de:

• código de "encanamento", vs
• código de "inteligência".

Vou explicar essa dualidade porque eu acredito que ela ajuda ter um mindset de programação que tende a gerar software de qualidade (*).

tonylampada

//////////////////////////////////////////////////////////////////////
// surface: handling http requests for login
// "app" is an express application
// "authenticationService" is a service that knows how to authenticate users

app.use(loggingMiddleware);
app.use(handleUnknownErrorsMiddleware);
app.post('/api/login', reqLogin);

function loggingMiddleware(req, res, next) {

tonylampada

// web framework

function webapp() {
  return {
    handlers: {},
    addRoute(route, fn){
      this.handlers[route] = fn;
    },
    exec(route, params){
      const handler = this.handlers[route];

tonylampada

// web framework

function webapp() {
  return {
    handlers: {},
    addRoute(route, fn){
      this.handlers[route] = fn;
    },
    async exec(route, params){
      const handler = this.handlers[route];