go-perfguard
woke
| go-perfguard | woke | |
|---|---|---|
| 1 | 6 | |
| 68 | 431 | |
| - | 1.9% | |
| 0.0 | 0.0 | |
| over 1 year ago | 28 days ago | |
| Go | Go | |
| BSD 3-clause "New" or "Revised" License | MIT License |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
go-perfguard
-
How can I learn more about how Go is optimizing/compiling my program? E.g. why certain functions get inlined but not others, why certain things escape to the heap, how much copying is happening, etc.
There's also this tool that you may find interesting: https://github.com/quasilyte/go-perfguard
woke
-
Discussion Thread
They made the GitHub repo woke
- Detect non-inclusive language in your source code
-
For those in DevOps/SRE roles in the gaming industry, what's your typical day like?
On a normal day, I've usually got tasks from our sprint. For example, recently we got a New Relic plugin deprecation notice, so I spent the last couple days porting our build infrastructure metrics from the old plugin stuff to use the more modern AWS Cloudwatch -> New Relic integration, plus did some related misc alert cleanup. The rest of the week I'm probably going to help with some bugfixes on our custom Git GUI. Then next sprint I'm setting up some tooling to help us clean up some problematic terminology in our code to be more inclusive, using stuff like https://github.com/get-woke/woke plus https://pre-commit.com/ probably. And then after that is my turn (I think?) to be "Dev on Duty", just handling whatever emergent issues come up, like build nodes dying or support requests from our team when they ask for help debugging weird build failures or whatever. And then after that we're doing some groovy cleanup and refactoring to help keep our pipeline maintainable. So pretty much it varies wildly.
-
Anons son is different
This
- Woke: Detect non-inclusive language in your source code
What are some alternatives?
go-critic - The most opinionated Go source code linter for code audit.
Comcast - Simulating shitty network connections so you can build better systems.
reviewdog - 🐶 Automated code review tool integrated with any code analysis tools regardless of programming language
Postman - CLI tool for batch-sending email via any SMTP server.
revive - 🔥 ~6x faster, stricter, configurable, extensible, and beautiful drop-in replacement for golint
github-act-runner - act as self-hosted runner
go-ruleguard - Define and run pattern-based custom linting rules.
nilnil - The Golang linter that checks that there is no simultaneous return of `nil` error and an invalid value.
croc - Easily and securely send things from one computer to another :crocodile: :package:
m365-gender-pronoun-kit - Helper scripts and guidance to add a Pronoun field (She/Her, They/Them, He/Him) to your Microsoft 365 tenant and display it in the Microsoft 365 profile card shown in Outlook, SharePoint, Delve...
Hugo - The world’s fastest framework for building websites.