Hacker Newsnew | past | comments | ask | show | jobs | submit | more PerryCox's commentslogin

I personally don't like the Monaco GP due to how big the cars have become making it (nearly) impossible to pass. Still you are correct it definitely is a classic race.

Monaco, Spa, Suzuka, and Monza are some of the best and most iconic tracks in the world.


>I personally don't like the Monaco GP due to how big the cars have become making it (nearly) impossible to pass.

Believe it or not, a modern Formula 1 car has basically the same footprint as a Chevrolet Tahoe

A 2022 Formula 1 car was 5.5 meters, and 2.0 meters in width. Or 11.00 m². By comparison, a 2023 Chevrolet Tahoe is 5.35m in length, and 2.06m in width. Or 11.02 m².

Sure, they only weigh 800kg (1760lbs), but we're basically racing full-size body-on-frame SUVs at this point. I guess we can be glad they're not yet the size of a Suburban, but yikes.


Do you have comparison figures to the F1 cars in the 80s or 90s?


Michael Schumacher's 2000 Ferrari F1-2000 was 4397mm x 1795mm, or 7.89m².

Michael Schumacher's 1995 Benetton-Renault B195 was 4350mm x 1990mm, or 8.66m².

Ayrton Senna's 1988 McLaren-Honda MP4/4 was 4394mm x 2134mm, or 9.37m².

Niki Lauda's 1977 Ferrari 312T was 4143mm x 2030mm, or 8.41m²

Jim Clark's 1965 Lotus-Climax 33 was 3604mm x 1650mm, or 5.95m².


I just knew that the word "iconic" would pop up, I just didn't know where. You had me guessing until the end.

Spa and Suzuka are great tracks. Monaco and Monza are horrible tracks. The only reason they don't remove Monaco is that it has this air of glitter.


Can’t forget Interlagos as far as classic tracks go.


Honestly I don't have any issues with this. Most of my team is in Europe and I'm in America so even before COVID and WFH became the norm, I was still talking to people via Slack, Teams, etc.

I think the best advice I can give is to reach out to people and have normal conversations when you don't need anything. If you only talk to people when you need something from them, they are going to be less likely to talk about things that they have going on outside of work. Talk about anything that they are interested in. Plus the beauty of messaging apps is that people can respond when they have time and if they are busy they can ignore the messages.

Also if you get some downtime in meetings or join early, ask how things are going, what the weather is like, or if they have any weekend plans. There usually is a bit of time before or after meetings where you can still socialize.


Hypothetically, do you think it would be nice if you found out common things you shared with you co-workers right from the start? For example not going 5+ months not knowing that they support the same soccer team that you do. That is 5 months worth of convo that could have happened from the start.

It seems that you are pretty social and take extra steps to build the connections. So, wondering if it would be easier for you to not have to do the leg work and be able to get into the main things you and your co-worker can talk about for hours.


Exactly. I actually call up people when there is downtime and shoot the breeze. We talk about ideas, office politics, anything under the sun. So even though we are all WFHing I was able to bond with my new team this way.


This is a really neat idea! I wonder how close you could get the prose to actually explaining the codes purpose as opposed to just saying "this is a for loop"?


The purpose (intent) wouldn’t be explained, but it could be useful for tools which have oddball syntax and are only used sometimes (infrequent enough for you to forget).


I do the same with my .vim folder. You can place your .vimrc file in there as .vim/vimrc and now everything is backed up in git. I've been working this way for a few years now and can get setup on a new machine in a matter of minutes.


I think Boston Dynamics is the closest to making robots that could actually be useful in real life situations. I would love to develop code for one of these.


There are a number of robotics companies (Savioke, Fetch Robotics, Bear Robotics, MiR, to name a few) that are producing robots that are currently doing work in the real world. I will fully grant that those all require in-advance mapping and fairly level floors, but to me that can fit "real life situations".

Note: I have worked at one of those, and got an offer at another.


But do you see the difference between Boston Dynamics (BD) and {Savioke, Fetch Robotics, Bear Robotics, MiR} ?

BD's robots move using limbs while others use small-er wheels which limits the terrains these robots can be used in.


Because the bigger companies forced them out of business or acquired them.


I think this is a very valid point. There are times when Python is not the absolute best choice for a given problem, but in most cases it can allow you to achieve the desired goal in a way that is easy for newcomers to the particular codebase to grok very quickly.

There are times when it may be better to use another language and there is nothing wrong with that. I default to Python and if I think there will be specific issues with it, then I can look at a more specialized language.


The pawn movement is acknowledged at the end of the first paragraph:

> Pawns are a little weird, but in general they always have to move forward.


Anyone else getting this error? I tried on Debian 9 and MacOS 10.14.6 after installing via pip.

  import reloading
  Traceback (most recent call last):
    File "<input>", line 1, in <module>
      import reloading
    File "/home/lucas.mccoy/.local/lib/python2.7/site-packages/reloading/__init__.py", line 1, in <module>
    from .reloading import reloading
    File "/home/lucas.mccoy/.local/lib/python2.7/site-packages/reloading/reloading.py", line 87
    exc = exc.replace('File "<string>"', f'File "{fpath}"')
                                                         ^
  SyntaxError: invalid syntax


It only works with Python 3. Thanks for reminding me that I should add a note to the Readme.


It does work in Python 2 with the following patch:

    diff --git a/reloading/reloading.py b/reloading/reloading.py
    index 1d28e2f..1a5f981 100644
    --- a/reloading/reloading.py
    +++ b/reloading/reloading.py
    @@ -84,9 +84,10 @@ def reloading(seq):
                 exec(body)
             except Exception:
                 exc = traceback.format_exc()
    -            exc = exc.replace('File "<string>"', f'File "{fpath}"')
    +            exc = exc.replace('File "<string>"', 'File "{}"'.format(fpath))
                 sys.stderr.write(exc + '\n')
    -            input('Edit the file and press return to continue with the next iteration')
    +            print('Edit the file and press return to continue with the next iteration')
    +            sys.stdin.readline()
     
         # copy locals back into the caller's locals
         for k, v in locals().items():


Brilliant, thank you. I'll patch that.


That's an f-string, so it only works with Python 3.7 and later


f-strings were introduced in Python 3.6, fyi:

https://docs.python.org/3/whatsnew/3.6.html#whatsnew36-pep49...


> intelligent anti-vaxxers

No that's an oxymoron if I have ever seen one.


Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: