You take an incredibly advanced and complex programming language,
and dumb it down to the absolute bare essentials in order to embark
on the journey of learning a new system.
Hello, World
21–30 of 174 posts
Re: Hello, World
#22I'm most impressed by the domain name
Re: Hello, World
#23Interesting, at 32 and already deciding this was it for you regarding programming where it was first a passion. Well, guess it's about what makes you happy. See you in a few years (if that) for yet another adventure, stop seeking greener pastures, it's all a lie.
Re: Hello, World
#24You take an incredibly advanced and complex programming language, and dumb it down to the absolute bare essentials in order to embark on the journey of learning a new system. The purpose of the "Hello, World!" program, at least as I've understood it, is to make sure that you can actually get code running with whatever language, frameworks, and build process you have. Printing out a simple phrase is sufficient to demo…
Is it though ? I always had a little voice in my head thinking this is just `a posteriori` justification.
Re: Hello, World
#25> I am burnt out on having a “40 hour” work week that actually occupies the majority of my mental time. This really resonated with me. I can't just stop thinking about this stuff just because I'm at lunch or at home if I'm working on a hard problem. But I don't get paid for that time.
And yet, is that so bad?
It is when it interferes with stuff you actually care about. Like when I'm supposed be having family dinner or playing with my daughter and I realize instead I've just spent the past several minutes staring into the distance thinking about a work problem.
Sometimes I really envy people who never get the urge to work (either actually or mentally) on work after leaving the office at 5 pm.
Re: Hello, World
#26Today, I will leave behind the digital world that changed me from human to robot, I will begin building a tiny home and I will commemorate almost getting down to this honest days work by blogging about my new-experience-to-be working the soil.
Re: Hello, World
#27Re: Hello, World
#28Programmers can easily resonate to this blog. But I think this is the moment of truth of transition from a programmer to an engineer where you realize you are better off creating something on your own from the ground up than working for someone else's creation.
Re: Hello, World
#29This seems the natural progression for programmers now. 10 year slog of hope decaying; relatively monotonous work, then a sudden urge to do something antithetical in pursuit of happiness. I guess I'll be in a log cabin in Iceland in 5 years time!
it is also interesting how often the pursuit of happiness involves some degree of isolation.
Re: Hello, World
#30You take an incredibly advanced and complex programming language, and dumb it down to the absolute bare essentials in order to embark on the journey of learning a new system. The purpose of the "Hello, World!" program, at least as I've understood it, is to make sure that you can actually get code running with whatever language, frameworks, and build process you have. Printing out a simple phrase is sufficient to demo…
If we're talking about the modern purpose of a "Hello, world!" program, then I agree. However, at the time the idea was originated, and I'm sure for a good time afterwards, build processes and frameworks weren't as mainstream as they are today. Therefore the function of a "Hello, world!" program was simply to test out the basic features of the language. That's the way I see it.