What were some key patterns and subtleties that significantly influenced hiring decisions and candidates moving on to next-steps? That is a question I often get asked. After a long time on my to-do list, I am finally writing down my thoughts based my personal experience as a hiring manager and engineering leader having interviewed hundreds of engineering candidates through my career.

As we proceed, please know that I won't cover how to answer specific technical questions and l33t code type things. For brevity, let's just assume technical chops are sufficiently assessed elsewhere.

I’ll focus what things interviewees did that made the biggest impact on decision-makers but often get overlooked. Some play to the logical conscious side but many are important as they touch on our human subconscious side of our brains.

Okay, let's jump into it! Here are my personal tips and notes on what makes a candidate memorable going into interviews. I hope it helps for anyone reading! (Including my future self as a reminder.)

The Basics: Starting on the Right Foot

1. Timeliness and Preparedness
   • Being a few minutes early shows respect for the interviewer’s time and avoids adding stress at the start of the call.
   • Setup your Zoom, Webex, Google Meet client etc... well ahead of time, make sure the camera and mic settings are working well
2. For remote calls - You are your video frame
   • Angle your camera so your eyes are at ~1/3rd down from the top of the overall image. Done right you should have your head and shoulders all visible.
   • Ideally you'll look straight into the lens of the camera during the call. I know not always possible, but try and avoid looking at a monitor to your left or right not appearing to make eye-contact.
   • Ensure you’re well-lit on camera
     • Use natural lighting by windows
       or
     • Use a strong nearby light source. Ideally a bright lamp/key-light at 45 deg from you, and is set pointing at your face just above your head
   • Eliminate background visual distractions by using a virtual one or move to where you have a clean minimalist background.
   • Check that your audio is crisp, and eliminate risk of background noise (close that door/find a good spot in the house).

First impressions are subtle but powerful. Coming across as prepared and professional immediately sets a good start to an engaging conversation.

Energy: Bring Your Best Self

One of the simplest but most effective ways to set yourself apart is through your energy.

• Enthusiasm is Contagious
  Show genuine excitement for the role, the company, and the conversation. Enthusiasm demonstrates that you care about the opportunity and makes the conversation more enjoyable for both parties.
• Draw from Dale Carnegie’s Timeless Lessons
  The principles from How to Win Friends and Influence People are classics for a reason. They work. Here are a few key takeaways that are invaluable for interviews:
  • Smile: A warm, natural smile puts both you and your interviewer at ease.
  • Show Genuine Interest: Be sincerely curious about the role, the team, and the interviewer. You shouldn't need or feel like you're acting. Just think actively curiously about the person and team on the other side.
  • Admit Mistakes: If you stumble or don’t know something, own it honestly and pivot back to what you can contribute. DO NOT try to lie, make excuses or make things up. It is easy to see right through these things and is an immediate red flag for seasoned interviewers.
• Mirror and Match Energy
  Match the interviewer’s tone and energy, then elevate it slightly. If they’re low-energy, bring positivity without overdoing it; if they’re excited, match their enthusiasm.

A little more energy on your part ensures you’ll stand out from others to the interviewer having to conduct a string of interviews.

Just like the old saying "the camera adds on 10lbs", the camera also somehow seems to reduce your energy by 20%! So don't be shy to add a bit more energy boost to compensate.

Approach Interviews as a Collaboration

Especially if you are nervous – the mindset you bring matters. This isn’t an adversarial “you vs. them” scenario or a hierarchical “boss vs. staff” situation. Approach it as a partnership: a conversation to discover if working together would create mutual success.

When you reframe the dynamic as a collaborative opportunity, it removes unnecessary pressure and fosters a more authentic connection.

Response Strategy: Clarity Wins

1. Direct and Focused Answers
   Stick to the point. Avoid going off on tangents, meandering or over-explaining. For engineering roles especially, do not feel the urge to fill in silences nervously by rambling. Thoughtful pauses and thoughtful clarification questions are better than rambling. Overall be thoughtful of the time and attention of the interviewer from their perspective.
2. Structure Your Responses
   Use frameworks like STAR (Situation, Task, Action, Result) to deliver organized answers. This helps the interviewer follow your thought process and leaves a stronger impression.
3. Honesty Over Guesswork
   Maybe the #1 tip of all. If you don’t know an answer NEVER MAKE things up. Best to admit you don't have that experience or skill set transparently. Most interviewers are more interested in how you think and how you approach problems than whether you know everything off the top of your head. Do not risk braking the little early trust your are just trying to build up with this new relationship.
4. Problem-Solving Questions: Think Aloud
   • Rephrase the question to confirm your understanding. Important: Do not ever assume a question and rush through starting an answer before it is fully done being asked.
   • Walk through your thought process step by step.
   • Use examples from past experiences where possible, but it’s okay to suggest how you’d approach it based on what you know.

Timeless Principles for Connection and Trust

One of the biggest differentiators in an interview is your ability to build rapport and establish trust. Here’s where even more Dale Carnegie principles shine:

• Listen Actively: Avoid interrupting or speaking over the interviewer. Listening well shows respect and attentiveness. (Tip: If you ever notice the interviewer wanting to interject or cut in, acknowledge that and pause and ask if they wanted to say something. DO not plow through obliviously. This is a big sign of respect and attentive interaction.)
• Use Their Name: This small habit makes the interaction more personal and engaging.
• Own Your Shortcomings: If you don’t have all the answers or make a mistake, be honest. Owning up gracefully builds credibility.
• Show Empathy: Acknowledge their perspective, especially if they express concerns about challenges you might face in the role.

Ending Strong: Questions That Leave a Mark

The questions you ask at the end of the interview are an opportunity to demonstrate your curiosity and alignment with the role. Here are a few examples of some of my favourite:

• What does success look like in this role in the first few months?
• What challenges do you foresee for someone stepping into this position?
• Can you tell me more about the team dynamic and how this role fits into it?
• What’s the next step in the hiring process?

Good questions show you’re thoughtful and serious about the opportunity while also giving you valuable insight into whether this is the right fit for you. It also subconsciously sets me as an interviewer picturing you in the role.

Avoid asking questions that purely focus on what the company can do for you at a hiring manager, team panel interview -- e.g. salary, bonus, perks, titles etc... Those aspects should have and typically be covered with other recruiter logistical calls if done right. Your goal is to understand the job, role, work arrangements for hiring manager and team panel interviews -- avoid appearing aggressive in seeking for what you can gain. Subtle art here, but right time for right conversations -- screening early or during the offer negotiations phase.

The Takeaway

A successful interview is more than just a technical Q&A. It’s a chance to connect, build trust, and demonstrate that you’re someone the team can depend on. By focusing on preparation, energy, and interpersonal skills, you’ll elevate yourself from being just another competent candidate to someone they’ll remember and want to work with.

Even if you don’t get the role, you’ve built a connection, and a positive impression can open doors within the company or with the interviewer in the future.

Are you a leader who sometimes feels like a bottleneck in decision-making or in driving team initiatives? Wondering how you can build autonomy and nurture the next generation of leaders in your team? I’d like to share a practice I learned from multiple decades of being on teams as a member, tech lead and engineering leader and manager. It is a practice that I found consistently brought about higher performance teams, greater engagement and sense of empowerment for each and every team member. And most of all, a solid way to grow and foster the next generation of leaders. Too good to be true?... Its actually simple.

The practice is rotating the facilitation of team rituals among members. This could include everything from daily standups and sprint retrospectives to planning sessions and backlog grooming. Whether they’re new grads or seasoned engineers, everyone gets a chance to lead and contribute in new ways.

At this point, you may be asking "Alvin, does this not mean I am not doing my job team leader job by running these?" Here's the answer. No, believing that the team can only be successful if you make every decision, run every team meeting and "crack the whip" by pushing your title around is a trap and lack of confidence trope that new managers and leaders get wrong about what their role as a "leader" means.

The truth is that your role as a leader is not to be the irreplaceable "rockstar" of the team, smartest technical person or sole dictator of all tasks. Your job is to be the coach, the music producer, the designer of processes to make every member shine and bring about and foster a healthy and cohesive team of highly motivated and engaged individuals that delivered consistently, sustainably and resiliently as a team. The success of the team is the success of the leader.

So in this practice of rotating leadership rituals you are achieving this by way of getting the best engagement, sense of responsibility and creativity out of all members. I.e. You will grow a team of leaders with high agency than a team of task assigned "workers".

Why This Works

Rituals are more than recurring meetings; they’re opportunities for growth, collaboration, and team bonding. Letting different team members lead these sessions provides fresh perspectives, encourages leadership skills, and strengthens the team’s collective resilience. As the manager, you maintain oversight, but allowing team members to shape these processes promotes initiative and keeps everyone thinking like a leader.

I’ve seen quieter members gain confidence and senior members develop the skill of guiding others. Instead of relying on just a few voices, the entire team shares responsibility, supporting whoever is leading and stepping in to keep things on track when needed. This not only raises the quality of decision-making but also builds camaraderie and alignment toward shared goals.

How to Get Started

Start small by rotating just one ritual. For instance, announce that standup facilitation will rotate alphabetically every sprint – by first name or by a sequence you think will be comfortable. Initially, you might start with senior team members, followed by intermediates, then juniors. Over time, you can settle on an order that’s comfortable for everyone or just keep it alphabetical for simplicity.

Once the team is comfortable with this, expand the practice to other rituals, like backlog grooming, retrospectives, and sprint planning. Keep in mind that some will jump at the chance to lead, while others may be more hesitant. Your role is to encourage balanced participation, making it safe for quieter voices to be heard. And for your senior team members, it’s a valuable opportunity with coaching and a lesson in fostering inclusivity, not just taking charge.

Why It’s Worth It

This practice can transform a group into a resilient, self-sufficient unit. Even if a few key members are unavailable, the team will have the capability to continue operating smoothly. As a manager, you’ll know the team can handle challenges on its own, allowing you to focus more on strategic planning and higher-level initiatives.

It’s also a pathway for future leaders. By rotating responsibilities, you’re not only supporting the current team but also preparing the next generation of tech leads and engineering managers. And yes, one of the side benefits is that, as they grow, you’ll have more time to focus on broader goals, knowing your team is empowered and dependable.

I hope this approach brings as much value to your team as it has to mine. If you’ve tried something similar or have insights to share, I’d love to hear them—let’s keep the conversation going on how we can best support and grow our teams.

A leader’s decision is the most valuable artifact they can contribute on behalf of the team. Shared thoughtfully, it can make or break a team’s success. As leaders, we should be deeply invested in the process of producing these decisions—not just in the outcomes but in how we arrive at them and communicate them.

One of the greatest responsibilities and honours, you have as a leader is making decisions. At some point in your career, you’ve proven a track record of good decisions, coupled with the ability to quickly course-correct and learn from the not-so-good ones. This earned you the trust of your organization, granting you more say in the critical paths, major projects, and strategic initiatives that shape its future.

But decision-making isn’t simply about choosing outcomes. It’s a process that deserves careful attention and structure, especially as the choices multiply. Let’s break down decision-making into practical steps: What types of decisions are there? Which frameworks or mental patterns can help us with each? And how much time, effort, or data should we invest in each type? These questions matter because, as leaders, we’re faced with a relentless stream of decisions, big and small, every day.

Reversible vs. Irreversible Decisions

The first key distinction is between reversible and difficult-to-reverse decisions. This question sets the foundation for how you approach any choice. For reversible decisions, you can afford more flexibility, encouraging swift progress and embracing an iterative approach. If the decision turns out wrong, you can pivot with minimal cost.

However, if the decision has lasting implications, you need to take a more deliberate approach. Gather insights, consult your team, and carefully consider long-term consequences. Remember, though, that even high-stakes decisions should not linger unnecessarily, as indecision can harm progress and morale.

Assessing Urgency and Timing

Next, assess the urgency: Is an immediate decision necessary, or does waiting serve as a strategic move? In many cases, waiting can yield new insights that make the path forward clearer. Yet, there are situations where acting quickly brings greater advantages, helping you maintain momentum and prevent the team from getting bogged down in analysis paralysis. Striking this balance is essential—moving too fast may result in oversights, while moving too slow could mean missed opportunities.

Importance and Downstream Impact

The simplest starting point in decision analysis is determining the level of importance and downstream impact. For minor, inconsequential items, a quick, instinctual choice might suffice. But if the decision involves irreversible steps or a significant investment of resources, take a pause. Again, ask yourself if more data might emerge or needs to be sought, or if you already have everything you’re ever going to get. Lingering too long can become a bottleneck, fostering procrastination and preventing your team from taking bold, decisive action.

When Your Team is Split

Often, you’ll encounter situations where your team is divided, with strong opinions on both sides. When no natural consensus emerges, the role of the leader is to step in and make the call with clarity and confidence. To do so effectively, communicate openly about the information you’ve gathered, and walk your team through your thought process.

In these cases, the specific choice you make often matters less than the transparency you show in weighing all sides and explaining your rationale. A team doesn’t need unanimous agreement to thrive. It simply needs clarity, a sense of direction, and the trust that open communication was respected throughout the process. In practice, it’s often healthier for teams to embrace a “test-and-learn” mindset rather than rigid, top-down directives.

The Collective Weight of Decisions

Ultimately, a team’s success hinges on the cumulative impact of its decisions. Focusing on the process of decision-making—not just the decisions themselves—is crucial. A decision by a leader, when shared transparently, becomes a valuable artifact for the team’s success. Obsessing over this process refining this as you primary craft as a leader can be the defining factor that shapes a team’s trajectory.

So far, we’ve explored some foundational considerations for making thoughtful choices. In future posts, I’ll dive into various methods and techniques to enhance team decision-making. From basic pro-con lists and weighted matrices to creative approaches like Six Thinking Hats, these tools can help teams stay organized, objective, and collaborative, minimizing ego-driven pitfalls along the way.

Until then, remember: your decisions shape not only your future but the entire team’s trajectory. Embrace the process, foster clarity, and build a foundation for intentional progress with each choice you make together.

Leaving the corporate world behind is both exhilarating and daunting. In late June 2024, I made the hard decision to step away from my role as an Engineering Leader at Cisco. My goal? To dive headfirst and hands-on into the world of artificial intelligence and independently build a SaaS product from scratch.This is the story of how I brought sitereviewdesk.ai to life in just 50 days.I share a sprint retrospective towards the bottom of this blog.Share on: LinkedIn

The Need for Speed: Shifting from Corporate to Lean Execution

In the corporate environment, I found myself spending 80% or more of my time on meetings, status updates, and endless planning sessions. While coordination is essential in large organizations as a leader, it often leaves little room for actual personal tangible execution. I craved the agility of immediate decision-making and the thrill of rapid development.I aimed to invert my daily ratio to an extreme of 90% execution and 10% planning. This approach was inspired by the military's 2/3rd rule: spend one-third of the time planning and allocate the remaining two-thirds to execution. As an independent developer, this was not just possible—it was imperative. My challenge to myself and goal was to maximize learning and building with what I had left of summer 2024. I had planned at the time to re-evaluate in late September on next-steps for me -- so that was my personal "deadline".

Hands-On Learning: The Best Teacher

While I began with some courses from DeepLearning.ai, I have always preferred and know myself that I resonated more with hands-on application. That always seemed to stick better with me as I get into my 3rd decade of my career. For me at least, building, tinkering, and even stumbling along the way provided insights that no lecture could offer. I believe that real understanding comes from doing, not just listening and trying to absorb an inventory of theory and knowledge that I might or might not use later.

The Birth of SiteReviewDesk.ai

I started jotting down AI-based startup ideas that were both fun and potentially impactful. I wanted to solve real problems, even if they were old issues that could benefit from new solutions. That's when the idea for sitereviewdesk.ai crystallized—a service that automates website reviews using AI, providing deep insights and recommendations for better engagement.

50-Day Retrospective

What Went Well

• Morning Stand-ups: I began each day with a 10-minute personal stand-up meeting. This practice helped me jot-down top priorities, move previous day missed tasks and goals to today if it made sense, and adjust to any new developments overnight quickly.
• Prioritizing Impact: Focusing on big-impact tasks over minor distractions kept the project on track. It’s easy to get lost in the weeds; staying focused on the core functionality was key.
• Daily Commits: Ending each day with a final commit to the main branch created a satisfying sense of progress and ensured that nothing was left hanging. Each day's batch of edits and rabbit holes can get gnarly, but just like a relationship with a spouse -- try to never go to bed upset or leaving things messy :).
• Establishing an AI Project Masterplan.md: Something I picked up from Code with Brandon's template here was invaluable as a way to build and maintain a sort of master project plan that you can maintain and give to any LLM for context on your project. This is so you don't have to re-explain to LLMs over and over again what exactly you're doing and the context. I just put this file in my Anthropic project file cache for example, or kept pointing to it in Cursor/VSCode for the LLMs to read first as a primer before answering and working on my code.
• Optimizing AI Tools: Making it a good habit to keep updating these system/agent prompt engineering and context documents frequently was good hygiene and significantly improved the efficiency using AI development tools. Files like the masterplan.md file, a db schema description file, project file folder structure explainer and README.md for the repo were key. This all helped reduced the time spent on iterative messaging the LLMs and increased the quality of their outputs.
• Choosing the Right AI Tools: I found that Cursor outperformed VS Code with the Continue extension for my needs. Additionally, Ollama was fantastic for experimenting with different models locally without worrying about API costs. During development I probably did 80% of LLM API calls using Ollama (Llama 3.1) and 20% on production paid models Gemini, GPT 4O, Sonnet 3.5 etc..

Challenges Faced

• Tool Limitations: While using Anthropic's Project feature, I encountered issues with updating files. The inability to replace files with the same name led to confusion about which version the AI was referencing. I notified Anthropic about this key functionality miss btw. Maybe others have too!
• Platform Complexity: Running everything on Google Firebase and GCP was more convoluted than expected. The separate admin consoles and scattered documentation made navigation and troubleshooting time-consuming.
• Documentation Woes: Google's documentation was less user-friendly than I had hoped. I often resorted to using language models to find answers, which isn't ideal when you're deep in development.

Lessons Learned

• Avoid Manual Copy-Pasting: Early on, I wasted time manually transferring code snippets from AI chat windows. F**k that -- don't be like me and do that. Switching to Cursor streamlined this process, integrating AI suggestions directly into my codebase. That's one of the things they forked and implemented into their core editor with better fuzzy logic to inject lines of code more accurately. Continue.dev with the limitations of being a VS Code extension didn't do as smooth of a job with this. I haven't tried and done the latest track test with VS Code's latest releases to try and compete with Cursor on this.
• Select the Right Models: General-purpose models like Llama 3.1 didn't meet my coding needs. Specialized fine-tuned models like Codestral and paid models like GPT-4.0, and especially Claude 3.5 Sonnet, provided better coding performance.
• Tool Efficacy Matters: Cursor's intuitive integration of AI suggestions into live code made it superior to alternatives like Continue.dev, which was hit-or-miss in its effectiveness. (But I did miss the "/<custom_command>" function from Continue for common prompts you want to use with the LLM window – Cursor should add that in!)

Reflecting on the Journey

Looking back, the experience was everything I hoped it would be. Of course, there were lots of expected challenges and learnings, but they were just minor setbacks and actually valuable lessons that contributed to both personal and professional growth. While, I am certain I could have spent more time on upfront market research with this particular product, I believe that building something meaningful sometimes requires taking that leap of faith.

Moving Forward: What's Next?

As I continue to iterate on sitereviewdesk.ai, I'm diving into the realms of marketing and user acquisition—a whole new world of learning and set of challenges. But that's the beauty of this journey. Every step opens up new avenues for learning and growth.If you're a software engineer looking to pivot, or someone interested in AI and rapid product development, I hope my experiences offer some valuable insights. Let's keep pushing the boundaries of what's possible.Share on: LinkedInThanks for reading! Feel free to share your thoughts or ask any questions in the comments below.

As a software engineer with over 20 years of experience in the tech industry, I've learned that one of the most valuable skills for saving time and boosting productivity is the ability to manipulate text efficiently and quickly.This skill is often underestimated how much ROI in time this amounts to over the years for a engineer who lives in an IDE or text-editor all day.

Today, I want to share just one of my favourite powerful techniques using Visual Studio Code: multi-occurrence selection with Cmd+D and Cmd+F2. This skill can make your coding workflow smoother and more efficient.The Power of Multi-Occurrence SelectionMulti-occurrence selection allows you to select and edit multiple instances of text simultaneously. This feature is incredibly useful when you need to make repetitive changes across your codebase. Whether you're converting brackets to parentheses or reformatting text into CSV, multi-occurrence selection can save you significant time and effort.Watch the 2-minute Full Tutorial:I demonstrate multi-occurrence selection in action. Don't forget to like, comment, and subscribe for more coding tips and tutorials!

I'm excited to share a new milestone in our journey of exploring the vast world of AI and this sharing back to the community!As you know, my mission with AlvoRithm is to share my experiences around building with AI and products around AI and share with everyone. Today, I'm thrilled to announce the release of my first AlvoRithm channel's YouTube tutorial: "Run AI Models Locally: Install & Use Ollama for Free AI Power!"

Why This Video?

In the fast-paced world of AI development, the cost of running powerful models can be prohibitive. Many developers, especially those just starting, are looking for ways to experiment with large language models without breaking the bank and not risk leaking any sensitive data to the cloud and online providers. This video addresses that need by introducing you to Ollama, an open-source project designed to run AI models locally on your laptop or PC.

What You'll Learn

In this comprehensive tutorial, I guide you through the entire process of getting Ollama up and running. Here’s a sneak peek of what you’ll learn:

• Downloading and Installing Ollama: Step-by-step instructions to get you started quickly and efficiently.
• Setting Up AI Models: How to configure Ollama to run on your laptop or desktop
• Using Ollama's Command Line and RESTful API: Making the most out of Ollama's powerful features.
• Integrating with VS Code: Enhance your coding experience with AI by integrating Ollama into your development environment.

Why Ollama?

Ollama is a game-changer for anyone looking to delve into AI development. It’s a wrapper around the open-source Llama.cpp project, designed to simplify the installation and operation of large language models on local machines. Whether you’re a seasoned developer or a newcomer, Ollama is a straight forward a cost-effective and powerful way to explore AI and run different models.

Practical Applications

In the video, I demonstrate a practical application of Ollama, starting with a basic model setup and integration with coding tools like VSCode via a Continue.dev plugin. You’ll see how easy it is to have a local AI assistant that can help with coding and more just like if you were pair programming with a really smart engineer and fast typer!. The flexibility of Ollama allows you to experiment with different models and find a ton of other plugins and tools out there that can integrate and leverage it via the easy localhost port 11434 RESTFul API!

Join the Conversation

I’m eager to hear your thoughts and experiences with Ollama. Have you tried other open-source AI model running platforms and tools from HuggingFace or elsewhere? How do you plan to integrate AI into your projects? Share your insights and questions in the comments section of the video or right here on the blog.

Watch the Video

Link to watch should be at the top of this blog post or here again. Don’t forget to "like, subscribe, and hit the notification bell" to stay updated with the latest AI tutorials and insights from my journeys.Thank you for being part of the AlvoRithm community. Together, we can unlock the true potential of AI and bring its practical benefits to everyone.Stay curious and keep innovating!Best, AlvinP.s. Want to help and also shape the content I should make? PLEASE share your ideas and thoughts on the video comments or on my LinkedIn: https://www.linkedin.com/in/alvinswong/Share on: LinkedIn

Picture this: there I was, comfortably nestled in an engineering management role at Cisco, a legendary tech giant with an amazing benefits and compensation package. Life was good, right? Well, it was... but if you're anything like me, an engineer at heart, something was missing over time. That spark, that fire in my belly that made me fall in love with tech 20+ years ago.So, I did what any rational person would do. I quit my job. 😅Crazy? Maybe. Exciting? Absolutely! Let's talk about it...(Thanks for reading! 😊 I share all this openly with the hope that it helps you with your life and pursuits, both in work and your passion for your craft. May it offer at least one tech industry colleague's experience for your consideration.)Share on LinkedIn

A Leap of Faith

I worked at Cisco for about a decade since the acquisition of OpenDNS in 2015 - the hot security startup I had joined back then. Over the years, I gathered a ton of experience across several teams and roles, including Security Engineer, Network Engineer, Software Engineer, Technical Lead, and Senior Tech Lead.As I gained more seniority and leadership experience, I naturally moved into leadership roles and became part of the senior levels of Engineering Management, stepping in wherever our business needed me. I was fortunate to join, start, hire, and lead teams, working with a ton of smart, awesome people, and together we delivered on some impactful projects.My career in a big tech giant was going well, and the momentum of the business cycles was fulfilling. But deep down, perhaps like some of you in the industry reading this blog, I gradually found it more difficult to extricate myself from necessary but lengthy corporate processes, meetings, and management tasks. I longed to spend personal time on immediate hands-on exploration and building things directly.I loved my team, and fostering their teamwork and growth is something I will cherish forever. However, what was best for the team often trumped my desire to spend time coding and building directly. As it should, and I would pick them over me any day of the week.With my deep passion and obsession with the AI/ML explosion, I came to a realization. I needed a change to follow my heart and pursue more exploration into AI/ML adoption. I wanted to learn and develop directly, something I had been obsessed about lately.After discussing with my family and ensuring I could survive for several months, I made a hard decision and took a leap of faith. I decided to swing the pendulum back to being hands-on by taking 3-6 months away from a traditional "day job" to learn everything I could about AI/ML. I aimed to understand how to work with it, how to code with it, how to develop content and business strategies with it, and ultimately how to build a startup with it.Yes, call me crazy 😜, but I'm simultaneously juggling studying, coding, and building while maintaining my business and leadership skills through a solo-preneur startup project. Let's see how far and fast AI can take us as a force multiplier! 🚀(Spoiler alert: It's only been 3 weeks, and I've never been more productive, excited, and focused. Working long and hard with new tooling and tech, co-developing and brainstorming with LLMs, this is a huge upgrade in personal satisfaction. Life's good 😊.)

Discovering AlvoRithm

During this transition, I felt I needed a new face and brand to reinvent myself. I've decided on the AlvoRithm. AlvoRithm will be a personal brand dedicated to sharing my journey, insights, and discoveries in AI. It’s a play on words, combining my passions for music production, video content creation, and more. AlvoRithm is not just a platform for documenting my experiences; it’s also a space where I aim to inspire and educate others who are passionate about technology and creativity.AlvoRithm's mission is to bridge the gap between AI theory and practical application, providing valuable insights to software developers, tech professionals, aspiring engineers, and anyone interested in the future of technology. Through blogs, vlogs, and social media, I share weekly updates in a Sprint retrospective style, highlighting what went well, what I learned, and areas for improvement.

Learning and Growing

My journey into AI has been incredibly enriching over the last three weeks. I'm currently diving deep into Deep Learning Specialization courses from Coursera with Andrew Ng from Stanford University. These courses provide a solid theoretical foundation and practical skills essential for navigating the AI landscape.In parallel, I'm working on a startup idea that leverages AI to create innovative solutions. This hands-on project allows me to experiment with the latest LLM models, cutting-edge techniques, and applications for software development. It's an exhilarating process that combines creativity, technical expertise, and a passion for problem-solving.

Sharing Knowledge

One of my core beliefs is that knowledge should be shared. Through AlvoRithm, I aim to distill complex AI concepts into easily digestible content. My goal is to save you time and provide you with the most valuable insights from a seasoned tech industry professional.I can start with going over what I believe every tech enthusiast should explore in order:

1. Conversational AI: Engage with chat models like OpenAI's GPT-4 or Anthropic's Claude.
2. Image Generation: Experiment with tools like DALL-E, Midjourney for generating images or equivalent.
3. Foundational Concepts: Understand key AI terms and concepts (e.g. LLMs, Supervised, Unsupervised, Parameters, Quantization, Fine-Tuning, context-windows, temperature, RAG, multi-modal, agents.
4. Coding Assistants: Integrate the latest code workflow enhancing tools (e.g. Github CoPilot, Agentic Frameworks like Crew.ai or Autogen).
5. Local Hosting: Explore local LLM hosting alternatives and open-source models.
6. Popular Models: Try out various open-source models (e.g. LLaMA 3, Mistral, Gemma 2) vs paid models (ChatGPT, Claude)

Looking Ahead

As I continue this exciting journey, I'm committed to launching at least one new startup around September, centered around an AI-based application I'm passionate about and I'll be using AI itself to help accelerate and implement the service. AlvoRithm will be the hub where I share every step of this journey, offering insights, lessons learned, and inspiration to my audience.

Call to Action

If you're intrigued by my journey and want to stay updated and keep in touch on the latest in AI, tech, and creative content, I invite you to follow me:- LinkedIn: https://www.linkedin.com/in/alvinswong/- YouTube: AlvoRithm - YouTube channel - X.com (Twitter) - @theAlvoRithmLet's explore together!