Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Ask HN: What change in your programming technique has been most transformative?

news.ycombinator.com

Post reply on HN
Print view View original

121–130 of 215 posts

Re: Ask HN: What change in your programming technique has been most transformative?

#121

Post by j88439h84 »

valand wrote: post #73

Static typings + type inference Parse, don't validate https://lexi-lambda.github.io/blog/2019/11/05/parse-don-t-va... All libs/products should be pure functions, with input output documented, making libs/products predictable Use in-app event sourcing to reduce the need for global states states DoD https://youtu.be/yy8jQgmhbAU In non bare-metal languages, this will be useful for readability For errors, return instead…

> in-app event sourcing

What's the difference between in-app and not?

Re: Ask HN: What change in your programming technique has been most transformative?

#122

Post by AdamCraven »

The most transformative experience was learning how to retain information better following the Coursera course: Learning How to Learn (https://www.coursera.org/learn/learning-how-to-learn)

I'd not always been the best learner and this taught me how to learn more effectively. Whilst at the sametime accepting the limitations of the brain.

It led me to find the Anki app and combined with more effective learning, it positively affected my ability to be a better programmer.

Re: Ask HN: What change in your programming technique has been most transformative?

#125

Post by AJRF »

From iOS perspective changing to clean architecture using VIPER has made our code testable and easier to reason about.

We enforce the architecture as much as possible through protocol conformance, which doesn’t always work, but works extraordinarily well for “Views” or “Scenes”.

It’s taken so much stress out of the development lifecycle for our team.

Re: Ask HN: What change in your programming technique has been most transformative?

#128

Post by gtirloni »

ericb wrote: post #64

Making debuggability (transparency) a first-class design criteria. For many (most) systems, there are designs that make perfect sense, but will be hard to debug. When I started designing so that programs could tell me what they are going to do, what they are doing, and why, and so that their state, wherever possible, could be expressed into a structure where I could "see" the wrongness, my development time went way d…

Interesting. Any examples of libraries or papers?

Re: Ask HN: What change in your programming technique has been most transformative?

#129

Post by hinkley »

glitchc wrote: post #29

Not mentioned yet 1) Start with consistent naming conventions, notation and structures 2) Rely on autocomplete to simplify typing/readability/programming effort. It’s a tremendous force multiplier. Ninja’d 3) TDD 4) Functional programming

Consistent naming does not mean “use the same word for all similar things”. It means using one word every time you have the same thing.

Words stop meaning anything when you use it all the time.

Use a thesaurus. Naming everything “handler” or “node” is just naming them “function” and “object”.

Re: Ask HN: What change in your programming technique has been most transformative?

#130

Post by contingencies »

nikivi wrote: post #6

Using https://github.com/watchexec/watchexec to evaluate code as I save. https://github.com/nikitavoloboev/dotfiles/blob/master/zsh/a...

Re: watchexec, another two patterns are: (1) trigger processes using pre-commit hooks with your local RCS/VCS. (2) replicate core watchexec functionality using inotify-tools, fsnotify or similar. As you seem to be using go also consider https://github.com/fsnotify/fsnotify
Post reply on HN