nice2win 🛠️🎰📈 @nice2winDapp - Twitter Profile

Pinned Tweet

nice2win 🛠️🎰📈 @nice2winDapp

over 3 years ago

New contracts, Dune analytics, $N2W news and more in our monthly update! Go and give it a read! https://t.co/E4swWPWbfv

3

2

0

793

nice2win 🛠️🎰📈 @nice2winDapp

over 1 year ago

Our games will soon be closing yet you'll find the same degenerate odds on Dorgewurld in 3 weeks

0

3

0

60

nice2winDapp retweeted

pstar @CryptoPstar

about 2 years ago

Situation rn at @KengLernitas @zorksees @kain handing over the reins while @mastermojo83 watches on😂

2

17

5

0

624

nice2win 🛠️🎰📈 @nice2winDapp

over 2 years ago

@AlgodTrading We're finishing up the development of our token and it's utilities. 3rd biggest crypto casino on-chain btw. Take a look at our Medium: https://t.co/iC5i20YNro

0

1

0

7

Who to follow

Full-time airdrop hunter, part-time degen 💸 | Clicking, claiming, and praying for that moon 🌕

nice2winDapp retweeted

Santiago

@svpino

almost 3 years ago

Scrum is a cancer. I've been writing software for 25 years, and nothing renders a software team useless like Scrum does. Some anecdotes: 1. They tried to convince me that Poker is a planning tool, not a game. 2. If you want to be more efficient, you must add process, not remove it. They had us attending the "ceremonies," a fancy name for a buttload of meetings: stand-ups, groomings, planning, retrospectives, and Scrum of Scrums. We spent more time talking than doing. 3. We prohibited laptops in meetings. We had to stand. We passed a ball around to keep everyone paying attention. 4. We spent more time estimating story points than writing software. Story points measure complexity, not time, but we had to decide how many story points fit in a sprint. 5. I had to use t-shirt sizes to estimate software. 6. We measured how much it cost to deliver one story point and then wrote contracts where clients paid for a package of "500 story points." 7. Management lost it when they found that 500 story points in one project weren't the same as 500 story points on another project. We had many meetings to fix this. 8. Imagine having a manager, a scrum master, a product owner, and a tech lead. You had to answer to all of them and none simultaneously. 9. We paid people who told us whether we were "burning down points" fast enough. Weren't story points about complexity instead of time? Never mind. I believe in Agile, but this ain't agile. We brought professional Scrum trainers. We paid people from our team to get certified. We tried Scrum this way and that other way. We spent years doing it. The result was always the same: It didn't work. Scrum is a cancer that will eat your development team. Scrum is not for developers; it's another tool for managers to feel they are in control. But the best about Scrum are those who look you in the eye and tell you: "If it doesn't work for you, you are doing it wrong. Scrum is anything that works for your team." Sure it is.

svpino's tweet photo. Scrum is a cancer.

I've been writing software for 25 years, and nothing renders a software team useless like Scrum does.

Some anecdotes:

1. They tried to convince me that Poker is a planning tool, not a game.

2. If you want to be more efficient, you must add process, not remove it. They had us attending the "ceremonies," a fancy name for a buttload of meetings: stand-ups, groomings, planning, retrospectives, and Scrum of Scrums. We spent more time talking than doing.

3. We prohibited laptops in meetings. We had to stand. We passed a ball around to keep everyone paying attention.

4. We spent more time estimating story points than writing software. Story points measure complexity, not time, but we had to decide how many story points fit in a sprint.

5. I had to use t-shirt sizes to estimate software.

6. We measured how much it cost to deliver one story point and then wrote contracts where clients paid for a package of "500 story points."

7. Management lost it when they found that 500 story points in one project weren't the same as 500 story points on another project. We had many meetings to fix this.

8. Imagine having a manager, a scrum master, a product owner, and a tech lead. You had to answer to all of them and none simultaneously.

9. We paid people who told us whether we were "burning down points" fast enough. Weren't story points about complexity instead of time? Never mind.

I believe in Agile, but this ain't agile.

We brought professional Scrum trainers. We paid people from our team to get certified. We tried Scrum this way and that other way. We spent years doing it.

The result was always the same: It didn't work.

Scrum is a cancer that will eat your development team. Scrum is not for developers; it's another tool for managers to feel they are in control.

But the best about Scrum are those who look you in the eye and tell you: "If it doesn't work for you, you are doing it wrong. Scrum is anything that works for your team."

Sure it is.

2K

25K

4K

12K

5M

nice2win 🛠️🎰📈 @nice2winDapp

almost 3 years ago

It's been easier playing dice than playing the market currently #volatility 📈📉

0

3

0

105

nice2win 🛠️🎰📈 @nice2winDapp

almost 3 years ago

I'm helping test @friendtech, the marketplace for your friends on Base 🐰 Get the app and search for my Twitter username to be an early holder of my shares 🤗

1

2

0

110