DEV Community: Chit Khine

The Scary Power of AI

Chit Khine — Wed, 26 Mar 2025 09:56:01 +0000

This is a submission for the Future Writing Challenge: How Technology Is Changing Things.

I have some free time for the day and pop up some ideas on creating some text animations which might be useful for my next project. I was planning on creating 100 styles at first but I focused more on the display side on how I can showcase my 18 styles that I created with ChatGPT. This took me around 2 hours to be available on vercel alone with ChatGPT's help Text Animations

After that, another idea pop up to create a personal diet plan app using AI. I created another NextJS app to support both backend and frontend. I was planning to use the OpenAI to provide the recommendations for a 7 day plan, however, OpenAI doesn't have a free quota anymore so I go through with the CohereAI. Again, I got this done in under 1 hour.

As someone who's been developing for over a decade, this pace is really unsettling.

What used to take a full sprint now takes me a coffee break and a few prompts. I’m building working products — frontend, backend, AI integration, even polish — all in literal hours. That’s exciting. But also? Terrifying.

Because if I can do this this fast, solo, with AI… imagine what someone younger, faster, or more ambitious can do with the same tools. It’s not just about keeping up anymore — it’s about knowing how to use the tools that might replace us.

So I’m not fighting the future.
I’m collaborating with it — before it learns to code better than me.

Will DevOp skills be a must for developers in the future? (From my journey)

Chit Khine — Sat, 23 Nov 2024 17:24:37 +0000

I have been working with AWS for 3 years now and I would like to revisit my journey of how I have been in touch with it and getting used to it.

It has been amazing how I have been entangled with AWS for the past three years. I came to know about the position and responsibilities of DevOps when I first received the news from my CEO for the company that I worked for 3 years ago. It was a startup company inside a big corporation and my CEO informed me that our startup was about to die out soon in 3-4 months. Since I am one of the starting members of the startup, my CEO would love me to try out a new position as a DevOp Engineer which is the only open role at the moment. Most people encourage me to try it out since I would get used to it quickly since I came from a Fullstack Developer role.

The requirement to get accepted as a DevOp was to learn and perform the tasks with Senior members of the team and to pass the AWS Cloud Practitioner Exam in 2 months. During this period, I learned a lot about AWS starting from basics to (IAM, EC2s, S3 and scalings) as well as some best practices with what to do and what not during that period. As we all know, DevOps hold great responsibilities and also need to handle the stress of working mostly 24-7. I had a few situations where I needed to perform midnight deployments and also some painful task of learning while aligning with my new role. Therefore, I have decided to continue just my path of being a FullStack developer even though I fulfilled all the conditions requested by my company including passing the AWS Cloud Practitioner. However, I moved on to the new company as a FullStack Developer since I don’t want to pursue the life of DevOps.

The interesting fact is that the DevOp knowledge that I gained from those 2 and a half months have been a great asset for me in pursuing my FullStack Developer role. I learned to realize that many services provided by AWS are not only useful for DevOps tasks but also for developers, for example, AWS SES. Also, we can also help reduce the costs of our operations if we can understand how and which tool to use it perfectly. Even though I am currently working as a FullStack developer, I am heavily using the AWS services on many occasions and it truly helped me to become a better developer.

With AI and all the new technology, the demands and responsibilities of the developers have risen these days. Being able to integrate both the DevOps skill will become a necessity for the future since everything has been moving to the cloud. I am currently pursuing the AWS Certified Developer - Associate and I truly believe that every developer will need at least some skills of DevOps in the future.

First Time experience of recovering objects from Glacier to S3

Chit Khine — Fri, 15 Nov 2024 05:17:54 +0000

I had the objects of about 12TB of data and was trying to get rid of unnecessary data. I implemented a simple life cycle policy that moves the objects older than five years to move to a glacier.

Everything was going well for about 2 days and some objects are still related to the production images even though we haven't touched them for 5 years. The decision was to revert the operation.

I stopped the life cycle rule immediately to prevent further objects from going into the glacier storage class.

I read through the AWS documentation (https://docs.aws.amazon.com/AmazonS3/latest/userguide/restoring-objects.html) and found out that A few options I can use are using AWS CLI and AWS Batch Operations.
I decided to go with AWS Batch Operations since that seems like a reasonable choice but I do not have the manifest file. Therefore, I decided to use a AWS CLI in order to get the glacier items.

I prepare some scripts to get the list of items from the glacier_storage_class. however, due to the fact that there could be a large amount of objects in the list, it is always better to do it in the background.

2 things to note:

Provide the permission to the script

sudo chmod +x your_script.sh

Run it in background and make sure it is outputted the status to a log file.

./create_manifest.sh > manifest_log.txt 2>&1 & // run in background and this will show the processId
disown // disown the process
tail -f manifest_log.txt // you can see the status in the log files

Once I finished that, I prepare the manifest file in a format that AWS suggest

your_bucket_name/{object_key}

Make sure your object keys are encoded or else you will have a problem when you are running the batch processes.

Once you have the manifest_file, all you need now is to follow the steps to restore the glacier files and copy them to the standard bucket as in documentation.

Successfully restored!!!

This took me about 6 ~ 8 hours of back and forth debugging and checking up, so I hope it can help someone.

DEV Community: Chit Khine

The Scary Power of AI

Will DevOp skills be a must for developers in the future? (From my journey)

First Time experience of recovering objects from Glacier to S3

AWS #S3 #GlacierRecovery