@KindaABigDyl@programming.dev
@KindaABigDyl@programming.dev avatar

KindaABigDyl

@KindaABigDyl@programming.dev

I make things: electronics and software and music and stories and all sorts of other things.

This profile is from a federated server and may be incomplete. Browse more on the original instance.

Programming and Humility

This is something I’ve been wondering about for a long time. Programming is an activity that makes you face your own fallibility all the time. You write some code, compile it or run it, and then 80% of the time, it doesn’t work exactly the way you imagined. There’s an error message, or it just behaves incorrectly. Then you...

KindaABigDyl,
@KindaABigDyl@programming.dev avatar

I feel it's caused by two things:

  • In industry, most people do more reading than writing, so you see a lot of other people's mistakes and have to fix them rather than your own. You don't make enough code to feel humbled.
  • Out of industry, there's often a vacuum. You code one way and make a thing and you're proud of it. You never hear criticism, and you're defensive of your abilities. This could be programmers who are new or just out of college or do it as a side to their main job. You don't share code enough with people to learn better ways and be humbled. Good enough is enough to be proud of.

There's an in between state that can open up the door to humility. Maybe a person who works at a company and thus deals with customers, non-programmers, and a team but still works on open source and in their free time build lots of side-projects and open sources them. You're making enough code and putting it out there enough to really receive good criticism. Those people would be more likely to be humble I suppose

KindaABigDyl,
@KindaABigDyl@programming.dev avatar

I find that for myself a huge thing is extensive planning.

It's easy to be doing something and realize oh I need this and that and then you dig more and more and suddenly scope creep hits and oh man there's too much now, let me take a break and then never come back.

Sit down with some paper or a tablet and draw out every detail of the game. Explain every mechanic, every state machine, every object placement. If you can design a tightly nit system and all the specific tasks it takes to get there before you jump in, it'll be easy to implement, you'll do it quicker, and you won't feel burned out.

KindaABigDyl,
@KindaABigDyl@programming.dev avatar

Fish? Just a betta

All creatures in the tank? There are also two assassin snails (there were bladder snails too originally, but well...)

  • All
  • Subscribed
  • Moderated
  • Favorites
  • JUstTest
  • GTA5RPClips
  • thenastyranch
  • ethstaker
  • everett
  • Durango
  • rosin
  • InstantRegret
  • DreamBathrooms
  • magazineikmin
  • Youngstown
  • mdbf
  • slotface
  • tacticalgear
  • anitta
  • kavyap
  • tester
  • cubers
  • cisconetworking
  • ngwrru68w68
  • khanakhh
  • normalnudes
  • provamag3
  • Leos
  • modclub
  • osvaldo12
  • megavids
  • lostlight
  • All magazines