AI Cybersecurity Agent Bob now provides vulnerability information! 🤖🛡️EN
El Agente de IA Bob de Ciberseguridad ahora brinda información de Vulnerabilidades ! 🤖🛡️ES
#programming #coding #programación #code #webdevelopment #devs #softwaredevelopment #ai #ia #agents
The problem is that most companies with the resources to properly implement role fluidity only want to hire "unicorns." Having worked in hybrid roles at smaller companies before and after the widespread adoption of LLMs, I must say that it's a recipe for burnout. This is not only because it's difficult to assess the quality of your work, but also because, in practice, companies don't care much about documentation. In reality, you'd mostly be a software developer doing some documentation in your "free time."
Another problem with this model of a fluid software documentation team is that it assumes there are or will be software companies willing to prioritize documentation as a sector that deserves its own department. However, technical writers are often placed under the product umbrella, which isn't necessarily bad. In fact, it's much better than being placed under "marketing." Unfortunately, if role fluidity ever becomes the norm, I'm afraid it will most likely start with engineering.
https://passo.uno/docs-team-of-the-future/
#TechnicalWriting #SoftwareDocumentation #Programming #SoftwareDevelopment #AI #LLMs
If someone asked me to set up a team in charge of software documentation, I would not hire for specific roles or cookie-cut job descriptions. Professions tied to knowledge buckets are bound to shrink or disappear. Instead, I would hire people that could move freely between four quadrants, each defined by the proximity to a focus pole and its skills. The poles in this team setup would be the following: Product Vision, Knowledge Design, Engineering Depth, and Delivery Strategy.
Just published "Myth vs. Fact: why is code review so hard?"
It breaks down the misconceptions programmers have about code review, and how to adjust your approach for faster, more effective reviews.
Read on to find out why the world's best code reviewer is no match for the world's worst programmer: https://isaaclyman.com/blog/posts/code-review/
As always, my blog has no ads, paywalls, or popups. Enjoy.
A lot of teams procrastinate code review, phone it in, or get stuck in endless back-and-forth on every PR. Let’s talk about why. Myth #1 Myth: Code review is difficult because it’s boring and pull requests are too long. Fact: Code review is difficult because it duplicates the cognitive work of programming without all the intermediate steps. Engineers tend to dislike reviewing code. Instead of just accepting it as an unpleasant part of the job, we should ask why.
How I'm Productive with Claude Code
https://neilkakkar.com/productive-with-claude-code.html
#HackerNews #Productivity #ClaudeCode #TechTips #SoftwareDevelopment
Three levels of AI in software development 🧠
After my recent posts about vibecoding and devibecoding I want to zoom out a bit. I think there are three levels of using AI in software development — and they are really about risk.
🟢 Level 1: passive AI usage. Autocomplete, code review, planning, answering coding questions, writing documentation. You stay in full control, AI just saves you time. Almost zero risk, immediate productivity gains.
🟡 Level 2: vibecoding non-production code. Tests, internal tools, CI/CD scripts, prototypes. This is the sweet spot most teams underestimate. The upside is high but the blast radius is small — if a generated test is wrong it fails, if an internal tool has quirks nobody outside your team notices. Great place to learn what AI can and can't do.
🔴 Level 3: vibecoding production code. This is where it gets real. By my definition from the earlier post: vibecoded code is code nobody on your team has fully understood. Shipping that to production is a conscious risk decision.
⚡ The key insight: these aren't steps you walk through sequentially. It's a risk assessment. Level 1 and 2 are almost always worth it. Level 3 depends on your situation — a startup that needs an MVP in three months has a different equation than an enterprise with compliance requirements.
🔧 And when level 3 code needs to grow up? That's where devibecoding comes in — turning code nobody fully grasps into code your team truly owns.
Where does your team sit on this spectrum right now? 🔍
#SoftwareDevelopment #AI #Vibecoding #Devibecoding #CodeQuality #DevLife #RiskManagement
Interesting read:
What Actually Happens When You Replace Your Engineering Team with #AI | LinkedIn - https://www.linkedin.com/pulse/what-actually-happens-when-you-replace-your-team-ai-ala-stolpnik-gro6c/
This doesn’t have to be an either-or, and such a hypothetical #programming language could cater to both human readability (at the spec level) and efficiency and effectiveness for #AI driven code generation
archibaldtitan
Nube Colectiva
Miguel Afonso Caetano
Isaac Lyman
Hacker News
Marcel
N-gated Hacker News
Ankur Sinha "FranciscoD"
Timo Kissel