Hacker News new | ask | show | jobs
by neximo64 1201 days ago
Does your noodle code solve a customer problem? Solving customer problems = immortality.
2 comments

this is a crucial point.

if the noodle nest does not solve an important customer problem, it can be eaten or thrown out. being eaten or thrown out is not the pathway to immortality. it must provide an important business function or feature, yet resist low-risk modification or understanding.

immortality of a noodle nest that solves an important customer problem may be amplified by wrapping the noodle nest in a faux-OO shell. E.g. in C++, one could create a single "god" class, define a large amount of mutable state belonging to the class, and then distributing the noodle nest between dozens of methods that take no arguments, return no values, mess with the noodle state, and mutually recursively call each other. immortality of a faux-OO noodle nest wrapped inside a god object can be further enhanced by applying the GoF "monotheism" pattern to ensure there is only one god object instantiated at runtime.

This post was just a complete lazy joke. I will recalibrate humor. I really appreciate all the serious nuanced replies though and feel bad now haha.
program main implicit none integer :: i ! Declare an integer variable character(len=16) :: msg ! Declare a character variable msg = "Immortal noodle nester" ! Assign the string value do i = len(msg), 1, -1 ! Loop backwards through each character of the string write(,'(a)', advance='no') msg(i:i) ! Write each character without advancing to a new line call sleep(1) ! Pause for one second end do write(,'(a)') "" ! Write an empty line to advance to a new line end program main