DEV Community: Sanel

Hey Siri: Update Siri; Activate ChatGPT with Siri

Sanel — Thu, 18 Jan 2024 16:20:04 +0000

Hey Dev.to community!

I hope you're all doing great! Today, I'm here to share a nifty trick for boosting productivity: activating ChatGPT with Siri.

Or more eloquently put: Replacing Siri for all your questioning needs! It's about time to Update Siri ourselves!

As a software architect running my own business, efficiency is the name of the game, and this combo has been a game-changer for me.
And between you and me, it's surprising that Siri didn't get this upgrade sooner. We've been waiting for it like Apple CEO Tim Cook took a long lunch break. Hah-hah-hah. insert snooze emoji

The Solution Is Here

Important Note: This tutorial is tailored for iPhone users running the iOS operating system with the Siri voice assistant. Devices running alternative operating systems or featuring different voice assistants might have their unique tricks. This tutorial may not be applicable in those cases.

0. Install ChatGPT (The Official version by OpenAI on App Store: BEWARE FAKES)

1. Shortcut Magic

Head to your Siri Shortcuts ("Hey Siri open Shortcuts") app and add ChatGPT with a "start voice conversation" prompt to your library. Customize the phrase to something memorable – I went with "Update Siri." Because I find it terribly funny.

Author note: You can also use the default built-in command "Hey Siri Ask ChatGPT"

2. Invoke the Power

Now, whenever you need your virtual assistant (read: ChatGPT), say your chosen trigger phrase to Siri. For me, it's "Siri, Update Siri."

3. Ask Away:

Once Siri recognizes your prompt, ChatGPT springs into action. Ask any burning questions or seek insights on your latest coding challenge. Siri will not only send your inquiry to ChatGPT but will also read out the response loud and clear.

Autor note: Alternatively, you can make a custom shortcut that opens a direct voice conversation with ChatGPT - Pending a phone unlock.

4. Chat Aloud, Learn, Inquire:

Siri's old tricks of leaving you in the dark, struggling with basics, and playing the silent treatment are so last season. Enter ChatGPT – your upgraded assistant, the genius Siri wishes it could be. ChatGPT takes the wheel.

Stay sharp, stay curious!

Cheers,
S3
Passionate About Updating Siri

Dev.To Disclaimer. This post has been in some part, to some degree intelligently composed and refined with the assistance of AI or LLM technology. It in no way replaces or undermines the creative prowess of the original author, but merely assists in finding a common voice and formatting that is friendly for all readers

Embracing Simplicity: The Pitfalls of Obscure Complexity in Programming

Sanel — Thu, 18 Jan 2024 00:49:57 +0000

Introduction

In the ever-evolving landscape of software development, one persistent challenge stands out—the tendency for developers and small developer communities to segregate through obscurity, inadvertently introducing redundant complexities into their projects. While it's understandable that the desire for innovation and uniqueness drives developers, there is a growing concern that these pursuits often lead to convoluted codebases and a lack of accessibility. This blog post advocates for a shift towards smarter programming, emphasizing that more complexity does not necessarily mean better code. In fact, the mantra "MORE is truly LESS" should be at the forefront of our minds as we navigate the intricate world of software development.

The Obsession with Obscure Complexity

In the pursuit of creating something distinctive, developers sometimes fall into the trap of adding layers of complexity that serve little purpose. Obscure coding practices, unconventional frameworks, and unique methodologies can lead to projects that are hard to understand and maintain. What starts as an attempt to stand out can end up isolating developers and creating barriers for collaboration.

The Mistake of Mistakes

While it's essential to acknowledge that mistakes are a natural part of the learning process, it becomes problematic when these mistakes are perpetuated and celebrated within a community. Mistakes in coding, when not rectified, can become embedded in the codebase and lead to a culture of accepting bad practices. This environment, fueled by obscure complexity, can drive away learners who struggle to navigate convoluted codebases.

Advocating for Smarter Programming

Simplicity as a Virtue:
Embrace simplicity as a virtue in software development. Clear, straightforward code is not only easier to understand but also facilitates collaboration and maintenance. Prioritize readability over complexity.
Learning from Mistakes:
It's crucial to learn from mistakes, both individual and collective. Encourage a culture of continuous improvement, where developers can openly discuss and address coding errors. Mistakes are valuable opportunities for growth when approached with a mindset of learning and improvement.
Collaboration and Community:
Foster a collaborative environment where developers can share insights, best practices, and challenges. Small developer communities can benefit greatly from pooling their collective knowledge and experiences.
Balancing Uniqueness and Pragmatism:
Strive for a balance between uniqueness and pragmatism. Innovative solutions are commendable, but they should not compromise the fundamental principles of maintainability and accessibility.

Conclusion

In the programming community, the adage "MORE is truly LESS" resonates profoundly. It serves as a reminder that excessive complexity, obscure practices, and the celebration of bad code can hinder progress and drive away aspiring developers. By advocating for smarter programming—emphasizing simplicity, learning from mistakes, fostering collaboration, and striking a balance between uniqueness and pragmatism—we can contribute to a more inclusive and vibrant programming community. Let's build a future where the beauty of code lies in its clarity and the elegance of its simplicity.

What real-life example have you encountered with that made you frustrated? Your voice matters and it's more important than you think. Voice your concerns and tag me on Twitter!

Thanks for reading!

Post contents 100% views and original thoughts of the Author

dev.to disclaimer: Leveraging LLM's or "AI" is a great way to share and connect. I believe that AI-generated content should not be discriminated against or even observed. It has great limitations, but it serves the user by indulging them in the simple process of creation.

For more clarity read these guidelines here

An Unfiltered Journey Through Contentlayer: Windows Woes, JS Hiccups, and Advocating for Developer Zen

Sanel — Fri, 05 Jan 2024 15:30:10 +0000

Hey Dev Fam,

In the sprawling universe of web development, I recently took a detour into the realm of Contentlayer. As a seasoned Software Designer and Engineer at GCS, I'm all about crafting robust web applications and systems. However, my recent rendezvous with Contentlayer, especially as a Windows aficionado, left me with a mix of head-scratching and eyebrow-raising moments.

Navigating the Windows Maze

So, here I am, diving into Contentlayer, excited about seamlessly integrating markdown files into the frontend. But guess what? Windows compatibility plays hard to get. The setup process felt like a labyrinth, filled with bugs and glitches that made me question my life choices.

The Need for Speed – Or Lack Thereof

Contentlayer, coded in JavaScript, prides itself on being the go-to package. But let's talk real talk – the performance? Not exactly a speed demon. In a world where every millisecond counts, this tool's sluggish dance left me wondering if I accidentally stepped into a time warp.

MDX Musings

Now, MDX is supposed to be the rockstar here – Markdown meets JSX. Cool, right? Well, Contentlayer's take on it might not be everyone's cup of code. The lack of a smooth developer experience raised an eyebrow or two. As someone who values efficiency, the MDX abstraction felt like a detour, not the scenic route I was hoping for. Even if used as a low-level SDK, the maintenance for it would not be something reasonable.

Rallying Cry for Improvement

As a seasoned web warrior, my encounter with Contentlayer sparked more than a few thoughts. It's crucial for us, the devs in the trenches, to speak up. Let's create a culture where feedback is our superpower. Contentlayer might have stumbled, but hey, there's always room for improvement. Let's not just code; let's code better.

Vercel's Starter Blog Template: Not Quite Love at First Byte

Oh, did I mention this whole adventure unfolded within Vercel's starter blog template? Yeah, the implementation – not a masterpiece. Even us seasoned architects can be left scratching our heads when faced with less-than-stellar tools on even the most reputable platforms.

In Closing – Code Hard, Code Smart

So, my dive into Contentlayer had its fair share of hurdles. From Windows woes to performance hiccups, it wasn't the smooth ride I anticipated. As we navigate the dev galaxy, let's be discerning about the tools we adopt. Through our unique experiences and voices, we shape an ecosystem that thrives on innovation, accessibility, and a shared commitment to excellence. My personal alternative would be good old JSON files with a simple Markdown parser. This "Content" layer is 2 steps too far for my comfort!

Keep coding hard, but always code smart!

Cheers,

Sanel, the Web Architect Extraordinaire at GCS 👨‍💻✨

🚀 Finding Harmony in Web Development: Next.js, Vercel, Angular, Svelte, and Beyond! 🌐

Sanel — Thu, 04 Jan 2024 20:22:02 +0000

Navigating Web Development: Embracing Harmony in Tech Dominance

In the dynamic world of web development, the push for dominance by platforms like Next.js and Vercel sparks concerns about power concentration. While their ambition is commendable, a singular force dictating standards isn't ideal for a thriving ecosystem.

Enter Angular and Svelte – two formidable contenders playing vital roles in maintaining balance and preventing monopolization. Competition, as seen between Next.js, Vercel, Angular, and Svelte, fuels innovation and prevents unilateral industry control. Acknowledging Next.js and Vercel's contributions, a balanced and diverse tech ecosystem benefits everyone.

In the tech realm, Next.js and Vercel aim for dominance but balance matters. Angular and Svelte, as key players, keep things in check. Collective growth trumps concentration of power. Atlantean visions promote collaborative strength: Less monopoly, more harmony for a thriving tech ecosystem.

Even though I firmly believe Next.js and Vercel outshine the rest, only through communal continuance can we ensure their sustained success. The web development community's strength lies in collaboration, knowledge-sharing, and shaping the future together. This perspective, grounded in fairness and unity, beckons a resilient and thriving ecosystem.

Leave a comment if you want to learn more about this dynamic landscape and the tools shaping our digital future. Or if you want to know more about why I think Next.js and Vercel are something you should take a good look at!

Thanks for reading. - S3