epetre

You guys are the best example of a ghost job... and you are shamelessly posting every month too....

https://en.wikipedia.org/wiki/Ghost_job

https://images.app.goo.gl/zFMba68BzDgYMvfQ7

I second this. Similar experience with their interview process. Also, if you ask for feedback, they stop answering.

Pretty sure these guys are not really hiring, they just make you go through the process (tests, interviews) and build a pool of potential candidates.

In my experience, these guys don't follow-up on interviews. They wasted my time with a test and they have been posting here for more than 6 months.

Holding a startup and it's users hostage is standard Web3 practice, right? So excited for the Metaverse yayy!!

It's their job, but sometimes it's easier to argue or prove your point with some clear graphs and objective metrics. I see it as a tool to improve for developers and as an objective view of what really happened.

Sure it helps managers do their jobs, but I think that in some cases we might not even need a manager at all.

You are absolutely right, managers could ask developers for those metrics. It's actually how it's it's done right now, in my experience.

The value I see for developers is to get some objective metrics on a feeling they have. If they think something is inefficient, they should be able to be able experiment with their process. But that needs to be done a bit more objectively.

I think developers could also use this as proof that that the problem is not always with the team but sometimes it may come from management.

The scope creep is a good example of this. A manager keeps adding stuff to the current iteration and the dev team gets swamped. A widget could clearly show the impact of that scope variation.

I see value for the dev team, end-users and management if it's done right.