Steven Senkus

uncannyuse now has schema pages for Reality Composer Pro components—showing the exact USDA block RCP writes, field-by-field with types and sparse-authoring behavior, plus annotated fixture examples. 20 components covered so far. https://lnkd.in/dpsT2A-8

9

This is a great tutorial for folks looking to do some automated refactoring to their PHP codebase. I’ll be speaking on the same tool Saturday.

4

I built an automation system that submits building permits to Philadelphia's eCLIPSE portal. Without a single API endpoint from the city. - Queues permit jobs from our platform - Navigates the website programmatically (iframe detection, field resolution, dynamic element locators) - Runs 24/7 on Railway with real-time deploy logs Contractors in Philly spend hours manually entering the same data into government systems. This automation gives them that time back. Building in construction tech means working with systems that weren't built for you. #ConstructionTech #Automation #Railway #Philadelphia #Permits #SaaS

2

4 Comments

Accountability is the great equalizer of leadership. Without it, standards slip. Trust erodes. Culture drifts. I’ve led teams from 12 to 200+ people across commands spanning 100,000 square miles - and the most consistent factor in every high-performing team I’ve seen is accountability. It’s what aligns people behind one standard, regardless of rank or personality. In my latest video, I break down: 🔹 Why accountability separates good leaders from great ones 🔹 How to correct “organizational drift” before it destroys culture 🔹 When to move from verbal to written accountability 🔹 Why accountability can be both corrective and caring Watch the full breakdown here: 🎥 https://lnkd.in/eT2W6eZZ Let’s start a conversation - how do you build accountability without crushing morale? #Leadership #Accountability #OrganizationalCulture #LeadershipDevelopment #TeamBuilding #MilitaryLeadership #ElderMasterChief

1

I spent time in a newspaper newsroom watching the daily miracle unfold. Reporters filed stories, editors revised copy, fact-checkers verified information, layout designers arranged content, and printers prepared plates, all against relentless deadlines. What impressed me most was the version control: stories evolved through multiple drafts, yet previous versions were always accessible. The final product integrated contributions from dozens working in parallel. It hit me right then. That's how 𝐯𝐞𝐫𝐬𝐢𝐨𝐧 𝐜𝐨𝐧𝐭𝐫𝐨𝐥 𝐬𝐲𝐬𝐭𝐞𝐦𝐬 𝐚𝐧𝐝 𝐜𝐨𝐥𝐥𝐚𝐛𝐨𝐫𝐚𝐭𝐢𝐯𝐞 𝐝𝐞𝐯𝐞𝐥𝐨𝐩𝐦𝐞𝐧𝐭 work. When multiple developers work on the same codebase, you need systems to track changes, manage parallel workstreams, resolve conflicts, and maintain a clear history of every modification. 𝟏. 𝐔𝐬𝐞 𝐅𝐞𝐚𝐭𝐮𝐫𝐞 𝐁𝐫𝐚𝐧𝐜𝐡𝐞𝐬 𝐟𝐨𝐫 𝐈𝐬𝐨𝐥𝐚𝐭𝐢𝐨𝐧 Develop each feature or bug fix in its own branch to isolate changes until they're ready, preventing unfinished work from affecting the main codebase. 𝟐. 𝐈𝐦𝐩𝐥𝐞𝐦𝐞𝐧𝐭 𝐏𝐮𝐥𝐥 𝐑𝐞𝐪𝐮𝐞𝐬𝐭𝐬 𝐟𝐨𝐫 𝐂𝐨𝐝𝐞 𝐑𝐞𝐯𝐢𝐞𝐰 Require peer review before merging changes. This improves code quality, catches bugs, and shares knowledge. Automated checks help validate tests and style. 𝟑. 𝐔𝐬𝐞 𝐒𝐞𝐦𝐚𝐧𝐭𝐢𝐜 𝐕𝐞𝐫𝐬𝐢𝐨𝐧𝐢𝐧𝐠 𝐟𝐨𝐫 𝐑𝐞𝐥𝐞𝐚𝐬𝐞𝐬 Follow MAJOR.MINOR.PATCH: breaking changes increment MAJOR, new features MINOR, and bug fixes PATCH. 𝟒. 𝐌𝐚𝐢𝐧𝐭𝐚𝐢𝐧 𝐌𝐞𝐚𝐧𝐢𝐧𝐠𝐟𝐮𝐥 𝐂𝐨𝐦𝐦𝐢𝐭 𝐇𝐢𝐬𝐭𝐨𝐫𝐲 Write clear commit messages explaining why changes were made, not just what changed. Keep commits atomic for easier history tracking and reverts. Version control is the backbone of collaborative development, letting teams work efficiently while preserving project history and quality.

1

Check out this a brief demo of a small tool I have been building in the last couple weeks that turns dense federal appropriations PDFs into something regular folks can understand. Right now the pipeline looks like this: • A Next.js frontend uploads bills via presigned URLs straight into MinIO (S3-compatible storage). A FastAPI backend pulls the PDF, runs a parser that merges table cells and surrounding prose into structured rows, attaches page and bounding box metadata, and stores everything in PostgreSQL. • It then uses the OpenAI API to suggest cleaner program names and short summaries for each funding line. • From there the API can audit the table, generate diffs between fiscal years, export CSVs, and render highlighted snippets of the original PDF for context. Everything runs under Docker Compose: Postgres for relational data, MinIO for documents and images, FastAPI for the API, and Nginx as the single public entry point. The goal is to make it much easier to see what is actually being funded, compare versions of a bill, and link every number back to the source text. It's also a pretty neat use-case for use LLMs to create accessible tools that benefit everyone and break down barriers. Check out the code here: https://lnkd.in/eiQDzBuX

2