this post was submitted on 26 Oct 2023
71 points (90.8% liked)

Programming

17364 readers
173 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Rules

  • Follow the programming.dev instance rules
  • Keep content related to programming in some way
  • If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev



founded 1 year ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] burt@programming.dev 19 points 1 year ago* (last edited 1 year ago) (5 children)

Lots of good technical starting points here. I don't want to prematurely discourage you, but before you get into any code, evaluate your problem solving abilities. If that is an area you struggle in, work on that first, or at least in conjunction with programming basics.

I've worked with engineers who have all the code skills, but when faced with a complex issue, struggled to break it down into it's simplest components and wound up with a messy, over-engineered solution.

[–] rodolfo@lemmy.world 6 points 1 year ago (4 children)

particularly nasty situation, for real. in my experience, they know the bits of a framework, but they'll never get to write a modest regex: they'll have opinions on that too.

[–] ck_@discuss.tchncs.de 14 points 1 year ago (3 children)

That's why I don't get tired recommending How to solve it to engineers of every level

[–] Cratermaker@discuss.tchncs.de 4 points 1 year ago (1 children)
[–] ck_@discuss.tchncs.de 4 points 1 year ago

Should have added a disclaimer: it was written by a mathematician in 1948, so it's a bit of a dry read 😅

load more comments (1 replies)
load more comments (1 replies)
load more comments (1 replies)