epetre

6 ms·

1.
by epetre 2y ago
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
2.
by epetre 2y ago
I second this. Similar experience with their interview process. Also, if you ask for feedback, they stop answering.
3.
by epetre 2y ago
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.
4.
by epetre 3y ago
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.
5.
by epetre 5y ago
Holding a startup and it's users hostage is standard Web3 practice, right? So excited for the Metaverse yayy!!
6.
Show HN: A smart Tinder for friendships
3 points by epetre 9y ago|1 comments
7.
The code is not the product(blog.in-sight.io)
2 points by epetre 11y ago|0 comments
8.
Ask HN: How to write good technical documentation for SaaS
1 points by epetre 11y ago|0 comments
9.
Show HN: We invented the state flow chart to help agile teams trace the process(blog.in-sight.io)
1 points by epetre 11y ago|0 comments
10.
2 common issues you can quickly spot by tracking your Cycle time(blog.in-sight.io)
1 points by epetre 11y ago|0 comments
11.
Your team's commitment is not a guarantee(blog.in-sight.io)
1 points by epetre 11y ago|0 comments
12.
Don't assign work to developers(blog.in-sight.io)
3 points by epetre 11y ago|1 comments
13.
Empower your daily standup(blog.in-sight.io)
1 points by epetre 11y ago|0 comments
14.
3 reasons why story points are better than hours(blog.in-sight.io)
2 points by epetre 11y ago|1 comments
15.
6 ways you can deliver more by starting less(blog.in-sight.io)
2 points by epetre 11y ago|0 comments
16.
A Kanban View for Pivotal Tracker(blog.in-sight.io)
1 points by epetre 11y ago|0 comments
17.
2 reasons why estimating isn’t actually about estimating(blog.in-sight.io)
2 points by epetre 12y ago|1 comments
18.
A Pivotal Tracker dashboard that lets you change your done state(blog.in-sight.io)
1 points by epetre 12y ago|0 comments
19.
How defining done leads to better software quality and increased productivity(blog.in-sight.io)
1 points by epetre 12y ago|0 comments
20.
2 metrics most velocity charts are missing(blog.in-sight.io)
1 points by epetre 12y ago|0 comments
21.
3 benefits of improving your burn-down charts(blog.in-sight.io)
4 points by epetre 12y ago|6 comments
22.
by epetre 12y ago
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 mana
23.
by epetre 12y ago
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.
24.
3 lessons engineering should learn from sales and upper management(blog.in-sight.io)
9 points by epetre 12y ago|7 comments