Thoughts, ideas and opinions on all things software innovation, strategy, design, and development – from the technology experts at Revelry
Getting stuck isn’t a bad thing. Actually, getting stuck on my first day on my first project may have been the most valuable thing to have happened. It was in that moment that I learned all I needed to know about transparent communication at Revelry.
Sometimes, clients even say “but I don’t care about the commitment.” Firstly, I question whether that is true deep down. It’s hard for me to imagine someone paying a significant amount of money to have a problem solved,and then not caring when that solution ships, or even which parts of the solution ship in which order.
I’ve chosen this specific list as part of an effort to foster a shared understanding of commonly used terms. This “glossary” doesn’t exist in a vacuum – it can (and should) continue to be challenged and evolve over time as our understanding changes.
The hard part of this was recognizing the algebra beneath layers of domain-specific business rules.
I’m pretty lucky to work with a larger overall company that includes a larger design team, so I can count on them for a second eye. But if you’re working on a small startup and you’re the only designer there, have no fear. It can get overwhelming, but I’m here to help.
Before investing heavily into the entire IPFS infrastructure, you’ll need to wade through the misconceptions and the fud (Fear, Uncertainty, and Doubt).
The team that seeks out feedback and views it as an asset rather than a slap in the face is the team that delivers real value to clients.
Tweak your environment regularly. Try something new, and improve your productivity. One thing that definitely deserves some care is the terminal/shell.
I, for one, am looking forward to the dawn of the metaverse, and I hope to see all of you on the other side.