"Announcment"
It used to be quite common on mailing lists to categorise/tag threads by using subject prefixes such as "ANN", "HELP", "BUG" and "RESOLVED".
It's just an old habit but I feel my messages/posts lack some clarity if I don't do it π
bahmanm
joined 1 year ago
I didn't like the capitalised names so configured xdg to use all lowercase letters. That's why ~/opt fits in pretty nicely.
You've got a point re ~/.local/opt but I personally like the idea of having the important bits right in my home dir. Here's my layout (which I'm quite used to now after all these years):
$ ls ~
bin
desktop
doc
downloads
mnt
music
opt
pictures
public
src
templates
tmp
videos
workspace
where
binis just a bunch of symlinks to frequently used apps fromoptsrcis where i keep clones of repos (but I don't do work insrc)workspaceis a where I do my work on git worktrees (based offsrc)
Thanks! So much for my reading skills/attention span π
Which Debian version is it based on?
Something that I'll definitely keep an eye on. Thanks for sharing!
RE Go: Others have already mentioned the right way, thought I'd personally prefer ~/opt/go over what was suggested.
RE Perl: To instruct Perl to install to another directory, for example to ~/opt/perl5, put the following lines somewhere in your bash init files.
export PERL5LIB="$HOME/opt/perl5/lib/perl5${PERL5LIB:+:${PERL5LIB}}"
export PERL_LOCAL_LIB_ROOT="$HOME/opt/perl5${PERL_LOCAL_LIB_ROOT:+:${PERL_LOCAL_LIB_ROOT}}"
export PERL_MB_OPT="--install_base \"$HOME/opt/perl5\""
export PERL_MM_OPT="INSTALL_BASE=$HOME/opt/perl5"
export PATH="$HOME/opt/perl5/bin${PATH:+:${PATH}}"
Though you need to re-install the Perl packages you had previously installed.
First off, I was ready to close the tab at the slightest suggestion of using Velocity as a metric. That didn't happen π
I like the idea that metrics should be contained and sustainable. Though I don't agree w/ the suggested metrics.
In general, it seems they are all designed around the process and not the product. In particular, there's no mention of the "value unlocked" in each sprint: it's an important one for an Agile team as it holds Product accountable to understanding of what is the $$$ value of the team's effort.
The suggested set, to my mind, is formed around the idea of a feature factory line and its efficiency (assuming it is measurable.) It leaves out the "meaning" of what the team achieve w/ that efficiency.
My 2 cents.
Good read nonetheless π Got me thinking about this intriguing topic after a few years.
This is fantastic! π
I use Perl one-liners for record and text processing a lot and this will be definitely something I will keep coming back to - I've already learned a trick from "Context Matching" (9) π
That sounds a great starting point!
π£Thinking out loud here...
Say, if a crate implements the AutomatedContentFlagger interface it would show up on the admin page as an "Automated Filter" and the admin could dis/enable it on demand. That way we can have more filters than CSAM using the same interface.
I see.
So what do you think would help w/ this particular challenge? What kinds of tools/facilities would help counter that?
Off the top of my head, do you think
- The sign up process should be more rigorous?
- The first couple of posts/comments by new users should be verified by the mods?
- Mods should be notified of posts/comments w/ poor score?
Interesting topic - I've seen it surface up a few times recently.
I've never been a mod anywhere so I can't accurately think what workflows/tools a mod needs to be satisfied w/ their, well, mod'ing.
For the sake of my education at least, can you elaborate what do you consider decent moderation tools/workflows? What gaps do you see between that and Lemmy?
PS: I genuinely want to understand this topic better but your post doesn't provide any details. π
To be fair, here's the complete paragraph which makes sense:
Vagrant public networks are less private than private networks, and the exact meaning actually varies from provider to provider, hence the ambiguous definition. The idea is that while private networks should never allow the general public access to your machine, public networks can.
1
I am not the author.
https://github.com/galdor/github-license-observer
https://addons.mozilla.org/en-GB/android/addon/github-license-observer/
This is a cool little addon to help you tell, at a glance, if the repository you're browsing on github has an open source license license.
Especially relevant nowadays given the trend to convert previously OS repos to non-OS licenses as a business model (eg Akka or Terraform.)
A happy Labour Day, in advance, to all Canadians & esp. my fellow software engineers.
Looking forward to us getting closer to unionising our wildly wild IT industry.
Got a notification from LinkedIn saying "You're one of the few experts who have been invited to collaborate on ..." I got curious and opened up the link.
Apparently, now instead of professional writers being paid to pen down their, usually, cohesive & authentic views, LinkedIn is trying out the idea of generating content using an LLM and then asking for free editorial services from users in exchange for "badges" π€― π€¦ββοΈ
This is cheap IMO. Even for LinkedIn.
What's happened to the "content team" at LinkedIn!?
view more: next βΊ
Good question!
IMO a good way to help a FOSS maintainer is to actually use the software (esp pre-release) and report bugs instead of working around them. Besides helping the project quality, I'd find it very heart-warming to receive feedback from users; it means people out there are actually not only using the software but care enough for it to take their time, report bugs and test patches.