
## Preamble

---

In recent years, we've witnessed an accelerating integration of AI technologies into tools we use daily—everything from grammar correction tools like Grammarly to driving business strategies and decision-making. While this shift has made our work more efficient and streamlined, it also raises an important question: What are we losing in the process?

## The AI Takeover in Social Platforms

---

Consider social media platforms like LinkedIn. These spaces, once used to showcase our achievements and personalities, are now adapting AI tools that assist in how we present ourselves. AI-generated writing suggestions, profile insights, and even engagement strategies are becoming the norm. On the surface, these tools seem like a great way to polish our profiles and enhance our online presence. But what happens when we allow AI to shape the very way we represent ourselves?
By relying heavily on AI for content generation and recommendations, we risk losing the imperfections that make us human. Those quirks and individual characteristics that define who we are—whether it's an unconventional turn of phrase or a unique way of storytelling—are slowly being sanded down. Large language models are designed to optimise and refine, but they can never truly replicate the depth of context that shapes our individuality.

## Social Media and Self-Presentation

---

To give you a sense of just how significant this issue is, consider that as of 2023, over five billion people were using social media worldwide. That's over 60% of the world's population! Of these users, a majority report that they use social media to craft a specific narrative about their lives—whether for professional purposes like on LinkedIn or more casual self-presentation on platforms like Instagram, X (AKA Twitter) and Facebook (Statista, 2023). As AI continues to be integrated into these platforms, we should be mindful of how this technology shapes the stories we tell.

## A Subtle Erosion of Humility?

---

I'm not against the use of AI. In fact, I believe it's an inevitable part of our future, and it can offer tremendous benefits when used wisely. But there's a subtle but important distinction to be made. In many cases, AI strips away the rough edges, individualism, and the little nuances of human error or imperfection that reflect who we really are.

Take Grammarly, for instance. It provides users with an option to "acknowledge" when content is AI-assisted. This level of transparency allows the user to make an informed decision about their work. However, many of the large social platforms we use daily, like LinkedIn or Facebook, do not offer such transparency when AI is used to tweak or even generate content. As these platforms quietly integrate AI, we unknowingly start to conform to what the algorithm deems "best practice," potentially losing the uniqueness of our self-presentation.

## The Accessibility of Software Development and Its Risks

---

Beyond the way AI is affecting self-presentation, it's also reshaping technology and the software development behind it. AI-assisted tools, such as GitHub's Copilot and AI-driven no-code platforms, have made it easier than ever for people who don't traditionally see themselves as developers to produce content like websites, apps, and even video games. In 2022 alone, GitHub reported that over 1.2 million developers used its Copilot feature within its first year of release, and the no-code market is expected to reach a value of $45.5 billion by 2025 [Source](https://www.statista.com/statistics/1226179/low-code-development-platform-market-revenue-global/). This growing trend of AI-driven, self-taught software creation is opening the doors to a more diverse group of creators. On one hand, it's exciting to see more people acquiring programming skills and trying their hand at development.
However, I feel there is also a downside to this increased accessibility. Many of these new developers, while entrepreneurial, creative, and enthusiastic, may lack the foundational understanding of security, scalability, and best practices that traditionally come with formal education or years of experience. As a result, we could see an influx of poorly implemented, insecure, and unsustainable solutions entering the tech landscape.
Despite these challenges, the potential for innovation and creativity is vast. By addressing these concerns and providing support and education, we can ensure that this democratization of software development leads to a more inclusive, secure, and sustainable tech ecosystem.

### Risks to Security and Scalability

---

Using AI-generated code without experience may lead to overlooking common security vulnerabilities like SQL injection, cross-site scripting, or improper authentication flows. The 2023 Verizon Data Breach Investigations Report (DBIR) reveals that approximately 68% of security breaches can be linked to code vulnerabilities (Verizon DBIR 2023). When inexperienced users rely on AI to generate large amounts of code, these risks are heightened. While AI can provide fast solutions for building scalable systems, it's essential to consider the broader context and long-term performance to avoid incurring costly technical debt.

The increasing popularity of AI-assisted software development tools has made development more accessible, yet we must remain vigilant about potential risks. Inexperienced developers may inadvertently introduce vulnerabilities or inefficiencies into their code, posing security and performance risks in the future. The tech industry may face a surge of quick fixes and "good enough" solutions that fall short of the high standards needed for robust and reliable software.

By recognizing these challenges and addressing them proactively, we can harness the power of AI in software development while mitigating potential pitfalls. With the right guidance and awareness, developers can leverage AI to create secure, efficient, and resilient software solutions that meet the highest standards of quality and performance.

## Solutions for Responsible AI Usage

---

As AI-assisted development grows, it's important for new developers to continue learning and developing their skills beyond the tools they're using. AI can be a powerful enabler, but it can't replace the need for a deeper understanding of the software development lifecycle and the complexities that come with building secure and scalable solutions.

1. Commit to Lifelong Learning: AI can help streamline many aspects of software development, but there's no substitute for learning the fundamentals. New developers should focus on understanding key principles of secure coding, architecture, and best practices.
2. Utilise AI with Transparency: When using AI-driven tools, transparency is key. Just as Grammarly prompts and allows users to acknowledge AI involvement, other platforms should consider providing clear indications when content is AI-generated, giving users the chance to review, learn, and take responsibility for the output. Platforms can ensure transparency when AI is used to tweak or generate content by clearly labelling AI-assisted content, implementing detailed disclosure protocols, offering users the option to opt out of AI-generated suggestions, and engaging in ongoing dialogue with their user communities to adjust transparency and labelling practices accordingly.
3. Promote Best Practices: AI platforms should integrate educational prompts that help users learn best practices in real-time. For instance, GitHub Copilot could include explanations about why certain code suggestions might be more secure or performant, helping developers understand the "why" behind the suggestions.
4. Understand that Large Langage Models (LLM) Platforms are not Knowledge models: Large Language Models (LLMs) like GPT are powerful tools for generating human-like text. Trained on vast datasets, they can produce impressive outputs. However, it's important to remember that LLMs are not knowledge models. They lack true understanding and cannot verify the accuracy of the information they generate. While they can be valuable for creating content, their outputs should be critically assessed and fact-checked. It's crucial to use them with human oversight to mitigate the risk of misinformation and biases.

## The Bigger Picture: A Cautionary Note

---

AI is reshaping our interactions with technology and each other. While these advancements offer convenience, it's essential to approach them mindfully. Human individuality is immeasurable, these models and algorithms cannot fully encapsulate what makes us unique. Let's focus on how to best utilize AI thoughtfully, preserving the human connection that defines us.

## Call to Action

---

AI is an integral part of our lives, but it's important to remember the human touch. Whether using AI for writing, coding, business, or social media, pause and evaluate the outcomes. Ask: Does this reflect my essence? Is it secure and scalable? View AI as a resource, not a dependency, and use the extra time it provides to invest in skills, creativity, and uniqueness. Embrace the opportunities it brings while maintaining our humanity.

## References

---

1. Verizon 2024 Data Breach Investigations Report: [https://www.verizon.com/business/resources/reports/dbir/](https://www.verizon.com/business/resources/reports/dbir/)
2. Statista, Number of Worldwide Social Network Users: [https://www.statista.com/statistics/278414/number-of-worldwide-social-network-users/](https://www.statista.com/statistics/278414/number-of-worldwide-social-network-users/)
3. Statista, Low-code development platform market revenue worldwide from 2018 to 2024: [https://www.statista.com/statistics/1226179/](https://www.statista.com/statistics/1226179/low-code-development-platform-market-revenue-global/)
4. LinkedIn, Enhance your profile with LinkedIn’s AI-powered writing assistant: [https://www.linkedin.com/help/linkedin/answer/a1444194](https://www.linkedin.com/help/linkedin/answer/a1444194)
5. Astronort, Astronort: Why now?: [https://www.astronort.com/articles/astronort-why-now](https://www.astronort.com/articles/astronort-why-now)

## AI Acknowledgement

---

This article was developed using a combination of personal insights and AI assistance via OpenAI's ChatGPT. Specific prompts used included topics such as "AI and human interaction in social platforms," "impact of low-code/no-code on software development," and "statistics on social media usage." ChatGPT provided suggestions on refining the arguments, organising sections, and adding credible references. While AI facilitated research and suggestions, the opinions and conclusions expressed here are my own.

To help my writing process, I used these Grammarly AI prompts:

Prompts created by Grammarly

- "Identify any gaps"
- "Shorten it"

Prompts I wrote

- "expand on my ideas around how platforms ensure transparency when AI is used to tweak or generate content? "


The Rise of AI in Everyday Tools: Are We Losing Our Humility?


## In Progress

---

Decks of the Hunter is a working title for my next book.

I have set myself a goal for this book to write over 300 pages. I really want to dive more into the ideas around some elements of the first book, and really flesh out the world and characters of Lovecraftian 1920s New Zealand.

You can buy [The Dark that Dwells Beneath Te Aro](https://www.amazon.com/Dark-that-Dwells-Beneath-Aro/dp/B09JVFJKFX/) on Amazon. Please consider leaving a review on amazon, it will help toward my next novel currently in progress.


Decks of the Hunter


## Preamble

---

As part of my weekly routine, Monday's at 7:30pm NZT I sit down to watch Twitch for a couple of hours of Dungeons and Dragons from a local D&D crew.
Hosted by an old collegue of mine, [Getting Dicey](https://twitch.tv/gettingdicey) is alot of fun. Just, a bunch of kiwis having a laugh after work.

The Twitch stream has been rather successful over the last 3 years, gaining over 900 followers, with plenty of regulars and subscribers tuning in every Monday from around the world (_waves_ to Kyosti).

## The Idea

---

Host and Dungeon Master (whom I'll call our Product Owner) had a desire to introduce something to the channel, something that users could participate and engage with while on stream, but without them having commit to paying with real money.

There are a few ways viewers can support Twitch streamers, either following the channel, which is free, or paid methods such as Subscribing or buying and giving the channel 'Bits', a digital currency on the platform where you can buy a bundled amount and share with any channel you are watching with the click of a button.

Twitch released a few years ago another support method, Channel Points. These accumulate beneath the chat (twitch viewers can interact with Streamers via chat messaging as well), as you watch the stream, you are awarded roughly 30 points per 15 minutes. Viewers can, like Bits, select an option below the chat to spend their Channel Points on various rewards curated by the broadcaster.

## Could I do it?

---

The first thing I did was sit down and take a look at Twitch's developer docs. After about 2 hours of looking over the documentation, it did appear to have a very extensive [Rest Api](https://dev.twitch.tv/docs/api/).

The Product Owner and I had a chat on the community discord, so they could brief me on the idea, I then broke it down into a simpler user story.

> As a Viewer
>
> I want to spend Twitch Channel Points to unlock a random getting dicey trading card
>
> So that I can collect and view them

From here I could break down the objectives...But before I open an editor, more research was needed. I knew [Twitch Extensions](https://dev.twitch.tv/docs/extensions) existed, I knew there was a developer community out there, and I hadn't written any code in a very long time...

## Presentation Proof of Concept

---

I wanted to learn a few things with the proof of concept:

- React.js
- Displaying _n_ number of cards nicely and intutively

My gut estimate was this was going to take 3 weekends of schedule, roughly spending 2 hours each day, and my lovely wife would take the kids out for a couple of Saturdays so I could spend roughly 3 to 6 hours each weekend. That was my goal, and enough to keep me motivated.

### and 3 weekends later...I had a PoC

---

![Proof of Concept of trading cards](/GDCollectionPrototype.gif "Animated gif of prototype") ![Proof of Concept of trading cards card flip](/GDflipfix.gif "Animated gif of prototype")

## PoC TICK

---

Now that I had a PoC. It was time to understand if and how I could store data, thats where [MongoDB](https://cloud.mongodb.com/) came in. Now it was getting tricky. You see, there are some limitations with [Twitch Extensions](https://dev.twitch.tv/docs/extensions), particularily what you can, and cannot do client side in the extension itself. Twitch hosts the client side code to iframe the application in various views, Twitch do not provide a backend. I needed to store various things, OAuth API tokens, viewers card collection data etc. This needed a backend. After, a few hours of reading, I learned alot about Twitch Extension architecture, such as the EBS or "Extension Backend Service". This has to be hosted by you, the Extension developer, and Twitch provides the preferred mechanisms to connect to that EBS using JWT or [JSON Web Tokens](https://jwt.io/).

[Heroku](https://www.heroku.com/) to the rescue! Wow, we live in an amazing time in the web, I haven't been this excited since Flash and ActionScript...Anywho, Heroku _is a platform as a service (PaaS) that enables developers to build, run, and operate applications entirely in the cloud._ What this means, is I am able to easily set up a Node server on Heroku (for free) under the Hobbyiest tier (though we are now paying for the $7 tier now that it's live), and it only took an hour to learn and deployments are simply a git commit. A Special thanks to my work colleque Feng, as here is where I got a bit stuck...

I learned HEAPS here:

- Nodejs
- Authenticated Headers
- fetch
- CORS...so much CORS

This took a fair bit to do, lots of trial and error, but with some perseverance, and some help from what I consider a real developer, we got it all working.

## Twitch APIs and ComfyJs

---

This part was actually pretty simple, I had come accross a open source JavaScript library from Twitch developer [instafluff](https://www.instafluff.tv/) called [Comfyjs](https://github.com/instafluff/ComfyJS). This essentially reduced a ton of effort to set up the functionality to unlock cards. But, it did introduce a problem, I originally had this in the client side application. Without thinking too much about how authentication works on Twitch Extensions, so a big learning for me here is that Twitch has no (to my knowledge) way of setting up environment variables or secrets. These need to be stored on your EBS, and thus a refactor was needed to put it all server side on Heroku.

A benefit is, moving things sever side actually cleared up a bug where if viewers had the stream open in more than one browser tab they could unlock multiple cards for each screen they had open, yup, thats software dev, you never really know what will happen until users get a hold of it. We had run a few live tests with a few users during development, it was hugely helpful to see how different viewers interacted with the app.

## Release v1 - 3 Months after POC

---

![Release version one](/Walkthrough1.gif "Animated gif of first release currently live")

We did it team! We went live in October and the app is running and it still has some features and improvements to come. Though I will be taking a small break to write my second book, which I have been procrastinating from since starting this project, reduce work in progress!

You can come check out the app and collect some trading cards over at [https://www.twitch.tv/gettingdicey](https://www.twitch.tv/gettingdicey) Live on Mondays 7:30pm NZT

## Release v2 - 6 Months after POC

---

![Release version two](/WIP3.gif "Animated gif of second release currently live")

![Displaying Art By text for artists](/ArtBy.gif "Animated gif of second release currently live")


Getting Dicey Trading Cards


## Preamble

---

I was about 7 years old when my teacher got fed up with my horsing around in class when we were supposed to be practicing writing. I don't recall her name, but she definately started something when dragging me out of the classroom to the school library, sitting me down at a small lonesome desk with several sheets of lined paper and a pencil. "You write until I come back!", and she proceeds to shut the door behind her. So, I put my head down and begin to write what I recall was 22 pages of a knight facing off against a dragon until the teacher returned an hour or so later.

I felt proud of myself, I think the teacher was also, or maybe she enjoyed the peace and quiet.

Since then, most of my writing has been in video game magazines, software development proposals or contracts. There was definately an itch to learn to write a novel or short story at some stage.

## The Idea

---

With most of my projects, some inspiration generally sparks a thought which can snowball into a _sense of purpose_.
I participated in a text adventure with our online friends during COVID lockdowns, and the Game Keeper had curated a completely unique setting using the [Choasium Call of Cthuluh](https://www.chaosium.com/call-of-cthulhu-rpg/) rules. Instead of playing on a table top, we simply played out the adventure online, in text over our Discord, and it worked out surprisingly well.

It was such a great experience, I had an idea to write out that adventure from my own characters perspective.

## Learning to publish a book

---

For this project I didn't set out to write something to make money from it. I wanted to write a story and learn how to write something that could potentially be published.

I didn't really have a well established or thought out process for writing a book, so I simply just started by opening a word processor on my computer and began from the start. I knew I didn't want to focus on spelling and grammar, like my "blogs" I just write what I think, and do my best to tidy it up later, I think you get a more personable reading experience. One of my friends (hi Russ) has always insisted he review my emails, documentation, and proposals, and he said I am getting better, which is what counts in my book. In any case, spelling and grammer can be fixed later in the process.

## Kindle Direct Publishing

---

It didn't take me long to learn about Kindle Direct Publishing or KDP. Amazons publishing platform is by far the cheapest and most accessible platform I could find. It also has guideance on how to write a manuscript, though I didn't take one source on that, I surfed the googlesphere for "Novel Manuscript example" and "Novel Manuscript templates". There is plenty of information out there.

An interesting thing about KDP is, while you start with a Kindle or e-book release, there are options for printing (on demand) paper and hardback copies as well, the latter becoming available after 6 months once you have set up paperback copies. There is no need to hold any inventory.

A thing to note with KDP. If you are intending to make money, know they withhold the revenue until it reaches a threshold of $100 of your countries currency, and depending on your book it may take some time before this threshold is met.

## The writing process

---

It was 2 months in and I had a bulk of the 79 page story done. Spending 2 hours a day, and couple of weekends here and there I could spend a bit longer writing. I would find myself writing the fun parts first, the more interesting scenes in my mind, then going back and forth between pages joining up the scenes and events as I write them.

I had several locations in mind the protagonists ends up, until the big ending, so I was simply peicing the journey together, filling in dialogue and events on the way.

## Grammar and structure

---

English is hard, I also feel like punctuation can be subjective at times. But, the best tool you have is your users, or readers in my case sharing my work with others offered some great feedback, and the great thing about the KDP platform is that you can fix mistakes at anytime and any new book printed comes with those fixes, and your e-book updates automatically when you upload a new manuscript file.

For the first months of release, I first printed a proof copy, read it over a few times, fixed a few issues, then I printed a few paperback author copies, sent some friends and workmates a copy of the manuscript for constructive critisim. People tend to respond posititvely about the story and the book, and provided some edits here and there.

Now I have a hardcover available, it may still have one or two incorrect spellings "heals" vs "heels" (thanks Barb), so far readers have enjoyed what matters, the story.

## Dont be afraid to just start

---

You can buy [The Dark that Dwells Beneath Te Aro](https://www.amazon.com/Dark-that-Dwells-Beneath-Aro/dp/B09JVFJKFX/) on Amazon. Please consider leaving a review on amazon, it will help toward my next follow up novel currently in progress.


L.J. Percy

Workin progress.