14

So....
I was asked to transfer a spaghetti Android/iOS project to xamarin for a bank client yesterday because "that's what they use".

This is a crm/loyalty app that has been around for 2+ years now (you can imagine the mess). On top of that I have no knowledge of c#, .net or xamarin.

So I ask: "When is this supposed to be delivered?"

Boss: "It was scheduled for 2 weeks ago but let's say 2 weeks from now"

Me: "..... This is a huge remake it won't be even close to ready in 2 weeks"

Boss: "Let's check on the progress in 2 weeks and see how it goes"

Why is it hard for bosses to provide an actual timeframe???

He's been pulling the same crap with junior devs for years and of course they get nervous and create more spaghetti code...

Anyway long story short (not) I have an interview Monday!

Let's hope it's not more of the same!

P.S.: to junior devs: When you are given a deadline... IGNORE IT.

Comments
  • 6
    No, don't ignore it. This is a sign of immaturity (which might be the case). Say no, and explain why something is not possible. Ignoring is never the way.
  • 0
    @kpenc "Ignore the warnings, it's the errors you should be focusing on" - Abraham Lincoln 2k17
  • 0
    @kpenc I meant don't focus on the deadline. Every project is late anyway and in most cases the people setting the deadlines don't understand or care about the consequences.
    That's my experience anyway
  • 0
    @kpenc
    Also personally I do explain! Every time.
    Never made a difference mate...
    They always stuck to the initial deadline
  • 0
    How can someone learn a new language + framework and deliver such a huge project in 2 weeks? People can hardly learn the basics in 2 weeks. It's a big learning curve. Anyway, you were there because of your skills, you're not supposed to do anything that's out of your skills /expertise.
Add Comment