jonathanvmv8f @ jonathanvmv8f @lemm.ee

Posts

57

Comments

85

Joined

2 yr. ago

The Emptiness Machine by Linkin Park.

Listened to it for the first time two days ago and kept it going since

This is why ...] better

Sorry, what's the subject of that?

I was just referring to my original question i.e. how I should write comments in my code to explain its working if I have already done so in the code itself

Interesting to see your opinion on how commenting shouldn't be mandatory. I specifically go the extra mile to ensure my code is readable for everyone, by naming my variables and functions to be as self-explanatory as possible and breaking down long expressions to store chunks in variables. This is why I was feeling confused as to what more I could add to explain my code better, though I must admit there are still considerable complex portions in some of my projects that would appreciate similar simplification.

I believe you confused the 'how' of commenting the 'why' with 'why' of commenting the 'why', if that makes sense.

I am already aware of and totally agree with the need to document your code in this fashion for the convenience of others and self. What I am troubled about is its implementation in real life. How does one write comment that explains the 'why' of the code? How would I know if I haven't accidentally written something that explains the 'what' instead or anything that is simply redundant? It seems like this portion is left out 'as an exercise for the reader'.

Asking as a newbie programmer: how do you suggest we write comments that explain the 'why' part of the code? I understand writing comments explaining the 'what' part makes them redundant, but I feel like writing it the former way isn't adding much help either. I mean, if I created code for a clock, is writing "It helps tell what time it is" better than writing "It is a clock" ?

It would really help if someone could give a code snippet that clearly demonstrates how commenting the 'correct' way is clearly better than the way we are used to.

Though I appreciate the reply, I was looking for the difference between a remaster and a remake specifically. I think both of them should mean the same thing essentially.

What is the difference between the former two?

I got my gaming rig recently and played all the releases up to Rogue only this year. I assure you my specs are modest enough and it's just the game that is poorly optimised. Even Watchdogs 2 ran better than this.

Unity was the game I was most hyped for, especially because of its graphics and bigger maps. I even went to speedrun through the last three games to catch with the lore and begin playing it as soon as possible.

Alas, my PC couldn't meet up with the heightened hardware requirements and I had to give up after barely finishing the tutorial with the awful frame rates even with the settings set to minimal.

Thank you so much! I checked that he starred in the show 'Severance' which I just watched recently, which is why I could recognise his face.

Who's the guy in the second panel? I swear I've seen this guy somewhere recently and it's been seriously bugging me

BTW it's cake day for what was supposed to be a throwaway account

The Turkey Devil

1. For Linux enthusiasts, how do you decide which distro you would like to try out next among the plethora of options that are available? The difference I perceive between majority of distros gets smaller the more I try to understand about them.
2. What are the minimum issues I am likely to face using the most beginner friendly distro like Mint for programming and light gaming?
3. How customizable is the GUI in Linux Mint specifically? What if I want a start menu like Windows 10 with the app list and the blocky app tiles? What about those custom widgets I see in hardcore Linux users' desktops?
4. I heard there is no concept of file extensions in Linux. How am I supposed to work on my projects that I imported from my Windows machine that do contain extensions?

Bonus: Who creates those distro icons in color coded ASCII in the system info command in the terminal?

I actually meant the home page of your blog site, but modifying each blog in a similar fashion could also be great if possible, although that may also depend on the type of audience you are expecting that would read them.

A few of these articles genuinely interest me. I may consider reading them whenever I get time later.

I'm not much expert at reading blogs either lol. I think my suggestion as a novice reader would be to include a short piece of intro text at the beginning of the page to describe what topics the blog talks about (maybe sum it in about 1-2 sentences). That way I would instantly get to know if it is something I am interested to read or not.

But then again, I am a novice so I don't know any better 😔

A for effort

I am seeing this comment right after I finished 'Life is Strange'...

Not suggesting any big things here... All I propose is to have the options for toggling the canvas overlays (empty canvas, heat, template) directly within the canvas editing screen instead of putting it in the sidebar, kinda like Google Maps. I think the sidebar version would be preferred in mobiles, so you could make this desktop only.

Alternatively, you could allow the user to place pixels on the canvas even while the sidebar is opened, like the way it was for the first 48 hours of the event. Also ensure the right side of the color palette is not hidden by the sidebar.

Wish, I didnt know you could add direct images as templates. This makes much more convenient