ETA: summary…

Author describes how agentic coding tools have disincentivized the developer training and mentorship pipeline that the software industry has implicitly relied on to produce seasoned developers, predicting that once the shortage is fully realized it could take years to reverse.

The solution proposed is for managers and senior developers to get ahead of this shortage by foregoing the immediate yet shortlived productivity maximization offered by the agent-multiplied-senior structure in favor of longterm sustainability by deliberately facilitating experience fan-out to juniors.

The methodology proposed is based on a successful nuclear engineering apprenticeship program carried out on active service naval submarines.

cross-posted from: https://programming.dev/post/51247328

I use speckit, and while I like the spec/clarify/plan/task/analyze/implement loop (although it can get a bit overwhelming at times), I don't like that I have to start with writing a spec and implement it to begin with. I am looking for a more of a design phase before the spec phase, where I can talk about the overall application architecture, and then start writing specs for implementing pieces of it.

For instance, let's say I want to build a github repo provisioner that 1. creates repos with desired setup, and 2. bulk edit repos with secret updates, yaml updates, etc. I don't want to build both the features at the beginning. I want to first build only the create portion, and then do the bulk edit feature later on. With speckit, I can do this by only telling it to create the spec for the build portion, but later if I want to build the bulk edit portion, the whole application might need to be changed in important places, because it wasn't a 'planned' feature when it was first designed. I want instead to have a design phase where I describe and maintain a doc with the whole application, and when I start the spec for the create portion, the agent can understand that this create portion is only part of a bigger application and can design/implement the create portion accordingly.

Have you come across a situation like this? how do you handle your big applications? Please advise.

cross-posted from: https://programming.dev/post/49896390

I have been applying via linkedin, company portal which show up on google search but somehow nothing is working out, cold dm, emails almost all eventually ending in radio silence. Not asking for some shortcut just that it all isn't making sense.

cross-posted from: https://programming.dev/post/49576261

I just came across televison the fuzzy finder tui last night on trending github projects, and it looks pretty useful

alexpasmantier.github.io/television/

cross-posted from: https://lemmy.ml/post/45059519

Ever seen our AOSP based apps (Phone,Messages,Gallery...) & thought I could make a difference to bring them up?

We're seeking a senior Android engineer to take ownership of the default app suite:

https://grapheneos.org/hiring#android-apps-software-engineer

Code standard is high, vibe coders need not apply.

Spot-on summary of the state of AI affairs by Dax Raad, who ironically is a co-founder of opencode.ai

via shitter

everyone's talking about their teams like they were at the peak of efficiency and bottlenecked by ability to produce code

here's what things actually look like

• your org rarely has good ideas. ideas being expensive to implement was actually helping
• majority of workers have no reason to be super motivated, they want to do their 9-5 and get back to their life
• they're not using AI to be 10x more effective they're using it to churn out their tasks with less energy spend
• the 2 people on your team that actually tried are now flattened by the slop code everyone is producing, they will quit soon
• even when you produce work faster you're still bottlenecked by bureaucracy and the dozen other realities of shipping something real
• your CFO is like what do you mean each engineer now costs $2000 extra per month in LLM bills

Curious where others might stand.

My day to day “coding” is reviewing, revising and running plans against LLM/code-assistant tools. I juggle around 2-3 sessions of this on various features or tasks at a time.

Not to poke at React or any of the other popular frameworks, I'm sure they're suitable for Cybersecurity projects. They surely go through things like reviews and audits.

I'm asking from the perspective that web components are native to the browser and thus reducing what I think is called supply chain attacks (like if "npm install" introduces something it shouldn't).

Maybe the frameworks don't matter and depends on the browser/os/device it's run on?

Context: I have a p2p messaging app created with ReactJS and a separate project for a UI framework based on Lit. Both these projects can be a whole separate discussion. I was wondering if there could be any advantages to refactoring (or starting from scratch) the messaging-app to be based on the webcomponent ui framework.

Same question on r/ExperiencedDevs with comments here. I have an answer there, but posting here in-case anything is being overlooked.

https://positive-intentions.com/blog/decentralised-architecture

Creating webapps is easy enough, but in my app, im kinda going against the "best-practices".

For example, im using browser-based cryptography exclusively. while it can be easy advice to suggest to consider using a server to generate keys, i want to contrast it against a webapp that would be sandboxed within the browser.

I'd appriciate if you would be interested to share your thoughts on the approach. I'm aiming for this project to be the foundation towards the most frickin' secure messaging app in the universe. It might be too ambitious, but I'd like to set the bar high.

Permanently Deleted

A few months ago, I posted to complain about the build system at my job. It wasn't my only complaint about that job, but it was the easiest to put into words. There were other factors (unfulfilling work, unpleasant work culture, a manager with whom every interaction felt "fake") that led to me quitting in early January.

My original goal was to take several months off and focus on longtime hobbies as well as training/certifying to get a DevOps job. However, day 1 of America's current Republican administration made clear that my family is no longer welcome here, and we'd need a strong financial footing to move. I put my plans on hold and got back into the job market.

I had changed jobs during COVID and the post-pandemic market cooldown, so I thought I knew what to expect (folks who looked for jobs in 2000 & 2008 are allowed to laugh). I was not ready for how quickly job postings reacted to economic troubles this time.

In the end, after dealing with "AI" interviewers, mid-interview ghosting, rejections, and more, I got the kind of job I wanted by knowing someone. Specifically, a former coworker vouched for me to a friend of theirs who was hiring.

I see a lot of stuff online that equates networking with nepotism. It seems like the distinction is lost on some people: It's way easier to get a job when the hiring manager trusts that you know your shit. There's a lot of AI slop out there now, and it seems like human recruiters are less involved and more skittish than ever. Your advantage is your human connection to another person.

Don't burn your bridges with other jobs/people unnecessarily. The former coworker who recommended me isn't even a friend of mine, just somebody who I worked well with. I only learned that their friend was hiring after we met for lunch to discuss their experience working in DevOps. It's not beneath you to reap the benefits of positive social interaction.

Also: Those who remember my last post may find it funny that my new team is responsible for the build system.

hope this question doesn't sound too vague.

I hate every interaction with our tooling. I loathe our older-than-dirt source control system. I hate our 4+ hour build times from scratch. I can't stand our "never plan shit" development process. I despise waiting 3+ months to see my changes in prod. I'm baffled by our RTFM onboarding process when the "manual" is some document written at project launch that's never been updated in the 10 years since.

My current task is simple, took a short time to write my code. But I've had so much trouble with tooling that the process of submitting a code review has stretched over a week. At this point, I know what I can do next to fix it, and it would take maybe 20 mins to do. However, I can't bring myself to even do that.

As cruel as it feels to say, my manager is like some NPC. I am on two teams, one of which I meet with every day who doesn't understand the work I'm doing for team #2. Team #2 meanwhile consists mostly of people I've never met, not even on video calls.

The company is huge and I don't feel like I can make any impact. My plan at this point is to try and hold out for my 1 year shares to vest and then bounce. Take 6 months to brush up on dev-ops skills and then look for a new line of work.

hackernews Comments

Hello everyone,

I am a developer with 3+ years of experience with full stack technology so mostly .Net and React along with some side projects in other languages. I wanted to ask if anyone has had any luck moving from high-end projects, to lower end projects(C++). I've become extremely interested in lower level projects like, embedded programming, firmware, drivers, compatibility layers but I don't have any professional experience in those fields.

I understand that projects like these are high priority so they are less interested in taking a risk for a Dev without professional experience in C, C++, or Rust, even if they liked the candidate. I just wanted some insight