It feels amazing to be working with such an ambitious Team. Holly Jooyoung Diamond ??Kudos to your efforts!
Why does this job platform’s UI place so much importance on a map? CC: WorkOnward (Techstars '23) Your Job, on the Map., Holly Jooyoung Diamond ??, Sherveen Mashayekhi, Brian Hollins
Some thoughts on story splitting that's come up recently. Vertically slicing stories doesn't necessarily mean slicing a chunk to contain the skillsets of everyone on the team. Sure, it should contain as much from every level as possible when it makes sense. Ultimately, it's a way to break down work in a way that can be easily demoed and is a potentially shippable functionality that can be consumed for the users. ? Some changes aren't going to need UI updates. Instead of asking 'Is that a horizontal slice?', we should ask ourselves: 'Can our users easily see the change and are they getting value from it?' ? When a new feature or functionality comes in, we work on it because we know what value it has to our users. Every time we vertically slice, we should be able to answer that same question.
Software Engineer | Front-End Web Developer | React | JavaScript | CSS | HTML | TailwindCSS | Python
My 6-week Chingu Voyage is complete!! Our task was to create a responsive SPA that would be used to split group expenses. Here it is: https://islice.netlify.app We started with 9 team members - a Product Owner, 2 Scrum Masters, a Designer and 5 Developers/Engineers. Our team went through some rough times with a personal loss, family illness, balancing other work, several natural disasters, and unfortunately 3 members leaving the team. But despite all odds, we persevered and created an amazing product! I come away from this experience with a new working knowledge of Agile process, Git, and team communication. Through weekly sprints and daily stand-ups, I learned what questions to ask to keep the project moving forward. I learned to communicate my concerns with the team when things seemed unclear and to accept constructive criticism when I have overstepped my bounds, or when I have made a mistake. I have also noticed the importance of thoughtful system design, and how the choices made in the beginning can complicate future endeavors. One example would be choosing libraries (I’m looking at you, react-select) that seem cool but cause complications later in logic or styling. Another would be how the data flows through the components and how if you don’t reuse components (and instead build two components that are nearly identical), there might be confusion as to where the data is coming from/going and you may have redundancies which makes it difficult to locate and squash bugs. VS Code search was a lifesaver! I was excited to practice styling with Tailwind and connecting a Firebase/Firestore for data storage. I also learned a bit about data visualization using ChartJS and I’m excited to try it out in other projects. I struggled a bit with random avatar generators (choosing a library vs API, and then choosing the best API), but eventually found a solution. And I worked with my teammate to discover and solve a Netlify deployment issue. If you are dev that needs experience working in a team, I highly recommend Chingu.io
Marketing & Business Development | Skalebot | Storyteller | Canva Creator | Helping you work smarter and create better
I ignored it for 20 days—so today, I finally started! (1.5 years after quitting at Day 7) Back in August 2022, I excitedly jumped into the Daily UI Challenge. I was so ready. My first project? A coffee shop app. But by Day 7, I quit. Why? I felt lost. I thought I wasn’t “learning the right way,” and I feared my designs weren’t good enough. Fast forward to 2024: I promised myself I’d restart. January? Too busy. November? Still nothing. 20 DAYS of prompts sat in my inbox, unopened, while I let fear win. Today, I said: Enough. And you know what surprised me? I still remember the basics I learned & that’s where I started—again. → The Daily UI Challenge - Day 1: Sign-Up Page It’s simple. Is it perfect? No. But it’s a start. And starting is what matters most. Fear only grows the longer you wait. Taking that first step shrinks it. P.S.: I’d love to hear your open and honest feedback—what works, what doesn’t? #DailyUI
Two weeks ago I left my role at Ben, a company where I've grown and learned a lot and full of great people. Why? Because I always wanted to build my own products and felt now is the right time to do it. Over the past two weeks, I've researched, studied, designed, tried, failed, learned, and most importantly...had a ton of fun! I'm also happy to announce that I already have my first small product ready to launch! It's a small tool you can easily add to your website to collect feedback about UI issues, translations, and many more! If you have a website and want to give it a try, I'm giving away to the first 20 users a 1 YEAR FREE TRIAL to start getting feedback about my feedback tool, haha. Check it out at https://captureecho.com and let me knowif you have any comments!
???? Why is authenticating product integrations an important process for your company to master? Merge's Head of Technical Services (Pritak Patel) and Product Marketing Manager (Irene Hu) are hosting a webinar to discuss the following: ?? The significance of a smooth authentication experience ?? Challenges posed by various authentication methods ?? Merge Link - Merge's UI component guiding your users through authentication RSVP to join us on March 19th at 11am PT/2pm ET: https://hubs.li/Q02nCzYz0
