[FULL WORKSHOP] AI Coding For Real Engineers
https://t.co/gd8WB3r5x6
A hands-on workshop covering the full lifecycle of AI-assisted development, from turning ambiguous requirements into agent-ready plans to running autonomous coding agents that ship production features. You'll learn to stress-test vague briefs into structured PRDs, slice work into thin "tracer bullet" vertical slices, and run an AI agent with TDD. You'll watch it select tasks, write tests, implement code, and commit. You'll then refine your prompts based on where it struggles, graduate to fully autonomous (AFK) runs, and learn to design codebases that maximize agent effectiveness.
You'll walk away knowing how to:
- Turn ambiguous requirements into agent-ready issues
- Slice work into vertical tracer bullets an agent can grab independently
- Run AI agents human-in-the-loop and autonomously with TDD
- Design codebase architectures that AI agents love to work in
For: Engineers ready to move beyond chat-based AI assistance and build a real workflow for shipping features with autonomous coding agents.
I have been working on Obsidian Reader for a over a year. I didn't want to share it until I felt it was good enough. It's finally there.
Consistent formatting for any article. Outline, syntax highlighting, nice footnotes, adjustable typography.
Runs locally. Just rules, no AI.
We've added a new command to Claude Code called /insights
When you run it, Claude Code will read your message history from the past month. It'll summarize your projects, how you use Claude Code, and give suggestions on how to improve your workflow.
Some folks say AI is bad in big codebases. I don't think that's right - I think it's bad in bad codebases.
AI has no memory. Unlike you, it can't accrue understanding of a crappy codebase by banging its head against the wall over and over.
A well-structured codebase lets a new developer start and contribute quickly. Related code is grouped together, deep modules have simple interfaces, and feedback loops like types and tests let you know when you screw up.
Maybe the AI isn't the problem. Maybe it's your code.
Obsidian is now free for work.
Starting today, the Obsidian Commercial license is optional. Anyone can use Obsidian for work, for free. If Obsidian benefits your organization, you can still purchase Commercial licenses to support development.
Nothing else is changing. No account required, no ads, no tracking, no strings attached. Your data remains fully in your control, stored locally in plain text Markdown files. All features are available to you for free without limits.
Why make this change? Simplicity. The Commercial license terms were confusing and added unnecessary complexity to our pricing. Furthermore, as the Obsidian Manifesto states: "we believe that everyone should have the tools to think clearly and organize ideas effectively". This change brings us closer to that principle.
People in over 10,000 organizations use Obsidian. Many work in high-security environments, like government, cybersecurity, and finance. Some of the largest organizations in the world, including Amazon and Google, have thousands of employees using Obsidian every day. These teams rely on Obsidian to think more effectively and keep total ownership over private data.
Previously, people at companies with two or more employees were required to purchase a Commercial license to use Obsidian for work. Going forward, the Commercial license is no longer required, but remains an optional way for organizations to support Obsidian, similar to the Catalyst license for individuals.
Organizations that support Obsidian are now featured on the Obsidian Enterprise page. Your organization can be showcased by purchasing 25 licenses or more.
Along with Commercial and Catalyst support, our add-on services, Sync and Publish help Obsidian remain 100% user-supported. In the future, we hope to offer more services designed for teams. As always, these will be optional.
TeamCity is rethinking UI with Pipelines. Looks slick!
I like how smart features like build tool integrations, job reusing, and parallel testing are exposed. The hardest part is to teach users that CI tool can do more than just scheduling bash scripts.
🎉 Exclusive interview!
TeamCity's @MarcoBehler sat with Nana Janashia @njuchi_ to chat about all things #DevOps. Watch as Nana dives into the latest trends and tests TeamCity Pipelines live.
See the full interview 🍿 https://t.co/M8HGqnLfW0
IntelliJ IDEA 2024.1 introduces an overhauled terminal featuring both visual and functional enhancements to streamline command-line tasks. #NewInIntelliJIDEA
Learn more in this blog post. 👇
https://t.co/5feKwyciTF
@yoctopokey@burdiyan You shouldn't be pulling the parent into a feature branch, you should be rebasing your feature branch onto the parent. I can't think of any practical reason to pull into your branch unless its NOT the parent.
Merge vs. Rebase vs. Squash. Anyone who says "100% of the time you <merge/rebase/squash>" is wrong and I'm strong in that opinion. I'm asked about this pretty regularly, so I decided to take my copy paste answer I always use and put it in a gist. 🍿 https://t.co/LqXLbRsuNE
🐧 Cyber Monday is here 🐧! 65% off bundles, power bundles & IT professional programs + 50% off individual courses & certs + 10% off THRIVE-ONE annual subscriptions. Enroll today: https://t.co/SMAwoP5ABC
#Linux#CloudNative#ITCertifications#Training