HN user

anthonygore

201 karma
Posts108
Comments14
View on HN
walkthru.netlify.app 4y ago

Show HN: WalkThru – a better way of explaining code on the web

anthonygore
3pts1
divpay.netlify.app 4y ago

Show HN: DivPay – Get paid for sharing your programming knowledge

anthonygore
8pts3
coursekit.dev 4y ago

CourseKit: headless online course platform

anthonygore
19pts0
vuejsdevelopers.com 5y ago

Has Vite Made Vue CLI Obsolete?

anthonygore
2pts0
vuejsdevelopers.com 5y ago

WTF Is Vuex? A Beginner's Guide to Vuex 4

anthonygore
4pts0
vuejsdevelopers.com 5y ago

Should You Use Composition API as a Replacement for Vuex?

anthonygore
2pts0
vuejsdevelopers.com 5y ago

Cool Features of Vue Router 4

anthonygore
2pts0
vuejsdevelopers.com 5y ago

Build a Bootstrap 4 and Vue App

anthonygore
2pts0
vuejsdevelopers.com 6y ago

Code Coverage for Vue Applications

anthonygore
1pts0
vuejsdevelopers.com 6y ago

Vue 3 UX Wins with Async Components and Suspense

anthonygore
1pts0
www.freecodecamp.org 6y ago

How to Use Flat-File Data in a Static Nuxt App

anthonygore
2pts0
news.ycombinator.com 6y ago

Free Course Build a Single-Page App with Vue Router and Vue CLI

anthonygore
9pts0
vuejsdevelopers.com 6y ago

Why Vue CLI?

anthonygore
1pts0
vuejsdevelopers.com 6y ago

Reactivity in Vue 2, 3, and the Composition API

anthonygore
2pts0
vuejsdevelopers.com 6y ago

Vue 3 Tutorial (for Vue 2 Users)

anthonygore
2pts0
css-tricks.com 6y ago

How the Vue Composition API Replaces Vue Mixins

anthonygore
2pts0
vuejsdevelopers.com 6y ago

Clean, Scalable Forms with Vue Composition API

anthonygore
1pts0
vuejsdevelopers.com 6y ago

Vue.js 3 Tutorial – Build an App with New Features of Vue 3

anthonygore
2pts0
vuejsdevelopers.com 6y ago

Extending Vue.js Components

anthonygore
2pts0
vuejsdevelopers.com 6y ago

When to Use the New Vue Composition API (and When Not To)

anthonygore
1pts0
vuejsdevelopers.com 6y ago

7 Ways to Define a Component Template in Vue.js

anthonygore
2pts0
vuejsdevelopers.com 6y ago

A Closer Look at Vue Router

anthonygore
1pts0
vuejsdevelopers.com 6y ago

The Ajax Guide for Vue.js Apps

anthonygore
3pts0
vuejsdevelopers.com 6y ago

Build a Vue and Laravel Single-Page CRUD App

anthonygore
2pts0
vuejsdevelopers.com 6y ago

When to “Unstub” a Component in a Vue.js Unit Test

anthonygore
1pts0
vuejsdevelopers.com 6y ago

Dependency Mocks – A Secret Weapon for Vue Unit Tests

anthonygore
2pts0
vuejsdevelopers.com 6y ago

Knowing What to Test – Vue Component Unit Testing

anthonygore
1pts0
vuejsdevelopers.com 7y ago

Running Nightwatch E2E Tests with Headless Chrome and Vue CLI 3

anthonygore
2pts0
vuejsdevelopers.com 7y ago

Nuxt Tips Revisited

anthonygore
1pts0
vuejsdevelopers.com 7y ago

Accessible Form Validation Messages with ARIA and Vue.js

anthonygore
1pts0

Hi HN,

I’ve published over a hundred coding tutorials in the last few years and read hundreds more.

There are a number of things that frustrate me as both an author and reader:

- It’s difficult to create focused code examples.

- It’s difficult to keep code examples accurate and properly formatted.

My aim in creating WalkThru is to make it easier to read and write code tutorials. By utilizing the interactive and dynamic aspects of the web WalkThru provides:

- Code examples that can dynamically focus on specific lines.

- Code examples are compiled from linted and formatted source code.

I’d be grateful for any feedback or contributions.

https://github.com/walkthru/walkthru

How I approach it is to roughly map out the features it will need e.g. database, backend logic, UI etc. Then I'd think about whether or not I can achieve that with a stack I know e.g. Laravel/Vue.js. If not, I'd isolate the tricky parts and research what tools I'll probably need. Rinse and repeat until the right stack is settled on. Then start building a rough draft.

There are two important aspects here: getting ideas recorded, and organising them.

Note pads and text files are great for getting ideas down, but bad for organising them

If you can’t organise the ideas later, the whole system breaks down and you stop using it

I looked into different SaaS apps etc but they all had some features I didn’t like or were extraneous for me.

I realized the only way to do this was to create my own note taking app with a UI that was optimised for my way of doing things and would contain as few bottlenecks as possible for recording and organising

The result is an app where I can type something out in markdown format, apply tags, and then filter all my notes by tags

I uses local storage because I hate the idea of a login getting in the way of recording the idea

Identifying what's worth writing about is not a skill you have naturally, it's something you develop from practice. I know it sounds trite, but just start writing, and do it consistently, and you'll build the skill.

I've been blogging almost weekly for over a year. My first 5-10 articles garnered almost no interest; even now they have only a handful of reads on Medium. I was writing about jQuery tips for god's sake. But I eventually learned from my mistakes and now I have maybe 10 articles with more than 100 recommends on Medium, and I've had two articles make the front page of HN.

The problem with articles and discussions like this is that the "markers of success" pointed out may all be true, but incidental.

Take Slack as an example. Yes, it was a simple idea with low product surface area and easily protypeable etc etc. But other people had built Slack-like products before that met the all those same criteria and were not successful. The critical factors for Slack were the connections the founders had (or made), the VC money, and perhaps a whole bunch of other things.

As much as we'd like for there to be a nice, neat guides for successful businesses e.g. "build a little snowball", the truth is that the reasons for success are often totally unique, contradictory and unrepeatable.