HN user

oops

292 karma
Posts6
Comments110
View on HN

I feel like you can't really be considered a staff/principal if you can't already tell ahead of time where the perf bottleneck will be just on experience and intuition.

I feel like you can’t really be considered a Dunning-Kruger if you can’t already tell ahead of time where the perf bottleneck will be just on experience and intuition.

Nice! The visualization makes it easy to compare when cities are in the same hemisphere. It would be cool if there was an option to align the seasons when comparing cities in different hemispheres.

My experience so far has been: if I know what I want well enough to explain it to an LLM then it’s been easier for me to just write the code. Iterating on prompts, reading and understanding the LLM’s code, validating that it works and fixing bugs is still time consuming.

It has been interesting as a rubber duck, exploring a new topic or language, some code golf, but so far not for production code for me.

I've found no other mention of this on the internet

Here's one! (different character, but same issue it seems?)

https://www.reddit.com/r/linuxquestions/comments/1cbarz5/ele...

and I'd love to to hunt this down and fix it but have no clue where to start. I guess the first step would be to consistently reproduce the bug...

I am not familiar with Chromium at all, and I also don't run Linux on the desktop as I'm guessing from your video you do (?) so take this with a grain of salt...

I would start looking at the focus and key event handlers. e.g. maybe log the contents of pressed_keys and/or step thru the code from the beginning of the focus handler. It looks like this might be the place:

https://github.com/chromium/chromium/blob/01ab59ae08a38a361d...

https://github.com/chromium/chromium/blob/de351fd416ec36beeb...

Even if you can't repro it, you may be able to figure out the issue by just reading thru that code with some theories in mind. e.g. Since pressing another key seems to fix it, maybe look at what the code is doing there... my guess is the release event fixes whatever corrupted state it is in upon focus.

The measurements taken by the watch can be viewed over time in the Health app on iOS. Try image searching for "Environmental Sound Levels" "iOS" "Health" to get an idea of how it looks. e.g. here is a screenshot: https://www.idropnews.com/wp-content/uploads/2023/04/Apple-H...

It sounds like this iOS app can write noise levels to the Health app too: https://apps.apple.com/us/app/niosh-sound-level-meter/id1096... so maybe that could let you test drive this if you don't already have the watch.

Some things to think about:

1) You still have a job

2) The company is still in business

3) Just because there was a round of layoffs doesn’t mean there will be more

4) But of course there may

5) But that is always the case, your job is never totally secure

6) If you do not already have a backup plan in place, thank the stars for the headsup to get started on that

7) A plan is a good antidote for anxiety, and in this case may consist of: savings, ability to lower expenses if needed, building and maintaining a professional network, being interview ready

8) Making a decision is another good antidote for anxiety. Decide to stay or decide to leave. If you stay and get laid off, use your plan.

I’m not sure I agree with the suggestion to quit and find another job simply because your company had layoffs. There is no guarantee the new place won’t have layoffs too.

If you don’t already have a network, you have a perfect opportunity to start one here by reaching out to keep in touch with some of the laid off folks.

Every organized religion on earth would disappear within one generation if membership was not passed on through birth.

How long do you think that would last?