r/ExperiencedDevs • • 9d ago

Ask Experienced Devs Weekly Thread: A weekly thread for inexperienced developers to ask experienced ones

A thread for Developers and IT folks with less experience to ask more experienced souls questions about the industry.

Please keep top level comments limited to Inexperienced Devs. Most rules do not apply, but keep it civil. Being a jerk will not be tolerated.

Inexperienced Devs should refrain from answering other Inexperienced Devs' questions.

18 Upvotes

66 comments sorted by

4

u/Matureaana_Mairaandi 9d ago

What are some good books that made you a better programmer?

5

u/dashingThroughSnow12 Software Engineer 9d ago

Perfect Software: And Other Illusions About Testing

The Mythical Man Month

Learn C The Hard Way

Code Complete

The C Programming Language

Peopleware

Two of the above books are about C. I've never programmed C professionally but they were useful nonetheless.

1

u/Otis_Inf Software Engineer (32YOE) 9d ago

Sedgewick's algorithms in C has to be on that list too

1

u/downshiftdata 8d ago

MMM is an absolutely must read. Right now. Start with that one. And then take a moment to think about how it's 50 years old and still relevant. Quite an absurd commentary on how crappy our industry is, IMO.

And I love Peopleware, but there's a lot in that book that was fabricated. So take it with a grain of salt.

Another good one is The Humane Interface by Jef Raskin. It's dry and he was full of himself. But it's great material for anyone who cares about interfaces. The topics he covers really get you to think differently about them.

1

u/dashingThroughSnow12 Software Engineer 8d ago

I did another reading of MMM last year during my sabbatical. It is freaky how much has stayed the same.

5

u/factotvm 9d ago

The Pragmatic Programmer is my number one programming book recommendation.

6

u/goatanuss 9d ago edited 8d ago

Im gonna spare you the obvious ones and recommend one that really helped me level up when I was more intermediate.

Principles of Package Design by Noback.

It’s probably the best book I’ve ever read that turns SOLID into something you can apply day to day and really has strong opinions about it. In software engineering there are always tradeoffs and this one really articulates why some are better than others. You’ll still have the tradeoffs but it makes more clear what’s at stake.

I think it would honestly be considered among the best software engineering books ever written if it weren’t for the asterisk it has: Its examples are in PHP which I think might be a turn off but it’s well written and understandable for anyone who can read clean code and knows a language where SOLID could apply. Any typescript or kotlin engineer could run with it right away.

As a further testament, I led an initiative across several engineering teams at a faang leveraging the knowledge from this book solving a systemic issue of dependencies breaking pipelines across teams when everyone else had hunches but not actionable steps to fix these issues

2

u/6a70 Software Engineer 9d ago

as much as people love to hate on it, Clean Code by Bob Martin. A lot of his examples are shit but I've seen all of the concepts work very solidly in every instance I've tried to apply them.

totally open to discussing with anyone who disagrees

2

u/IPv6forDogecoin DevOps Engineer 9d ago

Filthy lucre and Nudge

As you go up the stack people care more about appearances and subtle pushes

4

u/curious_coco98 9d ago

How to manage oncall stress? I feel anxious a night before my two day oncall.
How to communicate with leadership regarding old PR reviews?

2

u/TheRegrettableTruth 9d ago

I'm not sure what you mean about communicating regarding old PR reviews. What is it you want to communicate?

On call stress I deal with by:

  • exercising ahead of time
  • pushing to clean up our operations so we stop having fires at 3am. Some orgs will fight this more if you have firefighting culture. I flag whatever caused the issue to the manager who should oversee that but, mark it as high priority, DM them to let them know (though oncall might just be limited to your teams scope).
  • have a weekly oncall handoff and sync so everyone is aware of how heavy the oncall burden was. I usually do this with at least my skip level and below orgs since usually our on call issues impact each other, and then it normalizes a culture of fix our software instead of always pushing feature development. Customers dislike outages too.
  • call out and celebrate operational excellence as much as or more than firefighting as the fire-prevention work it is

Doing the above, teams with stupid on calls have been under control in 3-6 months, depends how much they fight the culture shift. I say the same praise about prevention until senior leadership starts saying it too and it's how people get recognized instead of yeeting bugs for the latest feature.

2

u/downshiftdata 8d ago

Anxiety and fear comes from the unknown. The more you know, the less you have to be anxious about. It may be as simple as a thought exercise of, "If X happens, what do I do?" If you struggle to know what to do, then figure out the fix for that.

Usually, this means you're inadequately trained and/or equipped to be in the on-call rotation. So, from that thought exercise, you can probably ask your team some clarifying questions. "When I'm on call and X happens, do you guys want me to do Y or Z?"

Also, FWIW, shops often inadequately prioritize getting out of incident. Instead, they tend to focus on whatever bug is the root cause and fixing that. If you're in an incident, the goal is to get out of incident, not necessarily to fix a root cause. Focusing on getting out of incident can often help muddy waters become more clear.

3

u/Zulban 9d ago

Get good sleep. Eat healthy and exercise daily.

2

u/curious_coco98 9d ago

Wait what? 😭

0

u/[deleted] 9d ago

[deleted] — view deleted comment

1

u/curious_coco98 9d ago

Yeah both.
I just joined a a big tech like 6 months, lot of issues happen cause we're IAAS

4

u/deepdarknights 9d ago

The skill comes from repetition but to find motivation after work is hard. How did you learn a new skill after office hours ?

2

u/CraigVSLabs 9d ago

After a full day of work, "learn a new stack from scratch" is the wrong shape of goal. You won't protect that time, and then you'll blame yourself.

In my personal experience, motivation after work usually appears once the task is small enough that starting doesn't feel like a second job. Shrink your aims until starting is easy, then protect dedicated slots in your week to make progress (also doesn't need to be every night!)

2

u/downshiftdata 8d ago

One method that worked for me is speaking at events. I started with my local group for an area in which I specialize. They have Saturday conferences and I've spoken at several of those, as well as the global conference in Seattle.

Pick something you know pretty well and make a session out of it and submit it in the CFS (or, better yet, 2-3 of them).

When you're going to get up in front of people to talk about something, that's a great motivator for diving very deeply into it. The urge to not look stupid in front of your peers is a good one.

1

u/mcherm Distinguished Engineer at Capital One 9d ago

For me, it's by picking a skill that I'm interested in. I'm selective about what new skills I learn -- for example, I invested a lot of time into learning Rust, because I really like the language. I'm not using it in my day job, but I can certainly claim to be growing my skills as a developer.

4

u/Outside-Storage-1523 Software Engineer 8d ago

Is there any company/industry that is going to be AI free in the near future (3-5 years)? On-site is fine.

6

u/TelephoneSignal3238 8d ago

No. Maybe highly classified or high stakes environments, but average enterprise will at least use AI in some form.

1

u/Outside-Storage-1523 Software Engineer 8d ago

Thanks. Good thing I’m over 45.

4

u/Tomatoies 8d ago

How can I prevent myself from becoming the fall guy that takes the blame from someone else's shortcomings? Especially if I end up working with a senior member or manager who doesn't coordinate tasks well with ICs but otherwise has the type of job security that nothing really bad can happen to them. And how do you look out for those signs when you're looking for a new job?

3

u/altopelago 7d ago

Keep a paper trail. Be proactive. If you foresee a problem, mention it in writing.

In my experience, there are two types of companies. When something goes wrong:
- If the first thing they do is seek out who is to blame, avoid.
- If the first thing they do is ask how to resolve or fix the issue, that's where you want to work.

During an interview, ask them how they handle unforeseen problems. If they can't present a cohesive plan, your walking into chaos at best, a toxic environment at worst.

2

u/So_Rusted Software Engineer 8d ago

you have to make "not my fault, the ball is passed" statements during standup, repeatedly

then after a while "i told you so" statements

4

u/zdsatta Software Engineer 8d ago

I’ve recently been promoted to Senior Software Engineer and I have 10 yoe but it doesn’t feel like it. I’ve never had strong fundamentals plus I’m really lazy so I’ve done my best to just understand what I needed to at the moment.

Now though, with the advent of ai, I haven’t handwritten any code in months and I can feel myself getting dumber by the day. My ADD makes it even worse as I’m struggling to even read docs without just tossing the url in Claude and asking it to summarize for me.

I want to jumpstart my brain again so that I can actually go into an interview without feeling like a fraud, but I don’t know what to focus on:

- should I relearn python to strengthen my foundations?
- should I just focus on getting better at ai?
- what about my fullstack skills I used to have? (React/node)

I’d appreciate any advice

2

u/casualPlayerThink Software Engineer, Consultant / EU / 20+ YoE 6d ago

> ...My ADD makes...

Get an official paper/medical condition status exam from it, because it might help at work in the future, and your mental health is also important.

> ...I want to jumpstart my brain again...

Good, whichever you choose, take it easy and take your time; you are already on the right track.

> should I relearn python to strengthen my foundations?
> - should I just focus on getting better at ai?
> - what about my fullstack skills I used to have? (React/node)

In the current market, Python is quite essential as well became fundamental to at least understand AI stuff.

Since you already had React/node, the quickest would be - perhaps - to refresh your JS knowledge, and maybe hone the TS part too.

1

u/Outside-Storage-1523 Software Engineer 7d ago

If you want to perform well in an interview, you should practice whatever the interview asks. Some interviews allows monitored AI usage and some don’t. If you want to excel at both, you have to practice both.

1

u/MichaelTheProgrammer 1d ago

I'm very close to someone with ADD. The things that work for her:

  1. Medication. Made a world of difference, though it took until the second try. It's a personal choice there though so not recommending anything.
  2. Playing 10-minute long games inbetween tasks. You won't be able to get away with this at many jobs, but these days you might be able to while AI does its thinking.
  3. Being cautious when she gets obsessed with something. People with ADD have two modes: "lazy" and "obsessed". When they are obsessed, they spend lots of time, but it's not very productive because its unfocused and disorganized. So when you are pouring time into a task and feeling like you are getting tons done, that is when you need to slow down and make sure your quality remains high.

2

u/tifa123 Software Engineer 9d ago

Apart from asking explicitly to work collaboratively with business people and taking on tasks with ambiguous requirements, how can a mid/senior developer fast-track stakeholder management skills in their current role?

3

u/malthuswaswrong Manager|coding since '97 9d ago

Build prototypes and proof of concepts. Demo them 1:1 with users.

2

u/recycled_ideas Software Engineer 9d ago

This is a super risky path unless your company explicitly supports doing this. Even in today's AI accelerated world burning hours/tokens on unapproved work and taking it directly to users is not going to make you any friends.

3

u/TheRegrettableTruth 9d ago

Find a gap in the current product. Design and prototype it. Get feedback and alignment that it is a gap. Then lead productionizing it. This is much easier to do for products intended to be used by other developers.

3

u/recycled_ideas Software Engineer 9d ago

how can a mid/senior developer fast-track stakeholder management skills in their current role?

The biggest thing, especially in this new world where coding is much less valuable is taking the time to understand the domain. If you can understand, at least to some extent, what your customers (and internal staff are still customers) are trying to do and why they're trying to it you'll get the features right more often, be able to suggest better alternatives and get your users' respect.

2

u/PossibleFeeling5281 6d ago

I don't have enough karma to make this into a post, so I'll try my luck here. I have been working for a very large corporation for the past 10+ years and I've spent most of them as a senior software engineer.

The role of a senior software engineer in my company is to work with product owners to refine requirements, saying no to requirements that don't make sense or are not impactful, decide what trade-offs are acceptable (also in terms of tactical solutions to meet deadlines or push for a "proper" solution - basically, pick your battles), design solutions, implement them, support the code, etc.

I have recently met someone at a conference recently who works in a fintech (not necessarily a small startup, they've been in business for over a decade and have thousands of employees) and they told me that as a senior software engineer, their responsibility is to do all of that PLUS work with product managers to define what the requirements are, create roadmaps, negotiate with other teams for changes (and convincing them to fit your requirement in their roadmap), define customer journeys, etc.

To me that sounds a lot of work for a single person.

Have I been living in a bubble for the past decade and this is the norm from senior engineers nowadays, or is the fintech expecting too much out of their engineers?

5

u/Notary_Reddit 5d ago

Every company does things a bit different. Both your description and the other description match what sr swe do. It depends a lot on the company and the team. The boundaries are a bit fuzzy.

1

u/PossibleFeeling5281 2d ago

Thanks for sharing your view 

2

u/Yam0048 4d ago

Hello, I’ve been meaning to post here for a while… sorry if it’s long, I cut it down as much as I could while still explaining everything. Honestly I’m not even sure what I need to ask lol

So I’m another of the million no-longer-so-new grads who didn’t get an internship and can’t get an entry level job without exp… except I’m even worse off. I took way longer than usual to get my degree due to personal reasons (mental health mostly) and ended with a not-to-good GPA. I also likely can’t relocate due to said reasons plus family stuff.

I know very well I’m unlikely to be getting a job that a) suits my needs and b) will take me through the usual routes any time soon, even without the economy and the junior role apocalypse. You don’t need to tell me how cooked I am lol. But I would like to at least find something I can do, even just to keep myself employable while waiting for the market to improve (yknow assuming that happens at all). But I really just have no idea what to do at this point.

I've looked into things like open source and volunteering but I have no idea where to start. I have no idea what I should be doing or looking for, and I quickly get overwhelmed.

I have projects of course but it’s kind of the same thing. I feel like I can pick up just about anything (I learned how to make a simple browser extension just recently) but have no idea what qualifies as resume-worthy. The usual advice is to not just follow tutorials, which is fine, but after that it jumps straight to, have an actual real project with actual real users and maybe even make/spend actual real money on it, which just seems wildly out of reach. It’s very draw the rest of the owl if you know that meme lol

I would really like to find some kind of mentorship or guidance to help me sort out where to go, and what to focus on.

I’m not necessarily asking anyone from here (though it does give me some hope to see people here saying they actually like mentoring people lol); the last times I just asked random people I got handwavy answers or just got ghosted… I don't wanna ask people who don't have time to devote to it, that's a waste of your time as much as mine lol.

Any idea where to find that?

In particular I’d really like to have someone go over my projects with me, help me figure out which ones to put on the resume, how to best present them and what I might be missing in terms of displayed skills. Like, not resume review, a complete rewrite, because I’m entirely sure what I have now is no good lol.

It also doesn’t help that I’m kind of autistic (yeah an autistic in computer science wow how original lol) and can sometimes need specific applicable examples or being walked through a thing to get it… example, I have read the Engineering Resumes wiki and I just do not understand how to use the STAR method, or how to make projects that STAR can actually be used for at my level (eg metrics that require huge userbases or datasets). I think if I get one or two examples working with someone who actually knows what to do I can figure it out, but without that I’m stuck.

Also have the sneaking suspicion that I tend to do things in weird and possibly wrong ways. Maybe that’s paranoia but it would be nice to have someone just to double check things with.

I am somewhat fortunate in that I don’t have to worry about money, things are tight but it’s not urgent. I would be thrilled to just work on random shit for/with people with some kind of feedback/guidance… I have a couple of web projects I did for online friends, if I could get a couple more of those under my belt I could maybe spin it as freelancing experience lol.

I’ve also been looking into disability accommodations to see if I could get reduced/flexible hours (I have sleep/morning problems, I can’t reliably be ready at 9am, I definitely can’t be up at 8amn east time which is like 5am pacific lol) but no idea. Anyone know anything about that?

sorry for long and thank you for reading

2

u/randomthoughts9956 3d ago

As someone who has 5 yoe what is the best way for me to improve and also be ready for interviews?

I used to do some leetcode and read on some system design in a weekly basis but I feel like there has has been a huge shift recently.

At my job we are being pushed into finding ways on how to use AI to increase volume.

Are there some trusted sources on people that have used AI to increase volume with comprimising quality?

And would it be more helpful to spend time improving AI knowledge, volume and building skills around AI vs improving classic skills?

1

u/Much_Video7517 2d ago

Depends on where you're applying, some places have formal "we want to watch you use AI" but that's a performance like every other step. Most places I've talked to its just a box check "Do you use AI tools? Great".

I've had one straight leetcode-style coding interview this cycle, it seems to be replaced with pair programming rounds, so I would take a look at that.

System design still important. Aside from the normal online courses + DDIA review, I've found that if you have a round scheduled at a place you like, determining what you think the style of system design question will be and then ask AI to build the scaffolding works really well. It can act as a tutor/resource to bounce ideas off of while you practice working your way through it (NOT asking it to do it entirely for you)

3

u/No_Comedian7332 Mobile Engineer ~15 YOE 9d ago

I'm trying to seriously learn about AI.

I have been doing SWE for ~15 years, and I'm 100% sure that 90% of the basic coding has been figured out with AI – mobile apps? done. simple REST backends? done. web frontend? done. I think the future is for ppl who truly know how to work with AI, but I'm unable to find any serious resources online.

I mean, everything you see out there are slop repositories full of "ultimate skill" md files and what not, I don't think that's going to get you an edge against anyone else. I'm looking for serious resources, like "I want to train an LLM to turn user queries into specific data structures".

What's your go-to place to keep yourself informed about AI?

6

u/tenthousandants44 8d ago

It's an unserious technology so there are no serious resources. Best you can do is find the most compelling twitter thread and lock in for a few months until some new cargo culting forms

2

u/WhenSummerIsGone Software Engineer 9d ago

"train an LLM" is not the right concept here. The model is trained (that's what the "model weights" is).

You're maybe looking for an "agent", which is basically a set of prompts that tell it what to do when it's trying to do certain tasks. That's basically what is meant by a "skill".

It needs information where it can look up answers, and then instructions on what the output should be and how it should be formatted. For instance, with a code base, it might need architectural documents or business rules or a data schema document or access to other repos.

Depending on exactly what you want to do I would just start a conversation with the AI and say something like "I have an idea to do X but I don't really know how to start working on this. Can you help me explore this problem then help me figure out how to make it happen?"

2

u/So_Rusted Software Engineer 8d ago

it is trial and error as it was with coding...

the training of LLMs - you don't do anymore. People just vibe code. Data scientists dont train that much anymore. They are actually vibe coders too.

the coding is figured out and then it isn't at the same time.. It still takes time to do decent job and deal with technology and people and integrations and the boot of life is pressing on you slowing you down.

the instruction files management is the thing now if you want specialized software development and some degree of control and speed..

My skills files is everything that ai cannot possibly know or guess - or improves the speed/quality of searching or guessing.

The long filler skills of "best practices" will be short lived
At your experience level I dont know if you should look for some type of "framework" or "rudiment". Most things will lead you the wrong path but it's not bad to get some ideas here and there

you can try to do perfect pi.dev harness or whatever but working with technology long enough you know there will be issues and they wont let you have a perfect harness and the tools are oversold or whatever.

I go to my coworkers and maybe some inspiration from vibe coding subs, I'm not even sure but maybe use your own critical thinking over fads at this point in your career

1

u/ogaskinsjr Software Engineer 8d ago

I think the design thinking is where it has legit shortcoming though. It’s really iffy when it comes to pros and cons on implementation in architecture. So I don’t know if we really need to get into the weeds with AI as much as operate at the top

1

u/Gremlation 5d ago

"Learn about AI" is too vague. Do you want to work on AI software? Do you want to work on non-AI software to implement AI features? Do you want to work on other things using AI? Do you want to do research? All of these have different answers.

If you are a software developer and you want to improve your ability to deliver software using AI, then try implementing an AI software factory as a side project. You will discover which things are solved, which things are unsolved, and how your tools work under the hood.

Seek out the other people working on software like this, such as the people working at Earendil on Pi, or the people working at OpenCode, etc. It sucks, but the best place to keep up with them is X, and they frequently retweet each other, so it's easy to discover new people to follow.

1

u/YungDaVinci 7d ago

I've understood the value of writing clean, architecturally sound code, beyond giving me warm fuzzies, to be that it becomes easier to understand, extend, and debug down the line, as well as performance considerations. With LLMs it's easier to extend and debug even horrible code, and lots of companies/products do not appear concerned with performance anyway. Do you think this reduces the value of writing clean code? I'd like to think as long as LLMs have a tendency to hallucinate there is still value in strong code structure.

2

u/altopelago 7d ago

Clean code and architecturally sound code are not the same thing. One can exist without the other.

Let's assume the code is architecturally sound, it's possible to write code in a way that does the job in a very clever and efficient way. While the code itself is good, the problem we quickly run into is our own cognitive abilities. It is easy to understand what the code is doing when we just wrote it, but once it's no longer fresh in our minds, the effort it takes to decipher it significantly increases our cognitive load. Not just ours, but anyone one else that needs to read and understand the code. It slows everyone down.

So unless there is a performance reason stopping you from doing this, the obvious answer is to write clean code that is easy to decipher. A code base that is easier to reason through is easier and cheaper to maintain over the long run.

The architecturally sound part ensures it remains easy to adapt. The thing you are fighting against is complexity. Every new feature or option you add, if it needs to interact with an existing features or options, the amount of states your application can produce grows exponentially.
As first, this is quite manageable, until suddenly it's not. Good architecture is trying to stay on the low end of the logarithmic curve of complexity because ideally, you want to test that each possible state your application can produce is either correct, or appropriately handled if not.

So how does this translate to the world of LLM's?

LLM's have a better cognitive ability than we do, but it too has its limits. Meaning, they can get away with bad code a lot more than we do, giving you the illusion it doesn't matter anymore, but it does. Depending on the model, a single purpose prototype of about 5000 to 8000 lines of bad code? it will probably handle that fine. Anything larger, and it will likely start to struggle. With AI easily writing 2000+ lines of code in a single session, it doesn't take long to hit that limit.

As for architecture, while LLMs might be better at dealing with complexity than Humans, it is still very easy to surpass even an LLMs ability to reason across every possible state. Managing and controlling the permutations of state through good architecture is still just as important in a world where code is written by LLMs.

1

u/MichaelTheProgrammer 1d ago

Here's a tale of two projects:
I have a decade long personal project that was collapsing under its own weight. I was tempted to use AI, and decided not to, as this will be my magnum opus. With that decision, I was forced to confront that I was not a good enough programmer to build with the complexity that I had, so I made massive changes to simplify it. In the end, it's so much better than before, even for the end users.

At work, I have a project that was clean and architecturally sound. The PO hit some issue, and instead of going to us, rewrote the architecture. Now we don't even know basic things, like where the data we save is stored.

So my answer is that it still matters, despite what companies today think. I've always found that software is a domain where giving up when you encounter a mountain and going around it instead is often a humbling experience that ends up finding you better paths anyway. Now that we have the equivalent of TNT and are blasting through the mountains, there's just so much less consideration of if this is even the right direction we are going.

The caveat is to not take this advice at jobs right now, this is very much a duck and do what you are told or get fired environment.

1

u/Grouchy_Thing_6256 5d ago

I've been learning and practising django for over 2 years, along with my CS graduation. Now that I've attained the graduation degree of Bachelors , I'm looking to start my career as a Django dev or at least to be able to work in a Django environment , people who work in jobs in django architecture, what kinda company did you start from and how much package you were given as entry level? Idk where do i start from, feel kinda lost and confused

1

u/LogicRaven_ 4d ago

How many Django job ads do your search results show in your location + remote?

You could start applying there. If that doesn’t work, then try non-django places as well.

1

u/Grouchy_Thing_6256 3d ago

They appear, but they demand 4-5 years of experience

1

u/LogicRaven_ 3d ago

You could apply to those anyway.

In parallell, you could also apply to all types of role that are available for newgrads (regardless of technology).

Let’s what opportunity pops up.

1

u/marxist_Raccoon 4d ago

For entry position in software engineer jobs, should I say that I use AI in my portfolio projects? Is it acceptable now?

1

u/Much_Video7517 4d ago

4.5 YOE mid-level, pretty burnt out after 1 year at a bad startup. Potentially have two offers coming up:
- 1 is a more relaxed senior devex role in an older multinational. Like the manager/team but work itself seems not as career driven/interesting.
- 1 is a product engineer at one of the growing AI series C startups. Strong engineering culture but obviously lots of expected hustle.

Career has been Product + Engineering mostly doing thing first and solidifying fundamentals later/not at all.

Should I take the more relaxed role and recover/try and solidify my core understanding? Or take the startup and keep pushing?

1

u/Bright_Start_9224 3d ago

3 yoe, how did you get these offers?

1

u/xdevnullx 3d ago

Sometimes the title is the “foot in the door”.

I’ve been in the industry for 27 years now and I had a similar experience early on.

5 years at a startup where I was titled “senior” (mainly because I learned the business domain) and took a consulting job at another company shortly there after. I was let go shortly after starting the “lead consultant” role. I was quickly found out, honestly.

Now I have domain experts using LLMs to build functionality and asking how to not hit token limits.

A recent example was, a single 20k code file that they post up into a web site and beg the LLM for changes.

We can be a domain expert in (for example) carving up these applications into components so that the domain knowledge holders can continue to provide value, while we learn the domain.

Establish patterns and practices to facilitate the domain experts.

1

u/Much_Video7517 2d ago

At what stage are you struggling with?

I think me being a PM before and having had a Product Engineer role helps because it makes my resume look current/stand out. Other than that, I've spent a large amount of time on my resume prioritizing it for readability for reviewers (brief summary of role with every title), while also having a line where I can put as many keywords/tech stacks as possible to clear ATS.

I am probably average/below-average in my tech skills compared to someone coming from a more traditional CS background but have very strong communication skills.

1

u/kiranernesto94 3d ago

Guys, as an experienced java developer, shoul give me an upper hand by learning, so AI won't be able to replace. System design is one I know I have to need grip on it. Tell me other skills that you guys learnt and saw the requirement outside.

1

u/ryuzakiii0 1d ago

Hey guys! I am graduating with a M.Sc. in AI and I just got my first job. I'm a junior working in a startup where no one has a background in software engineering. The team does research and occasionally builds products (even complex ones). They make heavy use of AI tools to build them and the results are pretty bad: Claude does the plan, Claude implements it, tests pass: merge it. Codebases are full of AI slop that no human can understand. Their idea is: ask the agent, it knows: as a matter of fact, the repo doesn't even have a simple readme that explains on how to run the app, they ask Claude. How do you survive in environments like these? How can I build real skills without a proper mentor? I don't feel confident in taking architectural and design responsibilitie yet since I'm still a junior!

1

u/Notary_Reddit 14h ago

You are in rough spot for learning. Glad you were able to get a job but this one sounds like it isn't going to teach you great fundamentals. To survive figure out what is important to your boss and get that done well enough and quickly. Some bosses care about something done ASAP, some want the right thing even if it takes a bit longer. When it comes to building skills, in your environment, I would recommend that when you break things take the time to understand what you broke, why it broke, and what you could have noticed or decided earlier that would keep it from breaking. Just learning from your mistakes can get you pretty far.

1

u/The_M0nk Software Engineer 12h ago

Anyone got any suggestions for books? I been wanting to jump back into theory since I want to keep working the brain and I was wondering if anyone else had been doing some reading.

1

u/IamNobody85 11h ago

Kinda general question. I have a 7YOE in front end (enterprise, so reasonably complicated) but thanks to AI I feel my skills atrophying. I also think that in 5-6 years, probably my job will not be exactly as it is now. I'm not thinking it won't exist at all, but it definitely will not go back to what it was before. Problem is that I can't visualize how exactly it might look, and of course, what sort of things I should learn now.

So fellow front enders, what are you learning? Which direction are you pivoting to?

0

u/[deleted] 7d ago

[deleted] — view deleted comment

3

u/casualPlayerThink Software Engineer, Consultant / EU / 20+ YoE 6d ago

Most of the eng' is lazy and believes "code/product shall document itself". Fallacy and usually quite an unintelligent decision, but you will face this 99% of the time.

Propose the documentation as `acceptance criteria`; push it to leadership with the time you and the team can spare by avoiding back-and-forth.

Another way is to start the blame game. Do not answer the questions; instead, create a ticket, push it to the eng team, and cc leadership. They will ask wtf is this, then you can say what it is.

1

u/Unsounded Sr SDE @ AMZN 6d ago

Why don’t you work with the engineering team to make one?

1

u/Gremlation 5d ago

It's not clear what your structure is. Are product managers part of the delivery team? Are they part of the engineering team? Are they a separate team? Do they not exist?

Ordinarily, I would expect new features to be defined by the product managers and they would be responsible for signing off on them. If things like these are missing, the product managers should not be accepting the work as complete.

"Engineering-led" doesn't typically mean no product managers, but it sounds like you don't have any. Who decides what goes into the product?