הכל התחיל מפוסט תמים שהפך לוויראלי בקבוצת הפייסבוק "צרות בהייטק". עכשיו, הספר שאני כותב נמצא בשלבי הסיום ואני זקוק לתמיכתכם כדי להוציא אותו לאור! 🙏
אני נרגש לשתף אתכם בפרויקט שאני עובד עליו כבר תקופה ארוכה: 'המדריך להייטקיסט המתחיל'!
Tactical vs Strategic Programming, and why I'm nervous for juniors:
Good programming involves a mix of tactical and strategic decision-making:
- Tactical: on the ground, short-term. The soldier doing the fighting.
- Strategic: high-view, long-term. The general planning the war.
You need to be a tactician to write good code. To choose the right syntax. To figure out the file structure. To figure out how best to test your changes.
But you need to be a strategist to build code that lasts. To design the architecture. To automate away problems. To think beyond today.
Agents have eaten the tactical part of programming. When you can pay below minimum wage for code, there's no point going into the trenches yourself.
But AI cannot code strategically. Agents need someone at the top of the pyramid to tell them what to do. They need oversight.
So, a developer's day-to-day job has become 100% strategy. Long-term thinking, all the time. (maybe this is why I'm so tired all the time now)
If you identify as a tactical programmer - a code monkey - then you are out of luck. The job has changed.
Personally, I like it. I always preferred thinking strategically about code. If you asked me what my job was about, I'd say 'building apps', not 'writing code'.
But what makes me nervous is that we've pulled down the only bridge that brought juniors into the industry.
We used to train juniors like this:
1. Give them only tactical tasks
2. Let them build up their strategic experience slowly
Eventually, they are a good enough strategist that they are no longer a junior.
But what happens when all tactical code is written by AI? What is the point of a junior?
We obviously need juniors. We need new lifeblood coming into the industry. We need to leave paths open for extraordinary hires to enrich our companies.
But how do we train them? How do you train strategic thinking?
These are the questions I'm thinking about. I'd love to know your thoughts.
We’re introducing Dynamic Workers, which allow you to execute AI-generated code in secure, lightweight isolates. This approach is 100 times faster than traditional containers. https://t.co/c36Vkb7I0R
We checked our data and firewall logs and see no such thing. In fact, we see zero failed requests. That gentleman has since deleted their LinkedIn post. https://t.co/m7Fk0YI4U5 is up and looks like a really nice website.
Many times people report they've succeeded in attacking a host because they get blocked or throttled by our DDoS mitigations 😂 Possibly what was in play here…
Everything we're doing to make codebases "agent-ready" (better docs, less dead code, smaller surfaces) engineers always needed too. Agents just have zero tolerance for the entropy humans learned to work around. They can't "just know" a file is outdated or a code path is dead. They take your codebase at face value, which means it finally has to be worth taking at face value.