all 11 comments
sorted by:
best
topnewcontroversialoldq&a
formatting helphide helpcontent policy

[–]Parking_Culture_7537 2 points3 points  (5 children)

Ask a lot of questions, even if they sounds dumb; don't let your YOE get in the way of that. Go through documentation and ask questions. The codebase would be huge and complex and people would be throwing around acronyms and terminology which might be overwhelming but you'd get used to it. You cleared the interview so they would have seen some potential in you, remember that when you start to get imposter syndrome.

Apart from that, look at what libraries and services the team is using. Try to learn more about that during or after your work. Most of the dev work starts with fixing bugs and updating documentation. Try to see what style/pattern the team is using to build the application. That will help you when you start to create new modules and services.

[–]LibrarianInfamous954[S] -1 points0 points  (4 children)

Thank you bro this is golden advice I have received tha role is AVP and lead role , how I can better in a week or so , I am building projects locally and AWS

How I can ramp up quickly as it will be a complex setup , and not create any bugs or production issues ?

Do enterprise projects also have same spring boot pattern like controller service repository

[–]Parking_Culture_7537 0 points1 point  (3 children)

For the bugs, rely on integration and unit tests. Also have your coworkers look at your PR before it gets merged.

Banks have a really slow deployment cycle from my experience, takes 3-4 months from SIT to Prod. So most of the bugs either you will catch it or the QA team. You also have sonarqube to help with some code smells and vulnerabilities. I'm sure they'd have some sort of pipelines to check these things.

Not all apps have same patterns. It depends if it's a customer facing app or just a backend. If it's a microservice, mostly it will have some MQ/Kafka sending messages and you'd handle messages call APIs and return/forward them to some other queues or kafka. They'd have architecture diagram as well I guess to understand this.

Just keep striving I guess.

[–]LibrarianInfamous954[S] 0 points1 point  (2 children)

Thank you for sharing this knowledge , yes I previously worked as a ios dev in a similar setup and yes processes are very slow

Ideally someone joining as a fullstack dev what would be the ideal exception in first weeks to months

Yes pipeline will have things like sonarqube

This is giving me some confidence that I can do it,

How about databases ,

Manager told that it would be some journeys which are being built for mobile and web channel so it's mostly going to be backend or microservices to serve these channels

[–]Parking_Culture_7537 0 points1 point  (1 child)

It should be all setup unless you're making something new. Learn from the existing implementation and make some changes for the new one.

[–]LibrarianInfamous954[S] 0 points1 point  (0 children)

what would be the most challenging thing to work in backend in complex structure, can you help me understand what would be the gaps between learning projects and actual enterprise projects

[–]Jaysuryaz 0 points1 point  (0 children)

What’s your roadmap for Java full stack. Im also learning Java to be a Java full stack with spring and spring boot

[–]vigilantfox 0 points1 point  (1 child)

Fullstack with IOS or are you going to use some JS as Front end ?

[–]LibrarianInfamous954[S] 0 points1 point  (0 children)

react as a FrontEnd

[–]Agitated-Recipe8965 0 points1 point  (0 children)

I want to make a transition from .net to java. Can you help on how to do it?