DEV Community: Dani Amsalem

I Used ChatGPT to Create Something Ugly

Dani Amsalem — Tue, 21 Mar 2023 22:52:50 +0000

TL;DR 🤓

I was building my first Chrome Extension and got stuck.
I researched and explored to no avail.
A few weeks later, in the very late hours of the evening, I asked ChatGPT for help.
I was surprised to receive directions and even code samples.
As a result, I published my first Chrome extension!

Check out the As a Result 🎯 title at the very bottom of this article for the link!

I'd been working on a Chrome extension and reveling in the discomfort of discovery.

Sure, I'd heard of ChatGPT but I had no need for a chatbot. I didn't want to touch it.

In fact, I thought ChatGPT would be another fad.

That was until I read something from information security professional and writer, Daniel Miessler.

Do not let yourself fall into the Luddite* Trap with regard to AI, AI prompts, or ChatGPT. Do not do this. I know it’s tempting, and especially for people in security and people who appreciate the liberal arts. Don’t do it.

You’ll become the old guys yelling at people on his lawn. Don’t be that guy. Invite the new kids in for kool-aid. Learn the new lingo. Stay young. Stay curious.

Lean into this. Don’t be the person screaming at the printing press. It not only won’t help you, but it won’t make a dent. This is coming regardless of what anyone has to say about it.

Sourced from Daniel Miessler

* Luddite - a person opposed to new technology or ways of working.
Google’s English dictionary by Oxford Languages

That same day, I signed up for ChatGPT and installed it on my phone using Daniel's instructions and the OpenAI API.

Later that evening, I talked to a developer friend about ChatGPT. He said he'd been using it to help him with work.

Here's how he described ChatGPT

It's basically the absolute most perfect rubber duck
It's a f****n robo-duck

Of course, up until this point I'd been asking it silly questions such as:

Tell me about Donald Trump as if you were Doctor Who

Can you pretend we're in a world where insults and curses are not hurtful but instead fun and funny? In that world, can you give me 4 very fun and funny insults?

When I asked my friend which interface he'd been using to help him with his code, he sent me the link to OpenAI chat

That's when I began experimenting by asking it some VanillaJS questions like:

Tell me about the JS reduce function

A day later, I began using it to review some ReactJS fundamentals including:

What is a ReactJS hook and why is it called that?

That weekend, late into the night, I came up with a game-changing idea.

I should ask ChatGPT how to help me debug my Chrome extension!

Here's my exact query:

I'm building a chrome extension and I'm trying to scrape data from the page using the script.js file and display that in the popup.html file. How do I transfer the data between those two places?

In seconds, it responded with an explanation of how to transfer data as well as a code snippet to implement.

I was so excited, I could barely sleep! I finally had a path and some starting code to get unstuck and complete my Chrome extension project.

The next day, I committed myself to finishing my project. I was certain ChatGPT was the key to my coding problems.

As soon as I began implementing ChatGPT's code, I noticed the data it provided wasn't perfect. Often the answers used outdated code from deprecated Google Chrome processes and APIs.

But by giving it rules to apply for future responses, I found it improved quite a bit. For example, I'd say,

Please only give me responses that conform to "manifest_version": 3

I'd also often find myself asking it one question, which I'd use to evolve further questions. For example, I might ask it for a solution and then ask it to refactor that solution using JavaScript ES6 syntax.

Of course, there were some things that it just couldn't solve for me.

I spent a good couple of hours trying to implement some code ChatGPT suggested only to inevitably and consistently run into errors.

I asked it for alternative solutions, I asked it to check for more modern implementations but nothing seemed to work.

Then I came up with the brilliant idea (sarcasm) of reloading my browser tab and the Chrome extension. Lo and behold, error gone!

It may be an excellent rubber duck, but it's not looking over my shoulder to catch every sort of stupidity.

On the other hand, ChatGPT can do some brilliantly quick debugging.

I ran into some errors and rather than searching across the web for potential fixes, I provided ChatGPT with my code plus error and asked it to help me debug it.

Like magic, it indicated the object I was having difficulty with and a conditional way to handle a null object.

Wham, bam, thank you ma'am, my code worked!

As a Result 🎯

I was able to finish my first Chrome extension in days after using ChatGPT whereas I had made zero progress on my project for the previous 2 weeks.

A day or so later I completed the MVP and published my extension!

It's ugly, but you can check it out on the Chrome Web Store if you search for "SignUpSaver". Or visit this link https://chrome.google.com/webstore/detail/signupsaver/ibbajpbnilbagkgamelfmjnpapadkagm

And here's the Github repo if you want to tear it apart https://github.com/damsalem/ext-signupsaver

I've since published another ugly Chrome extension, this one a digital clock https://chrome.google.com/webstore/detail/hms-clock/mbjkpklcjihpfbldfapoecehlibmfffk

The Takeaway 🥡

As you've likely concluded, I'm now a big fan of ChatGPT. I excitedly discuss it with anyone who will listen.

I think it can be an excellent tool and learning resource for coders to both debug and brainstorm potential solutions.

I believe it can help every dev when we run into sticky situations every now and then.

Plus, it's pretty fun to chat with!

Notes
All images except for my app screenshot were generated by DALL·E, OpenAI

So you finished bootcamp?

Dani Amsalem — Sat, 26 Feb 2022 19:09:11 +0000

Now you're job hunting, or secured your first gig. Here's my story after finishing a full-stack bootcamp

--10 minute reading time--
I'd already held a wide variety of jobs. I'd tried my hand at cold-calling sales, installing tile in kitchens and bathrooms, working as a background actor in Hollywood, and welding studs in various oil refineries across the States.

I'd always wanted to be a developer, but I thought coding was too hard. That was until I learned about a 3 month long full-stack bootcamp. This was September of 2018.

I loved the bootcamp because it offered a promising career. I breezed through my HTML and CSS coursework but then barely grasped anything on my JavaScript and .NET courses.

I began hoping that I’d figure out how to code while on the job. After all, it was bootcamp, not a computer science degree!

Before I graduated, I was already sending out resumes. I started out sending around several high-quality resumes every day. However, I wasn't really generating any interest so I decided to create a simple template to speed up my process. I began sending dozens of resumes out every day.

To break up the monotony of job-hunting, I was taking a ReactJS course. As soon as I began, I realized this was too hard. I was trying to work on a project (ReactJS) without grasping the tools (JavaScript) that were required.

It was like trying to build a house without knowing how to use a drill, hammer or level.

I landed several interviews and sounded like a frantic idiot each time.

I remember one interview with a very interesting software company, I hoped I could catch his interest by mentioning that I knew ReactJS 🤦‍♂️

The interviewer, the CTO of the company, asked what my favorite part of React was. I quickly navigated to my course’s sales page and rattled off some of the bullet points.

Suffice it to say, I didn’t get another interview!

To expand my job-hunting activities, I began looking on Google and Yelp for companies in my area that might not be posting on job boards.

I found several agencies and would look for their website’s Careers page. If they didn’t have one, I’d reach out on their Contact page.

Finally, nearly 3 months in, one of those marketing agencies responded.

On a Wednesday, they gave me their coding challenge. It involved building a one-page WordPress page (something I had never done) and turning it in by Monday.

Because it looked like a tough project, I flip-flopped on deciding if completing the challenge was even worth it. I continued blasting out my resume through Friday.

However, that Saturday, I decided to knock the coding challenge out. I spent an hour or two watching a handful of YouTube videos and reading a couple of articles.

There were so many new terms, I wasn’t quite sure what I was looking at!

I downloaded some program called MAMP and used the same code editor from the bootcamp, Visual Studio Code. 6 hours and a lot of groaning later, I’d produced something I was somewhat proud of.

I turned it in immediately and we escaped from our apartment for a much needed break.

I really, really hoped this was it. But I couldn’t rest on my laurels. What if my little WordPress page was actually garbage?

A day or so later, I got a call that I was to come in for an in-person interview!

Thursday afternoon, I rode the subway, laptop in tow, to meet what might be my future employers for the first time.

The HR lady seated me in a small Upwork cubicle and told me she’d be back with the lead dev (gulp).

They returned and began with some introductory info about the company. Then they asked about me and my interests.

Finally, the lead dev swiveled his laptop towards me and asked me in what directory do I make edits to a WordPress project.

I began sweating…

I’d only looked at the WordPress folders for a short while hours that last Saturday!

Um… I think wp-content?

He paused. I dearly wished I'd reviewed my project before coming here! A moment later he confirmed my answer.

Inside I celebrated with fireworks and applause 🎇👏

The rest of the interview breezed by. I think he asked me some questions related to HTML and CSS, perhaps about the Bootstrap framework. I knew those well from the bootcamp.

The following week, the lead dev sent me a text me saying they'd get back to me with a job offer in a day or so! Wow, I jumped around my apartment yelling hurrah to my wife.

A couple days later, the HR lady emailed me the job offer. It was a 3 month long contract (with an option to extend) for a junior web dev role building WordPress templates. Then my eyes rested on the salary.

The offer was for a surprisingly low $48,000 year.

Let me put that in context. I had always hoped for at least $60,000-$65,0000 per year. Being a 28 year old married man with a wife who had gone back to school in NYC, we had been living off of my savings.

Once I was employed, we would continue living off of my single income and unfortunately $48,000 meant we would have to continue dipping into my rapidly dwindling savings.

The 3 month contract meant I could be job hunting all over again if they didn't like me!

Of course, I needed to just get my start and this was the first and only job offer to come in. I had to take it.

My first day on the job I was pretty certain they’d realize I was a faker.

I stepped into the shared workspace of the graphic design and copywriting team. This was where the lead dev and junior dev were working.

Everyone stopped what they were doing to shout greetings at me. I tried to match their enthusiasm but I'm pretty sure I missed the mark.

The HR lady brought me into a small, glass-walled room inside the workspace. She had me sign some paperwork and then brought the lead dev in to get me started.

I'd brought my personal laptop which was good because they said they'd buy me a brand new Macbook Pro soon. Until then, I should set up with their work environment.

I installed their code editor, grabbed a licensed copy of MAMP and was given a link to a Github repository (repo for short).

I desperately tried to remember some basic git commands. Struggling, I Googled it and got the project on my computer.

The lead dev sat down with me and had me add a semicolon to a CSS file and push it up to the repo. I saw my changes and was all smiles. This wasn't so hard!

Then he sent me a link to a live WordPress project and gave me the credentials to log in. My instructions were to change some content in the WordPress editor.

I'd already built a WordPress website years before becoming a developer so I knew my way around. This was easy!

My first few days continued like that, making simple edits to existing WordPress sites through the WordPress dashboard and getting oriented to the environment.

I made small talk with my colleagues and began to slowly unwind.

A couple of days later, I was given a new Github repo and told to edit an existing page in my code editor.

I struggled to find the applicable page so I asked the other junior dev. He shared that he was the one who actually built this page and so he was well-acquainted with the project.

It took me well into the afternoon to figure out how the HTML was structured, how the CSS related to it and how to make some simple changes.

I would constantly Google things like CSS selectors and HTML main tag.

Later, the lead dev showed me a couple of tricks to make this sort of work easier.

The days passed and I continued learning and struggling.

My first major task was to build out a new template based on a mockup we received from graphic design.

I looked at existing pages built by one of the other two devs and then I'd Google the terms and tools that I'd encounter.

The other junior dev mentioned something called "CSS flexbox" and "CSS grid". I studied the online documentation for both during work hours. I'd also found some online educational games and would play them when I'd get home from work.

I'd spend many of my evenings reading WordPress documentation, exploring CSS guides, and Googling things I'd encountered but didn't understand.

I was determined to get an offer to continue working here.

In fact, I'd been talking to some of my colleagues and I learned that everyone gets an initial 3 month provisional job offer. Then they're offered a second and final 3 month extension before they're either let go or brought on as full time.

3 months in and I was interviewed by HR, the CEO and the creative director.

Suffice it to say, I'd been anxious about this meeting.

We went through the pleasantries and then they asked about my experience so far. I tried to provide a lot of positive feedback. I also brought up the fact that I really needed and wanted a higher salary (ideally $65,000) just so we could survive.

I explained that I knew that wasn't their problem, but I really wanted to continue working here and this was a major requirement.

They provided some positive feedback about my work-performance and explained that they would consider my request and get back to me.

Two weeks later I had a follow up meeting.

I had come prepared. I had noted down various ways I had gone above and beyond the typical expectations. I'd been recording down my day to day activities and organized it into a write-up of my role. I figured that would help them onboard future developers and make the experience easier for everyone involved.

I also provided some statistics of my improving performance.

Their feedback was again positive but tempered with an honest but slightly negative comment about my lack of experience.

At last they proposed a full-time job offer with a raise to $52,000 year salary!

It was a full time role with slightly better pay and I figured I'd have future opportunities for better pay. I'd also be able to skip that second 3 months of provisional work.

I happily accepted.

Moving on to better, brighter future.

I'd now been with the same company for nearly a year and a half and had gotten another raise to $58,000 (with a one-time year-end bonus of $5,000).

I was leaving for another company. The new job was for $75,000 with an opportunity for a raise to $80,000 after 3 months. I didn't get the raise after 3 months, but worked my butt off and an additional 3 months later got the raise.

I've since switched to another company and am making nearly 6-figures. For the first few weeks at this company, I was getting paid handsomely to study a variety of courses on the tools and languages we're using.

How amazing is that? Just a couple of years prior, I'd spent thousands to attend a bootcamp. Now I was getting paid thousands to study courses!

I'm loving my job, my company and my team. It's fun and challenging and has a great work environment. Plus we get excellent benefits.

Wrapping it all up.

My point in sharing this long, personal story is that becoming a developer is not binary. You don't just turn the corner and become an expert. It's a gradual process that may require a lot of busy nights and weekends.

It took me 3 months to find a job after applying at over 500 companies, primarily in New York City.

You may be faced with the choice of what language to study or whether to go for back-end or front-end. Do your research and begin whittling down your options discarding those topics and interests you're uncertain about in favor of those you have more certainty for.

Eventually, you'll pursue a route and it will be the best one you could have chosen, with the data you had at the time. Don't worry, you can always shift within the dev space.

Shifts are made easier by studying and practicing outside of work hours.

My studies never finished at the bootcamp. I continued studying while job hunting and later while on the job and at home.

I'm continuing to study nearly 3.5 years after finishing the bootcamp.

While the pay as a dev can be excellent, initial roles may start off with lower pay. Fortunately, your future is bright and full of possibilities.

Lastly, everyone experiences imposter syndrome.

The funny thing is, everyone pretends. We pretend to know what we're talking about until we do.

Some folks go hard in the pursuit of excellence while others achieve passable levels and then become satisfied. Those who pursue excellence and have ambition have virtually no ceiling.

Did you hear that Amazon recently raised the max salary to $350,000/year?

Congratulations on finishing your bootcamp! Now get after it.

Is Programming Actually Hard?

Dani Amsalem — Thu, 04 Jun 2020 15:50:33 +0000

Not in the way you think it is…

In September of 2018, I began my first of 90 days of software developer bootcamp. I had just recently turned 28 and recent events in my life helped me decide to quit my job (as an e-commerce brand manager) and pivot into being a dev.

My only regret? I wish I had done it sooner.

When I was a kid, I used to think becoming a developer was hard. I thought it required lots and lots of effort to learn. I imagined forcing myself to read technical manuals and documentation. I had visions of studying math and formulas to develop superior thinking skills.

Fortunately, I couldn't be more wrong.

Recently, I reviewed my preconceptions and recognized them as fundamentally flawed thinking. It isn't hard, it shouldn't be complex, and it doesn't require superior mental powers.

I've found 3 requirements to becoming a developer:

Understand the words and symbols (there are a few of these).
Understand the grammar (developers call this "syntax" and it's the way words are put together to communicate ideas).
Understand how to Google what you don't know (so, so important)

Bootcamp

I attended a really interesting bootcamp in Portland, Oregon. What made it interesting wasn't the variety of courses, but rather the first course every program began with.

The first course you did defined every word and symbol fundamental to programming.

Everything from the symbols used in links (URLs), to the fundamental words like "computer" and "developer", as well as deeper technical terms, all were defined.

As I continued through the bootcamp's courses, I began to learn more about the grammar that is used. Fortunately, many languages use a similar grammar (aka syntax) and eventually this becomes second nature.

One of the things the bootcamp stressed was being able to do your own research.

At first sorting out my own confusions was very tough. As I pressed on, I found that using my new vocabulary had a major, positive impact on how I conducted my research.

I began using certain key words and phrases that other developers also used when trying to solve similar problems as me.

At some point, I realized I knew how to Google my coding questions.

Ultimately, what I got from bootcamp was belief in myself.

I knew how to code, I knew how to continue learning and growing, and I knew how to dig myself out of pretty much any confusion.

My First Job

After many hundreds of applications, many phone interviews (and rejections), as well as several coding challenges, I landed my first job as a web developer at an agency in NYC.

The pay wasn't great, the work was challenging, but I loved it.

I was constantly studying and researching because my role as a WordPress developer meant I had a new language to study. Not only that, but I still had so much to learn when it came to fundamentals of web development.

Fortunately, I had all the tools I needed:

An understanding of common terms and symbols.
An understanding of the grammar (syntax).
The ability to research and solve my own problems.

When you have a job, it's so much easier to learn and retain what you've learned.

When programming is your job, by necessity, you must learn new ways to do things.

When you work with other developers, naturally your understanding of development grows. Every developer has a different point of view as far as grammar (syntax), tools to use, and the process (any process) should be started.

Programming is less about repetitively solving the same problem, and more about finding new and better ways to solve the problem.

For example:

You can start a puzzle by finding all the edges and corners and assembling from there. Or you can start from the main point of interest, and build your way out.
You can start a video game by discovering what kills you, or you can explore the map, or even by reading the forums.
You can write a short story from the hero's perspective, from the narrator's perspective, or from a friend's perspective.

As many ways as there are of solving puzzles, video games, and challenges in life, similarly, you will find many ways to code things.

In Summary

So to sum it up, more than a year and a half into my career as a web developer I've recognized a few things that I wish my younger, twenty-something self had known:

Programming isn't hard, at least not like you might expect. All it requires are good study materials, and enough persistence to keep at it every day, even if it's only for an hour.
Programming shouldn't be complex, the more I read and study - and I do that daily - the more I find that all senior developers and experts advise us to write simple, human-readable code.
Programming shouldn't be avoided, just because you don't understand it. It's actually far simpler than it looks. All you have to do is break it down into single, simple components.

If you want to become a software developer or some other sort of specialist, don't become discouraged by how "hard" it all looks, or the appearance of complexity.

More often than not, the complexities are just a result of misunderstanding the words, symbols and grammar.

If you have those fundamentals in, and have some guidance for doing your own research, I believe any subject can be conquered, with a little persistence.

References

If you want to know what bootcamp I went to, or what study materials I recommend, check these out:

I attended The Tech Academy Bootcamp, they have online and in-person classes and you can find them at learncodinganywhere.com (if you tell them I recommended you I may earn a small commission).
The Tech Academy also published a tech dictionary with the simplest, best definitions ever. You can find the dictionary on Amazon.
After completing the bootcamp, I went through most of FreeCodeCamp's curriculum. While they don't cover words and symbols you need to know, they do have a lot of information and best of all, it's free. Learn more at freecodecamp.org
If you're struggling with computer studies in general, I can't speak highly enough about Study Technology by Applied Scholastics. Here's a quote:

The basic fact is that students fail to learn because no one ever taught them how to learn - that is, how to identify the barriers to learning and how to overcome those barriers.

If you have any questions or feedback, please share your thoughts below.