my nerdy friend that went on that journey with me is a musician and fashion model lol.
Maybe his/her experience in keeping the system simple and beautiful helped him/her recognise the passion in art.
my nerdy friend that went on that journey with me is a musician and fashion model lol.
Maybe his/her experience in keeping the system simple and beautiful helped him/her recognise the passion in art.
Haha your post made me reflect my journey. I had fun in college tinkering Arch Linux with i3. Now I’m an Infra Engineer (or DevOps Engineer, Platform Engineer, SRE, whatver) and still do the same job—keeping the system “reliable”.
That’s why I like it. No BS, no ads, no commercials, no show-offs, etc. Just some people with a bit of free time share their knowledge and stories.
I do wish we have more vibrant non-tech communities, though.
Then you have Clojure - a machine gun that shoots shivs.
Code aesthetic: If your code looks like a triangle, you’re seriously doing something wrong.
Well, people tend to pick the easiest way to achieve an objective, even though the solution is not simple nor optimised.
It’s sad to see it spit out text from the training set without the actual knowledge of date and time. Like it would be more awesome if it could call time.Now()
, but it 'll be a different story.
This is actually not a good advice, from my experience. If we don’t monitor, refactor, or improve the code, the software will rot, sooner or later. “Don’t touch” doesn’t mean we don’t ever think about the code, but we make the conscious choice not to modify it.