/**
* Gets the user
**/
fun getUser() {
return this.user;
}
You need the requirements doc from marketing. Then it will all totally make sense for sure. No cap.
Okay now I get the joke.
I hate these kind of people.
By the way, your ``` both need to be on their own, separate line
It renders correctly in my client (Sync), what are you using? I’ll edit it anyway.
It renders correctly on the web as well for me.
But the ``` being on their own line is how to write it properly, as stated this website among many others.
This way, you can put the intended programming language on the same line as the first ```, ensuring proper colour coding!
Ex.
echo "Hello $name\n";
echo "Hello $name\n";
EDIT I checked on mobile, it rendered odd on Jerboa for me:
Now it is fixed:
My comments are just the code that didn’t work but I don’t want to delete yet because I might make it work except I never will be cause I already rewrote it so it does.
Hey thanks for reminding me I made a clock squared in blender about 2 years ago
yes there is an error in the image, and no I’m not telling you where it is
An interesting concept would be if all hand on the 12 clocks would work, but the hands of the clock in the middle are stuck at 12 position, this way the hands in the middle would point to the clock showing the correct time.
What a fun idea!
Is it on purpose that all clocks in this are coupled at the 3 o’clock position? I assume all the clocks go the same speed. Then the large clock and all the smaller clocks at the 3 o’clock position (there are 13 of them) would show the same time. E.g. in one hour, the 12 o’clock position would show 1 o’clock, but the large clock and all the clocks on the 3 o’clock position would show 4 o’clock.
Oh and why is it a clock squared if you have three layers of clocks? Isn’t it cubed then?
I was mainly thinking of making some recursion hence why all the subclocks mirror the parent clock (for that given hour). Also I called it clock squared because I didn’t think the resolution would be high enough for people to actually notice the 3rd level of clocks.
You might notice that some dials don’t really align with the hours they’re supposed to show. That’s because I had to place a bunch of clocks at varying hours with a viewport rendering the parent clock at an angle that probably made it difficult to spot the errors. I rendered it once and didn’t bother re-rendering it once I saw the errors :)
Haha yes, recursion is always fun!
Although I’m still confused on what the clock would show in an hour. Because if the subclocks mirror the parent clock at the given time, then they would all be stuck to the hour they are positioned on? Or if they can move then the sublcocks are coupled to 3 o’clock of the main clock. But well, it is all hypothetical anyways :D
I know I’m probably doing it wrong but this is how I feel whenever I write unit tests
Checked one of mine:
# get path to the download directory
Oh, ok.