# Development Environment Published articles for Development Environment. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Designing Claude for ears, not eyes: An accessibility skill for blind and low-vision users DevFeed: [Designing Claude for ears, not eyes: An accessibility skill for blind and low-vision users]() Original publisher: [Read original article]() Author: Nubank Editorial Published: 2026-09-16T14:09:16Z Content type: article Language: en Sources: [Nubank]() Topics: [Accessibility](), [Claude](), [User interface design](), [screen](), [Users](), [Development]() Tags: [accessibility](), [accessible](), [claude](), [culture-values](), [data-science-machine-learning](), [development-environment](), [engineering](), [inclusive](), [life-at-nu](), [people-with-disabilities](), [text](), [users](), [vision]() ### AI overview Nubank describes BLIND-CLAUDE.md, an instruction set that adapts Claude responses for people who primarily use screen readers or read-aloud functionality. The approach treats auditory comprehension as an engineering constraint and changes behavioral instructions without modifying Claude or adding a native accessibility feature. ### Source excerpt How a cognitively diverse IT team at Nubank, they coded screen reader-friendly rules into Claude's instructions, treating auditory comprehension as an engineering constraint The post Designing Claude for ears, not eyes: An accessibility skill for blind and low-vision users appeared first on Building Nubank. ## Designing Claude for ears, not eyes: An accessibility skill for blind and low-vision users DevFeed: [Designing Claude for ears, not eyes: An accessibility skill for blind and low-vision users]() Original publisher: [Read original article]() Author: Nubank Editorial Published: 2026-09-16T14:09:16Z Content type: opinion Language: en Sources: [Nubank]() Topics: [Accessibility](), [Claude](), [Users](), [screen]() Tags: [accessibility](), [claude](), [configuration](), [culture-values](), [data-science-machine-learning](), [development-environment](), [life-at-nu](), [people-with-disabilities](), [vision]() ### AI overview Nubank describes BLIND-CLAUDE.md, an instruction set that adapts Claude responses for developers who primarily use screen readers or read-aloud tools. The approach addresses conventions such as Markdown tables, diffs, diagrams, long logs, and spatial references by adding behavioral instructions without modifying Claude or introducing a native accessibility feature. ### Source excerpt How a cognitively diverse IT team at Nubank, they coded screen reader-friendly rules into Claude's instructions, treating auditory comprehension as an engineering constraint The post Designing Claude for ears, not eyes: An accessibility skill for blind and low-vision users appeared first on Building Nubank. ## Improving Developer Experience, Level 4: Optimizing Feedback Loops: Tools, Tests, and Teamwork DevFeed: [Improving Developer Experience, Level 4: Optimizing Feedback Loops: Tools, Tests, and Teamwork]() Original publisher: [Read original article]() Author: tobi@techunicorn.builders (Tobias Mende) Published: 2023-09-02T04:00:00Z Content type: article Language: en Sources: [Tobias Mende]() Topics: [Developer experience](), [Testing](), [code productivity](), [Development](), [ide](), [Hardware]() Tags: [collaboration-continuous-deployment-developer-experience-developer-productivity-ensemble-program](), [developer-experience](), [development-environment](), [efficiency](), [hardware](), [ide](), [testing](), [tools]() ### AI overview This article examines the technical layer of developer experience, focusing on reducing feedback delays through suitable development environments, responsive hardware, IDE tooling, and automated testing. It argues that faster compilation, linting, and testing improve productivity, refactoring, and confidence in maintaining software. ### Source excerpt Improving Developer Experience, Level 4: Optimizing Feedback Loops: Tools, Tests, and Teamwork Last week, we dove into focus, clarity, and flow. Today, we will delve into the top layer of Maslow's Hierarchy of Needs (DevEx Edition). Here, it gets a bit technical. While the three bottom layers are mostly concerned with culture, structures, and processes, the top layer includes technical and cultural aspects. This shows how important and foundational non-technical aspects are for outstanding developer experience. ## Searching for RH Counterexamples -- Setting up Pytest DevFeed: [Searching for RH Counterexamples -- Setting up Pytest]() Original publisher: [Read original article]() Published: 2020-09-11T15:51:48Z Content type: tutorial Language: en Sources: [Jeremy Kun]() Topics: [Pytest](), [Python](), [Testing](), [Code](), [Development]() Tags: [development-environment](), [git](), [github](), [mathematics](), [number-theory](), [programming](), [project-organization](), [pytest](), [python](), [riemann-hypothesis](), [setup](), [shell](), [software](), [testing]() ### AI overview A hands-on tutorial that sets up a Python 3.8 project with pytest and Git, using a search for counterexamples related to the Riemann Hypothesis as the example problem. It explains terminal-based project setup, testing, organization, and how design evolves during development. ### Source excerpt Some mathy-programmy people tell me they want to test their code, but struggle to get set up with a testing framework. I suspect it's due to a mix of: There are too many choices with a blank slate. Making slightly wrong choices early on causes things to fail in unexpected ways. I suspect the same concerns apply to general project organization and architecture. Because Python is popular for mathy-programmies, I'll build a Python project that shows how I organize my projects and and test my code, and how that shapes the design and evolution of my software. ## Automating OS X app test build distribution across multiple OS versions DevFeed: [Automating OS X app test build distribution across multiple OS versions]() Original publisher: [Read original article]() Author: Fraser Hess Published: 2013-12-17T18:21:08Z Content type: tutorial Language: en Sources: [Cocoa Is My Girlfriend]() Topics: [Testing](), [Mac Mini](), [Xcode](), [ide]() Tags: [app-distribution](), [apple](), [build](), [developers](), [development-environment](), [local](), [mac](), [ssd](), [sync](), [testing]() ### AI overview The article describes a Mac-based setup for testing OS X applications across multiple OS X versions. It uses a Mac mini running VMware Fusion virtual machines, an SSD to improve performance, and scripted Xcode build distribution synchronized across the test environments. ### Source excerpt With Apple now shipping OS X upgrades every 12-15 months, Mac developers are very quickly finding themselves supporting their apps on multiple OS X versions. Until recently, my approach to testing on multiple OS X versions involved partitioning an external USB drive and installing the OS X versions onto it and booting off the partitions [...] ## Using GIT In Xcode DevFeed: [Using GIT In Xcode]() Original publisher: [Read original article]() Author: Joe Keeley Published: 2013-12-10T06:50:31Z Content type: tutorial Language: en Sources: [Cocoa Is My Girlfriend]() Topics: [Git](), [Xcode](), [version-control](), [iOS](), [Development]() Tags: [bitbucket](), [command-line](), [commit](), [development-environment](), [git](), [github](), [ios](), [merge](), [undocumented](), [version-control](), [xcode]() ### AI overview This tutorial explains how to use Xcode 4.6.2 for Git workflows in iOS and Mac development. It covers creating local repositories, making an initial commit, and connecting projects to remote repositories such as GitHub or Bitbucket. ### Source excerpt Git has become a very popular version control system in iOS and Mac development. Git comes with a set of command line tools to check status, commit changes, view logs, make and merge branches, and coordinate commits with a remote repository. There are a number of desktop apps that can perform these functions, including Xcode. [...] ## Contributing to Django: quickstart DevFeed: [Contributing to Django: quickstart]() Original publisher: [Read original article]() Author: Graham King Published: 2011-07-07T05:01:55Z Content type: tutorial Language: en Sources: [Graham King]() Topics: [Django](), [Development](), [pip](), [SQLite](), [MySQL](), [PostgreSQL]() Tags: [developers](), [development](), [development-environment](), [django](), [guide](), [how-to](), [install](), [mysql](), [patches](), [postgresql](), [python](), [software](), [sqlite](), [tests](), [version]() ### AI overview A step-by-step guide to setting up a development environment for contributing to Django core. It covers installing pip and virtualenv, installing dependencies, running the test suite, creating patches, and keeping a checkout current. ### Source excerpt "Empowering Django developers: A step-by-step guide to setting up your environment." ## Environment Structure for Django Apps DevFeed: [Environment Structure for Django Apps]() Original publisher: [Read original article]() Author: Map Published: 2011-05-17T03:55:56Z Content type: tutorial Language: en Sources: [Craig Kerstiens]() Topics: [Django](), [Development](), [Python](), [PostgreSQL](), [Git](), [osx](), [Ubuntu]() Tags: [development](), [development-environment](), [django](), [git](), [osx](), [postgresql](), [python](), [setup](), [things](), [ubuntu]() ### AI overview A cookbook for structuring Django project environments on OSX and Ubuntu. It explains how to create a Python virtual environment, install Django and PostgreSQL dependencies, use requirements.txt and .gitignore, and prepare a repository for contributors. ### Source excerpt I've been writing applications off and on for nearly 4 years now, since before Django 1.0 was even released. I must say the framework could not be better described than by its own tagline "The Web framework for perfectionists with deadlines". Among the things I love about it are: However, after using the framework for nearly 4 years I'm just now discovering my preferred way of managing environments. I know there's still a bit of back and forth on development environment/IDE, but as far as configuring actual project environment I've become very comfortable with what I've now been using for many months. It also allows for someone else bootstrapping their environment incredible quickly as well. Below is a quick cookbook of how to do this on OSX and Ubuntu. $ sudo port install python27 $ sudo port install py27-virtualenv $ sudo port install postgresql90 Now for setting up your project: $ mkdir example $ cd example $ virtualenv-2.7 --no-site-packages . $ source bin/activate $ sudo brew install python $ sudo brew install virtualenv $ sudo brew install postgresql Now for setting up your project: $ mkdir example $ cd example $ virtualenv --no-site-packages . $ source bin/activate $ sudo aptitude install python sudo aptitude install virtualenv sudo aptitude install postgresql Now for setting up your project: $ mkdir example $ cd example $ virtualenv --no-site-packages . $ source bin/activate For those of you not familiar virtualenv is a self-contained python environment. It holds its own copy of python and any libraries you install. Now that you've setup your virtualenv we can go through the process of installing django and setting up your repository. This is the same across all of the above platforms: Add to a .gitignore file: bin build include lib .Python *.pyc Add to a requirements.txt file: Django==1.3.1 psycopg2==2.4.1 Then run: $ bin/pip install -r requirements.txt This should fully installed any of your required apps and makes it easy for others to do the same to begi