DEV Community: Adam Holwerda

You Can Develop Every Idea You Have - Here's How

Adam Holwerda — Thu, 24 Jun 2021 04:52:37 +0000

Maybe this is obvious from the post title, but I'm a firm believer in attempting to develop every idea I ever have, in some way or other. That could be a napkin with a drawing on it, a slip of paper, a note on my phone, a Balsamiq wireframe.

I have a binder filled with ideas for UX and UI ideas. A web application that displays documents by mimicking an envelope opening. A Netflix-style content library that works like a dry-cleaning rack. Dioramas with controllable puppets performing on tiny stages. A smorgasbord of skeuomorphic schematics that would disgust Jony Ive. All because I make it a point to write down anything that occurs to me as a development idea, good or not.

I've also got a healthy influx of new ideas. Anybody who knows me would probably tell you this influx is too healthy. But new ideas can't be stopped. They're the culmination of being alive and awake, of collecting and creating things, and I have a hard time putting them aside. New ideas are often so interesting to me that I have no choice but to drop everything in order to pursue New Priority One, if only for a few minutes or hours.

This seems like an unfortunate dilemma. "Sucks for that guy with all the ideas," you might be thinking, "he'll never have time to finish them all."

And you're right. I can't finish every idea. But there's something else I can do that allows me to finish any idea, now or in the future.

What's that thing? I can start each idea on a development path.

What does that path look like? Well, it could look like this:

I can write a paragraph and draw a sketch of something, and I can throw that in a binder. At any point in the future I can pick up that sketch or description and push the idea further along the development path. I can use the sketch to make a Codepen or Codesandbox or Glitch project. I like starting in one of these programs rather than a "folder-spun" project using a command line boilerplate like npx create-react-app my-app or npx create-next-app my-app for a few different reasons:

Web apps like Glitch/Codepen/Codesandbox give you a development environment you can immediately access from anywhere, not just your development machines.
You can work on aspects of your app quicker than you might get to having to spin one up, and live-coding is a breeze with all of your changes recompiling and being shown to you in a window as you work.
Each project has a fullscreen view accessible via URL from the jump, so if you're working for a client or just on a new project, you can have a working link to it that's available from day one. This is not only an advantage, it feels like magic.
It ensures you're not wasting time on tooling or version controlling or deployment pipelines for projects that ultimately aren't worth pursuing.
Quick and dirty, find out if your idea works, and if it's worth further development, you can always export your project and start a git repo to make it "more real."

If an idea is "worthy" (usually I define this by the amount of time I'm spending working on it, and if the amount of code I'm writing is getting to the point where the web application is having a slower time building it,) I'll start keeping track of it in a version controlled repository associated with my Github account.

If an idea is not "worthy" I abandon it at and leave it for a future me to do something with (or not). There's no point working on projects that don't excite you or just for the purpose of "code complete" - I know developers who've worked on the same codebase for years and never came close to being "code complete" - it's a goal you can save for the projects of yours that are closest to you over time.

With Codepen, you can download a ZIP folder of your files (sans node_modules) and git init inside an unzipped version (maybe you move it to your ~/apps folder or something first) and start that way.

With Codesandbox, there's an integration with Github that lets you start a new repo with your project right from there (pictured below).

With Glitch, to download your project:

Open the project editor.
Go to the lower left corner of the editor and click Tools.
Click Git, Import and Export.
Click Download Project.
If your browser asks you to confirm or save, click OK.

as is documented here. There's also a way to export your project to GitHub

What does this work for?

You might be thinking to yourself, "Adam, I make Node applications."

Cool. There are a bunch of web-based tools for creating a node-like environment in the browser, and you can do your early development there:

Not a Javascript developer? No problem. Chances are there's an environment or a sandbox web application for your code flavor. Maybe your favorite language is Text. Then you might want to know about TxtFiddle.

What's your experience with tools like this? What's your strategy for keeping track of all your UX/UI/App ideas? If you have your own thoughts on all of this, leave a comment below. I'm always interested.

TL;DR:

What if every idea had an optionally finishable path? That's the thought behind Develop Every Idea. You don't know if any new Eureka! moment is a good idea, a bad idea, if you're going to spend half an hour on it or a month. That's why it's important to future-proof your mental content and put each idea on a development track. Don't limit your future self by deciding an idea is bad now. Record it, and leave it for a later, more discerning you.

Don't worry. If it's a great idea, you'll make it great! Trust the accumulation, and trust yourself to learn and grow.

I do.

I'm Adam, a web developer, self-published fiction author, and a sometimes somewhat humorous public speaker. I'm new to Dev, and you can follow me here or on Twitter @adamholwerda. I look forward to hearing from you!

13 Things To Check When Your Code Isn't Running

Adam Holwerda — Mon, 14 Jun 2021 18:41:13 +0000

Aidan Skinner

@aidanskinner

21 years down 'code mines and I'm still losing time to "this code is the not the code that is running"

17:57 PM - 14 Jun 2021

We've all been there. Some of us live there. You made code changes, and they aren't appearing in the compiled code, the locally-running web environment, or somewhere else you expect them to appear. I'll be using this list to save myself time in the future, and will be adding to it. Leave a comment with your own "Thing to Check" and I might add it!

Do you need to blow away a build folder?

I recently ran into an issue where a Typescript-compiled ./built folder used to generate a production build wasn't deleting old/renamed files (in the case of a folder restructure or renaming). So what ended up happening was, ./stores/SomeStore.js and ./stores/SomeStore/index.js were both files that existed in the build folder, but not my project. I'd make changes to ./stores/SomeStore/index.ts but when I built for production, the application was still being built with ./stores/SomeStore.js, and none of my code changes showed up in the application until I deleted .built and added a deletion step to my build process.

Did you make changes in a build folder?

Build folders often hold compiled versions of source folder code. If you're searching for code in your project and haven't excluded build folders from search, you can easily make the mistake of editing code that will just be overwritten by the source code when you build.

Are you "host filed"?

Are you thinking you're on a live version of an app because the URL shows that? But really you've host-filed yourself and you're proxying your local? Maybe it's time to vi /etc/hosts and check.

Environment variables obscuring debugging or removing your change?

Maybe you can't see your code change because logging is turned off in certain builds, or something.

Eliezer Steinbock (FrontWork.dev)

@elie2222

Incredibly annoying when the bug is having set the wrong environment variable. Seems to happen a fair amount 😭

Any tips for catching these sooner? Often a case of something working locally/in testing but not in staging/prod because env vars are different.

20:31 PM - 01 Nov 2020

Do you have multiple tabs/windows of the same App open, in different environments?

Have you ever refreshed, over and over, the staging version of an app, when what you meant to check was your local?

Josh Deltener

@joshdeltener

I just spent 20 minutes wondering why my code wasn't working, just to find out I was looking at staging instead of local dev. Ug. #toomanytabs #coffee #itsmonday

19:51 PM - 20 Jul 2020

Are you in the right terminal window/folder?

Some code needs to be run at a particular path, or from a terminal that has access and permissions to certain tools. Sometimes you have to touch a certain file to trigger a change, or you might have to spin up a new terminal.

Is there a delay in the view?

Does the code take a while to build after every change? Are you using a viewer that doesn't refresh the data source?

Laurie

@laurieontech

Not me thinking the mutation didn't work but it's really a database viewer with a delay showing the updated table 😭

17:37 PM - 14 Jun 2021

Did you save the file before building?

I can't tell you how many times I've rebuilt a project looking for an expected code change before noticing I haven't even saved the file I changed.

Molly Struve 🦄

@molly_struve

Code won't work? Did you try saving the file?

Your welcome.

18:26 PM - 22 Sep 2020

Making changes in the right branch? In the right file? In the right folder?

Maybe you've made a change in a feature branch but built the develop branch. Maybe you're working on a file with the right name, but you're in the wrong directory/at the wrong route. Maybe you're literally looking at the wrong file.

Anand Sriraman

@anandsriraman

@molly_struve I've been guilty of spending hours wondering why my code in test3.py isn't working, then realising I was running test2.py all along 😅

19:29 PM - 22 Sep 2020

Does your code change require other database or authentication changes?

Mouse

@mousedotexe

Me: deploys to AWS
Me, five minutes later: "why isn't my pipeline running?"
AWS: "Where is my MFA code, father? I crave authentication"

15:40 PM - 18 Dec 2020

Did you misspell something?

Fluffy Walkerr

@fluffywalkerr

Sat for 20 minutes trying to figure out why my code isn't running, I spelt append with 3 p's

16:41 PM - 29 Oct 2020

Árni St. Sigurðsson

@beltiras

@stebets Once took a colleague 5 minutes to spot a wrong case of a single letter in an environment variable name in a script. I had been looking for why the build didn't end up in the right place for 5 hours. 🤦‍♂️

04:47 AM - 22 Apr 2020

Did you push your code?

fraq

@0xfraq

"WHY ISN'T MY BUILD RUNNING? WHY DO YOU HATE ME?"
"Oh, I forgot to push my code"

21:31 PM - 31 Jul 2019

Are you checking build output but assuming build succeeded?

Maybe the build failed and you're still looking at the old application. It's happened to me.

If one of these ended up getting you unstuck, or you have your own Thing to Check, leave it below!