Pablo Virgo @ptvirgo@mastodon.technology

This happens to me a lot:

1. Search for the answer to a tech-related curiosity.
2. Top results are from stack-overflow or their stack-exchange network.
3. The answer no my question is: "closed: because we don't speak of such things."

#stack-overfail

I wanted to know if any of the programs included in my chosen GNU/Linux distribution were funding themselves with #flattr.

There were 46607 programs to check, so I wrote another program to look them up.

It seems the answer is "no."

Not what I expected, but I'm betting we'll reach a point where crowdfunding makes life much better for #foss developers.

Proposition: (If I'm hearing the anti-capitalists right..)

Computer programmer isn't an effective career because "merits."

It's an effective career because the means of production are both difficult to extract and trivial to acquire.

#haskell tutorial - Riding a Bike

Part 1: Newtonian Physics
Part 2: Limitations of the Newtonian Physics Model for Describing Motion
Part 3: ...

Hoping to play with #haskell's Text.Trifecta parsing library on a toy project. I can't seem to make it play nice with unit testing (esp Hspec.)

Is there a normal approach to testing the results of parsers?

#question

Been practicing two minute, off-the-cuff speeches in conjunction with #toastmasters.

Here's one about drama triangles, which are actually useful to know about.

https://soundcloud.com/p-virgo-781714486/karmpan-drama-triangle

If you're in the US and think net neutrality is a good idea, there's another shot at getting it back.

https://www.battleforthenet.com/

Today I got the #edx dev-stack up and running locally. There were about two hours of hurry-up-and-wait.

Looks like my #flattr subscription will be split three ways this month.

1. Wikimedia Foundation (for wikipedia)
2. Keera Studios (a #haskell programmer on github)
3. Some article I read.

We have the tools and resources necessary to reclaim the #libre Internet without turning creators into beggars.

A fellow #toastmaster taught several strategies for giving an impromptu 2-minute speech:

1. Give an opinion and 2 - 3 reasons to justify it.
2. State a problem and show its causes.
3. Offer a viewpoint and elaborate.
4. State a goal and 2 - 3 actions to achieve it.
5. State a problem and 2 - 3 actions to solve it.
6. Identify a process and describe its steps.
7. Break a topic into components and describe them.

noobs:

"Windows is too insecure. I want to #Linux because I hate worrying about malware."

also noobs:

"Curated package managers are too complicated and slow to update. I want to auto-install anything that looks cool on the Internet."

@saramg @Wraptile Thanks for filling me in ..!

Bothers me to find gaps like this.

Seems like the #foss world ought to have the interest and resources to support a flowchart tool and some people to maintain it.

Do #foss people still work with flowcharts?

Using anything more recent than Dia? What do you like?

Some features missing from #git blame.

git blame --passive-aggressive-email

git blame --i-will-end-you

git blame --not-mad-just-disappointed

Summary of my thoughts upon writing my first "real" #haskell program. If you're a programmer who's been thinking about learning Haskell, here's what I found.

https://www.pablovirgo.com/what-it-was-like-writing-my-first-real-haskell-program.html