Brian Walsh

😀 Upcoming Complimentary Angular Coaching Session with SeaLadder: 📅 Angular Front-End Development Intro Session: Wednesday July 3rd at 8 PM AEST If you've already signed up for the Angular session, we look forward to seeing you then! Calendar invites and additional information has been sent out via email. Haven't signed up yet? Head over to our website or complete the Google Form below. My partner Adam Pond is going to be your rockstar coach - and if you know Adam you know his passion for learning is unmatched. The course is 4 weeks long, culminating with a project that you can proudly put on your CV 🚀 Why Join SeaLadder? 😎 SeaLadder is revolutionizing upskilling for software developers through a community-driven approach. As a member, you can: - Learn at your own pace or within a cohort - Become a mentor and share your expertise - Engage in diverse tech topics - Grow with a supportive community Special Beta Launch Benefits: - Free coaching sessions - One month free access - Discounted rates for the first three billed months Visit SeaLadder for more information and to secure your spot. 🌊 SeaLadder: Empowering Developers through Community and Learning 🌊 #angular #professionaldevelopment #frontenddevelopment #softwaredevelopment

4

THIS... is why we started Summit Venture Studio... These are 27 software development projects Spencer Walker and I worked on while inside the University of Utah. The Y-axis is Millions of dollars (valuation). The X-axis are value inflection points. The two companies that had the highest value at exit/raise in this chart were actually valued much higher but it skewed the graph so I am just showing how much they raised. The GREEN all exited or raised money, the BLUE were all licensed to established companies so a real value was never set after that and the RED were shut down. An interesting point to think about is that these projects were "assigned to us" and were not "chosen" as good business opportunities. Now we are screening the deals we work on for commercial viability. I am super excited for the future. Who wants to come and play with us and start a company with us? We have 8 in the pipeline and I just finished a meeting where we agreed to launch our next company hopefully in the next few weeks.

85

14 Comments

RAG architecture implementation is not as simple as it sounds. How can one optimize the retrieval mechanism so that speed doesn't become an issue? How can one reduce the hallucination specifically where the accurate answers is extremely critical for the business? Is Vector similarity is the accurate answer there?

6

2 Comments

Here's a demo of my app, q.buzz

2

The majority of developer tutorials are BORING and don't work. 😩 Why? They are written from the perspective of the project/product...and not that of the developer. My video walks step-by-step through how to fix this. (Link to the full video in first reply)

18

5 Comments

For the first time in my 15+ years of career I wrote an ecommerce replatform proposal to a client that 𝐃𝐎𝐄𝐒𝐍'𝐓 𝐢𝐧𝐜𝐥𝐮𝐝𝐞 301 𝐫𝐞𝐝𝐢𝐫𝐞𝐜𝐭𝐬, and it's not because the URL structure will remain the same, it won't, it's because... The old platform was some weird custom angular front-end build that made it completely impossible for search engines to index anything beyond homepage let alone rank for something. So, no need for redirects because old URLs that have been live for years aren't even indexed. #magento #replatform #ecommerce

14

3 Comments

I’m dusting off my old podcast once more for (hopefully) another full season. For this episode, I had on Jacob Kastensmidt to talk about web components and Lit. We talked a little about what web components are, as well as how they fit into the larger frontend ecosystem. Check it out if you’d like to learn more about Web Components: https://lnkd.in/efYNXnZM

2

"Promising God and delivering email prompts."—Meredith Whittaker on big tech and AI. We're missing the genuine utility of this latest crop of machine-learning tools by burying it in hype and poorly considered applications. This is a design problem, not (only) a matter of marketing or hubris. The job of UX is to identify problems worth solving, pick the right technology (if any) to solve that problem, and then set expectations and channel behavior in ways that match the system's capabilities. That's ALWAYS the job for design. But setting expectations and channeling behavior is more important than ever in cases like AI-mediated experiences where designers are not always directly in the loop. Lots of services are dropping the ball on all of those fronts in the rush to get AI features out the door. It's good to explore and experiment—and look, we're going to fail a lot as we learn to use this new design material. But let's not front experimentation as anything more than it is. Sentient Design is all about using AI tools (that's all AI is for now—software, an enabler) in the right way to solve real problems. There's so much opportunity and good work to be done. But let's stop smoking our own supply.

23

4 Comments

Action. Style. Key details. ASK - the 3 steps to using AI. Action - Explain what you want Copilot to do. Style - Describe the format you want the response presented in. Key details - Set the stage with more context about your situation. https://lnkd.in/eins5D2H #msftemployee #ai #copliot #generativeai

3

When there is great uncertainty, there can't be predictability to any useful level. We have to reduce uncertainty to where it can be managed effectively, and we do this by running experiments... trying things. Does the stakeholder like what we've done? Does the customer like what we've done? Are we solving the problem that customers have? This puts us in the 'complex' quadrant of the Cynefin Model, where we have to try and (perhaps) fail, perhaps repeatedly, until we know enough. Yet, we still have a goal in mind and we at least know the first few things that need to get done... or the first thing we need to test to determine feasibility. Apple knew that unless it could source a ruggedized hard drive that would withstand being carried and occasionally dropped, the iPod would not be successful... so getting a commitment from Western Digital (who had been working on such a drive and was almost ready to ship) was the key decision point. The Wright Brothers knew that unless they could figure out a way to turn their airplane without 'skidding' and stalling a wing (a problem that had killed many of their inventive contemporaries) they couldn't build a safe airplane... oh, and find a lightweight, powerful-enough motor while you're at it. It all comes down to reaching decision points: do we know enough to know whether to continue, or whether to cancel our effort? In the example below (waterproofing a below-ground basement), we are going to have to continue. Therefore, we want to continue only at the pace at which we are certain of the decisions we're making. Is what we're doing working? If so, do more! If not, do something else. That is exactly what the contractor did in the post below, making 'MVP' experiments until the path to success was clear, until they had the 'Aha!' moment. So, when do we get predictability with useful accuracy? At the 'Aha!' moment. Figure out what 'Aha!' moments are needed, devise experiments to reach those moments and drive enough uncertainty out (you'll never get to zero) to where the range of uncertainty is acceptable. #predictability #forecasting #estimation #commitment #agile #planning #riskmanagement #projectmanagement

3

3 Comments

Great points here by Clay Griffith. In the dynamic world of technology, the question surrounding your tech stack shouldn't be - does it work today? But rather - will it help me effectively compete tomorrow? When evaluating whether your tech stack requires an upgrade, the focus shouldn't solely be on its current functionality. The more pressing question is, does your tech stack offer a scalable, adaptable foundation that supports continuous innovation and improvement, all while maintaining a relatively low total cost of ownership? In today’s fast-paced market, resting on the laurels of a tech stack that 'just works' may leave you lagging behind. Innovation isn't a one-time event; it's a continual process. If you're not consistently pushing the envelope and exploring how to better serve your clients through technology, rest assured, your competitors are. In contemplating the future-readiness of your tech stack, consider these critical points: 🔍 Scalability: Can your technology grow and adapt as your business evolves? 🔗 Integration Capabilities: How well does it play with new technologies or systems you may need to adopt? 📊 Metrics: What data supports your decision-making process? 🔧 Maintenance and Development: Are the costs and efforts sustainable in the long term? 💡 Innovation Potential: Does it enable you to quickly test and deploy new ideas? Remember, choosing the right tech stack is about laying the groundwork for tomorrow’s success, not just meeting today’s needs. As you ponder your strategic tech decisions, I encourage you to think not just about what works now, but about what will empower you to excel in the future. #TechStrategy #FutureProofing #InnovationMatters

3

I initially adopted bootstrapping out of necessity. But today, I view it as the default founder operating system. The rules have also changed. ▪️ Traditional bootstrapping is often viewed as self-funding, but a better descriptor today is customer-funding. ▪️ Traditional bootstrapping is still seen as mutually exclusive to fundraising, but many bootstrapped companies customer-fund to traction and then choose to pursue fundraising - not for survival, but growth. This is why I coined a new term: “BOOTSTART”, which is a play on bootstrapping and starting up. In yesterday’s newsletter, I shared practical tactics for bootstarting your idea to traction. In case you missed it, 👇 https://lnkd.in/gx4MBAkp

34

4 Comments

🤔 "Can we add wordcloud to recognize PSF donors?" >>> import wordcloud ✅ Done Thanks to Carol Willing for the idea and Joe Carey for actually implementing it on the website! Python Software Foundation Donations page now has a wordcloud, in the shape of PSF logo! 🤩 Check it out on this page: https://lnkd.in/gshADfjT Issue tracker: https://lnkd.in/gJ6hcFra #Python #ThePSF

27

Action. Style. Key details. ASK - the 3 steps to using AI. Action - Explain what you want Copilot to do. Style - Describe the format you want the response presented in. Key details - Set the stage with more context about your situation. https://lnkd.in/eins5D2H #msftemployee #ai #copliot #generativeai

1

Here’s why you should 100% use Waterfall for your next project! Wait, no I can’t say that with a straight face 😆 But there is definitely a time and a place for waterfall 👇 Agile has trouble with projects like the NASA CADRE project we worked on. We can’t exactly deploy the software on the moon, → then tweak it, → deploy it again, → tweak it again, Over and over and over. It would take years and the development would be insanely slow. What are some projects that you’ve worked on where waterfall development just made more sense than agile development? Let me know in the comments! #agiledevelopment #waterfalldevelopment #Softwareengineer #softwaredeveloper

16

1 Comment

How do you make technical folks trust your marketing? The mistake we notice companies make, again and again, is to promote a solution before they’ve shown they know about the problem developers want to solve. What strategies have you found effective to demonstrate you understand dev problems?

7

2 Comments