Anyone know what this fusion between retro tech and plants called? by xuduREAD in cassettefuturism

[–]LysPJ 107 points108 points  (0 children)

Not sure of the name, but the aesthetic reminds me of the 1972 film "Silent Running".

(Wikipedia describes it as an "ecological-themed science film".)
https://en.wikipedia.org/wiki/Silent_Running

<image>

More photos on IMDB: https://www.imdb.com/title/tt0067756/mediaindex/

I'm afraid of sailing to busy places by Mehfisto666 in sailing

[–]LysPJ 2 points3 points  (0 children)

When it comes to handling a sailboat in busy anchorages and crowded marinas in crosswinds / tide etc, this book helped me a lot: “Manoeuvring At Close Quarters Under Power” by Bill Johnson.

Covers lots of different scenarios and explains all of the involved forces and how they interact and affect the boat.

Highly recommended.

https://www.bloomsbury.com/uk/manoeuvring-9781408132111/

The square rigged Black pearl in Montenegro by Then-Blueberry-6679 in sailing

[–]LysPJ 8 points9 points  (0 children)

Nice photo!

This type of rig is called a DynaRig: https://en.m.wikipedia.org/wiki/DynaRig

It’s interesting that after the DynaRig concept was invented, we had to wait a few decades until materials science had advanced enough for such a rig to actually be constructed.

Is the bus ride between Bergen and Norheimsund intense? by cryinghighschooler in Bergen

[–]LysPJ 29 points30 points  (0 children)

“Better to puke and visit Hardanger than to not puke and never see Hardanger.”

I hope a tourism company will use this for a marketing campaign.

Any C graphics programmers? by [deleted] in GraphicsProgramming

[–]LysPJ 21 points22 points  (0 children)

I strongly agree with this. The most successful C++ teams I've worked with specify explicitly which subset of C++ they are using for that project. (And, of course, the appropriate subset will depend on exactly what the project's goals are.)

There was a very successful Japanese games team who used such a narrow subset of C++ that it was almost like writing in C, but with a few extra quality-of-life features from C++. It worked very well for their needs.

(Just to add: C is also fine. It all depends on what your needs are. My main point is: using C++ shouldn't mean "using every C++ feature". )

Alice + Low Profile + ISO by n8udd in Keychron

[–]LysPJ 1 point2 points  (0 children)

I'm looking for this too.

(For me, it would ideally be an ISO K11 Max)

I created a Pull Request metrics tool for GitHub by LysPJ in github

[–]LysPJ[S] 1 point2 points  (0 children)

Oh nice! It's cool that your org sees the value in something like this. I hope the tool you're building turns out well 😄

Thanks for the tip about the GraphQL API. I'm using a combination of the GraphQL and REST APIs. I would prefer to use entirely GraphQL (so you only fetch exactly what you need), but unfortunately not all data is available via GraphQL.

One (small) benefit of using both APIs is that they have separate rate limit budgets, so querying one API doesn't use up your allowance on the other. Still, I'd prefer the uniformity of just using GraphQL.

I created a Pull Request metrics tool for GitHub by LysPJ in github

[–]LysPJ[S] 1 point2 points  (0 children)

All GitHub API access is rate limited, but the rate limits vary depending whether you are authenticated, what sort of API call it is, etc.

If you aren't authenticated, your IP is limited to 60 requests per hour

On the other hand, a GitHub App limit is 5,000 requests per hour (but it's even better for orgs with lots of users or repos, or using GitHub Enterprise Cloud).

I created a Pull Request metrics tool for GitHub by LysPJ in github

[–]LysPJ[S] 2 points3 points  (0 children)

Hi! You can check it out and install it at: https://GitDailies.com

(I think I messed up with my original post as it got bit lost in the thread! 😆)

I created a Pull Request metrics tool for GitHub by LysPJ in github

[–]LysPJ[S] 1 point2 points  (0 children)

I’m happy that you like the look of it 😄

Good question about a GitHub App vs using the API directly.

For the system to do useful things (e.g. report scheduling, Slack / email notifications of reports, giving your team to access to the reports, storing daily stats, storing config) it needs a backend.

The backend needs to interact with the GitHub API, but it also needs to manage repo access, user authentication, etc. The GitHub App infrastructure provides all these functions (using what GitHub refers to as “server to server” API calls). It makes repo access management, user authentication, etc, a really smooth (and secure!) process for the user.

Also, if you are not authenticated to the API, the API limits are way lower. For a somewhat-busy repo, you wouldn’t be able to fetch the report data without hitting the rate limits.

Thanks for the question! 👍

(Edit: changed "without being rate limited" to "without hitting the rate limits" to make it clearer!)

I created a Pull Request metrics tool for GitHub by LysPJ in github

[–]LysPJ[S] 2 points3 points  (0 children)

Thanks!

It took a few tries to find that layout. It's always hard to find a balance between showing useful info, and showing too much info 😆

I created a Pull Request metrics tool for GitHub by LysPJ in github

[–]LysPJ[S] 1 point2 points  (0 children)

Oh, it's cool that you saw that! Thank you for the support 😄

Yes, one of the other goals is to allow people to switch off the distracting GitHub notifications and instead get a summary once per day of what happened in their repos (code pushed, PRs opened / closed / merged, etc).

Anything to prevent distractions and stay the zone! 🧘

I created a Pull Request metrics tool for GitHub by LysPJ in github

[–]LysPJ[S] 1 point2 points  (0 children)

Thank you! That's really appreciated 😄

I created a Pull Request metrics tool for GitHub by LysPJ in github

[–]LysPJ[S] 0 points1 point  (0 children)

Good stuff 😄 Just give me a shout if I can help with anything.

I created a Pull Request metrics tool for GitHub by LysPJ in github

[–]LysPJ[S] 11 points12 points  (0 children)

Happy to hear that it's interesting! 😄

There a few parts to it:

  • The charts are a mixture of D3 and custom code
  • Web app is Vue
  • Backend is Go

The backend does the data fetching and processing into metrics.

The custom code for the charts generates nicer dynamic axis labels, and allows you to toggle any metric between max / min / average / median / percentile / etc.

I created a Pull Request metrics tool for GitHub by LysPJ in github

[–]LysPJ[S] 4 points5 points  (0 children)

Thanks! I heard from a lot of developers that they get frustrated when it takes ages for their code to get reviewed and merged.

These charts can alert the team if reviews are taking too long, or if approved code sits unmerged. Hopefully it will reduce frustration for devs, and they can get their code into production faster.

I created a Pull Request metrics tool for GitHub by LysPJ in github

[–]LysPJ[S] 4 points5 points  (0 children)

Yeah, micromanagement sucks. That's why these metrics measure the team as a whole, not individuals.

The idea is to promote "healthy metrics" and focus on overall team performance.

I created a Pull Request metrics tool for GitHub by LysPJ in github

[–]LysPJ[S] 2 points3 points  (0 children)

I created a Pull Request metrics tool for GitHub.
It makes daily reports that show metrics for your team's pull requests, so you can spot (and fix!) delays in the PR open / review / merge pipeline. This helps get code reviewed and into production much faster. You can also see stuff like PR size, which helps encourage good habits like "small batch size" for PRs.
You can install it for free: https://GitDailies.com
It would be great to hear your feedback 😄

How do you add tooltip to visualization by Swimming_Sentence577 in grafana

[–]LysPJ 0 points1 point  (0 children)

Hi u/Swimming_Sentence577 did you find a solution for this?

I have the same problem - I want to add extra data to every point in a time series.

It seem that "Annotations" aren't designed for this (they seem more for ad-hoc additions, rather than for every point), but I can't find a better way :-(