justin = {
main feed
,
music
,
code
= {
cockos
,
reaper
,
wdl
,
ninjam
,
jsfx
,
more
}
,
askjf
,
pubkey
};
Ask Justin Frankel
No reasonable question unanswered since 2009!
Suggested topics: programming, music, sleep, coffee, etc.
Note: please do not ask questions about REAPER features, bugs or scheduling, use the
forums
instead.
Name:
Ask:
Human (enter yes):
[
back to index
] | [
unreplied
] | [
replied
] | [
recent comments
] | [
all
]
Question:
Hey Justin! How do you weigh implementing code design that is much faster to implement (hacky) vs design that is more robust but will take much longer to implement, is it just down to importance of the system/how hot the path is? Any times you regretfully implemented the former, lessons learned? Thank you!
Asked by Jack (194.110.115.x) on May 6 2025, 8:16pm
Reply on May 6 2025, 8:23pm (edited at May 6 2025, 8:25pm):
there are a lot of other factors, but the biggest is probably the certainty of the design: if the elegant solution is fully understood and I have a great degree of confidence in it being the correct solution, then go that route even if it's a ton of extra work. if the problem isn't sufficiently understood such that an elegant solution is not unlikely to end up being the wrong solution, then definitely go hacky until you figure out what the elegant solution is. for things in between, interpolate...
the biggest thing, though, is don't be afraid to rewrite _small_ subsystems in a larger project. that is a great thing to be able to do, once you've seen how they've been used for a long time. because at that point you should understand the elegant solution.
Comment:
Your Name:
-- Site Owner's Name:
(for human-verification) Comment:
[
back to index
] | [
unreplied
] | [
replied
] | [
recent comments
] | [
all
]
Copyright 2025 Justin Frankel
.
|
RSS