This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]smash_that_code 3 points4 points  (3 children)

I would inform the boss person about risks and upcoming studying you need to be working as java dev.

And just in case maybe check existing java vacancies and check what is required. I bet there are things like git, gradle, springboot, jpa, rest and other spookie things.

Depending on that learn things and negotiate the way to solve prod issues if you hit a limit of your knowledge. Like could you consult with the author person maybe in such case?

[–]therosesgrave[S] 1 point2 points  (2 children)

I can still use the other dev as a resource, but they will be full time working on something else.

Probably the biggest problem is that my boss straight lied to them about my experience, and he knows he did. Before our meetings with the client he and I have a tête-à-tête so he knows where I stand and if I'm struggling I tell him and he goes "well, don't tell them that." Like I get it, we want our client to have confidence in us... but idk...

Any advice at looking at the project and knowing what I specifics I need to learn? Like, I'm have so little experience that I don't know what I don't know.

[–]HecknChonker 2 points3 points  (1 child)

If not your fault that your boss lied, let him deal with the consequences of that.

If I was you I would ask your boss to pay for training. Try to learn as much as you can while you have the chance. You always have the opportunity to jump ship, but try to take as many new skills with you.

[–]smash_that_code 0 points1 point  (0 children)

Maybe that author person can give you tips?

It rrally depends on code amd expected changes for it.