Take the pressure out of your way. Get Salesfinity It's free to try.
POV: When you don't have enough pipeline for Q4 (due to holidays)
Skip to main content
Take the pressure out of your way. Get Salesfinity It's free to try.
POV: When you don't have enough pipeline for Q4 (due to holidays)
To view or add a comment, sign in
Q4 is moving along quickly, before you know it, it will be Q1 2025.
To view or add a comment, sign in
This is a big deal. I've come across very few open source projects which ship weekly releases (though they do exist). Ironically, while it takes a lot of work to get to a constantly releasable state, it's less work to maintain. Previously, we were following a six-week release cycle. Every release was painful. Flaky tests would accumulate, especially on less commonly used platforms. To get there, the team - Fixed over 350 issues and flaky tests - Improved testing infrastructure, especially around performance regressions - Most importantly, built the discipline around consistency. Overall we're catching regressions faster and shipping features faster.
We recently moved to weekly Ray releases to ship features to our community faster. 🚀 Doing so required us to fix flaky tests and completely revamp our release process. 👊 Read more here: https://lnkd.in/gUejngmD
To view or add a comment, sign in
When you get 3 new users on launch day after grinding for 2 months
To view or add a comment, sign in
So make the tech accurately first then after you've finished you can play with it
To view or add a comment, sign in
Because moving quickly (and safely) is a competitive advantage ;)
We released Ray 2.20 this week! (our third weekly release). You'll notice the numbering has changed (incrementing from 2.12.0 -> 2.20.0). The bump indicates a release on all platforms, whereas our weekly release cadence includes a subset of platforms. Some stats for this release 🍒 Zero cherrypicks (despite releasing on all platforms) 💇♀️ Released 2 days after branch cut Sounds easy but it really isn't 😅 Weekly releases mean that we get features & fixes to our users faster.
To view or add a comment, sign in
From hype to disaster 🚨 Sometimes the biggest flops teach the best lessons! Today I learned about Segway - that cool-looking human transporter that was supposed to change the world but ended up falling flat (pun intended!). A $100M+ oops that's got me thinking about my final year project... Quick wisdom bombs from the Segway story 💡 1. Problem First, Solution Later Cool tech is not an actual need (Segway was awesome, but nobody asked for it!) 2. Test Early, Fail Fast $100M spent in secret - Big yikes (Note to self: Get feedback ASAP) 3. Price it Right $5,000 for personal transport? (No wonder cycles won this race 🚲) 4. Keep it Simple Sometimes the simplest solution wins My Final Year Project Game Plan: - Test early, test often - Actually talk to users - Solve real problems, not imaginary ones - KISS (Keep It Simple, Student!)
To view or add a comment, sign in
POV: You lose weight in 3 months 🥝 Save this post and remember these tips for later!
To view or add a comment, sign in
❓Did you know❓ Our excellent systems are not only designed to create ramps, but they can also be used to build platforms. This provides an easy way to create a level surface, helping to avoid going up and down over thresholds. They can also be used to create steps and resting platforms for portable ramps. #ramps #platform #excellentsystems #solutions #leveling #threshold
To view or add a comment, sign in
Getting users to love your product isn't enough. Somebody needs to give you rectangular pictures of kings and presidents in exchange for it. Product pitfalls and how to avoid them, on today's Troubleshooting Agile with me and Jeffrey Fredrick: https://lnkd.in/eM6esdBd
To view or add a comment, sign in
Create your free account or sign in to continue your search
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.
New to LinkedIn? Join now
or
New to LinkedIn? Join now
By clicking Continue to join or sign in, you agree to LinkedIn’s User Agreement, Privacy Policy, and Cookie Policy.