Post AMro33PqB1d9DlxQky by binder@hackers.town
(DIR) More posts by binder@hackers.town
(DIR) Post #AMrmtNVAXjLUfOGw52 by someodd@fosstodon.org
2022-08-24T22:16:30Z
0 likes, 0 repeats
Programming: I used to be fond of the idea of hacking things together as fast as possible, but now, these days, I think it's just better to get things right the first time. But I also think there's some subtle balance you have to strike especially when first starting a project, maybe.Thoughts?
(DIR) Post #AMrnO98nzB9n6YU17Q by nebunez@fosstodon.org
2022-08-24T22:22:04Z
0 likes, 0 repeats
@someodd I'm in my 8th year of employment as a programmer, and I agree with this 110%
(DIR) Post #AMrnRen2lvHW8ByiSu by brianb@fosstodon.org
2022-08-24T22:22:42Z
0 likes, 0 repeats
@someodd I go for "make it work first" and then move into "make it maintainable" once the idea is on place.
(DIR) Post #AMrnZPhgkLndesAjOi by Angle@anticapitalist.party
2022-08-24T22:24:06Z
0 likes, 0 repeats
@someodd Getting things right the first time is great... If you know what 'right' is. If not, you might be better off doing some rapid prototyping while leaving things open for change later. What I usually have to do. XD
(DIR) Post #AMrntId2lDi9VWTvqC by zens@merveilles.town
2022-08-24T22:27:40Z
0 likes, 0 repeats
@someodd if you don’t hack together something fast, what are you fixing to make it right?
(DIR) Post #AMro33PqB1d9DlxQky by binder@hackers.town
2022-08-24T22:29:27Z
0 likes, 0 repeats
@someodd I've always been of the build better mindset.
(DIR) Post #AMroiBPJMyN9sZK0xc by wizzwizz4@fosstodon.org
2022-08-24T22:36:53Z
0 likes, 0 repeats
@someodd Hacking is for when you don't know how to design things. It's like a breadboard v.s. an ASIC.
(DIR) Post #AMrpl8HlX46r1JlLmq by thraeryn@hackers.town
2022-08-24T22:48:38Z
0 likes, 0 repeats
@someodd In my own experience, it's important to take the initial excitement I feel, turn it into productivity, and bang out something I can look at, point toAfter that, when I've shown people my work, is when I think "This still has a long way to go." That's when I dig in to improving the project.I need that first, exciting stage, though, where I tell folks: "Yeah, I'm building a house! I've even got the land cleared and most of the framing up!" I need those good feelings from showing off to keep me on task.But I'm obviously not programming for a living. 😅
(DIR) Post #AMrpvf38ZTPRX2wO92 by byterhymer@mastodon.social
2022-08-24T22:50:28Z
0 likes, 1 repeats
@someodd At CoLABoration for the Future 2010 at the Computer History Museum, where Doug Engelbart and many of his contemporaries were gathered, it was discussed how the ideal is to spend 70+% of time in a brainstorming stage, getting as many variant perspectives and input as possible before working on an implementation. Collaborative intelligence can often help avoid problems which may be non-obvious.The shorthand of: "measure twice, cut once" also holds true I think?Plan more, patch less.
(DIR) Post #AMsYX9MNElKQEecnk8 by M0YNG@mastodon.radio
2022-08-25T07:10:14Z
0 likes, 0 repeats
@someodd sure, I could do it "right" but then I'll often never get it done.Nothing I write is likely to be used by more than five people, so I'd rather get it working, even if not technically "right"I don't have the luxury of time, or space, so if it works, that's good enough.I'd rather make it fault tolerant so I can keep using it when it doesn't work and fix it when I can.