Result Stocks 22nd Oct 2021-

Right, screw it. Here's a thread on *that* FBLive by Alex Cairnie about #Govanhill. Lets do a watch-through shall we? (Mind, I'm a resident of Govanhill, and a sociologist. I'm also 5'3, and a visibly queer woman so if half his claims are true I should be living in terror)

00:30: Welcomes viewers and uses points out that his videos are only getting attention b/c they're 'horrific'. Directs folk to his Youtube page. So already clout hunting.

1:08: "I've been warned to stay out of Govanhill. I'm a marked man" (proceeds to use a beanie as a disguise)

1:30 "Laughing and joking aside, here's somebodys front garden." Proceeds to show litter and claim its thrown from windows and this is 'common'. I know a handful of streets with litter issues like this, but its neither common nor unique to #govanhill and other deprived areas.

2:10 "Don't be under any illusion I'm only showing you the bad bits" - only shows you the bad bits.

3:45: He's had offers of help, but hes said no because hes not responsible for 'anybody elses safety' Good lord.

5:01: "Its not that bad. But its not all good either" -Correct

6:00: TW: child abuse - He starts claiming to have been contacted by a health professional and told about child abuse 'in the area'. Huge ethical issues here as the 'professional' who has 'been in the game a long time' is reporting to Facebook Dude and not authorities.

🕵️‍♂️ How Google's PageRank algorithm works

The PageRank algorithm gives each page a rating of its
importance, which is a recursively defined measure of importance, based on if important pages link to it.
It's recursive because the importance of a page refers back to the importance of other pages that link to it

Here's how it works in practice:
1⃣ We start with some pages and crawl them for links

2⃣ Each page has 1/N points (where N as the total number of pages)

3⃣ Add points to each page for the amount of links to it, divided by the number
of links emanating from the sources of these links

A thread on HN about bad code in legacy projects both makes me think how little we've learned as a discipline over the years and, honestly, how little credit we give ourselves for some pretty major

Fun going down this list and thinking: "Hmm, plausible at a well-run modern software shop", "Hmm, possible, but requires implausible tradeoffs", "Literally disallowed by languages", and "If you were to attempt doing that our test suite wouldn't let you merge."

I think we as an industry celebrate (not quite the right word) failure too much and don't celebrate success nearly enough. There is no DailyWTF for competent execution, word of which generally stays pretty local to the source while incompetence passes into legend.

Alrighty let me try to thread the needle on being the change I want to see in the world while not giving away anything that will get me in trouble:

Ruby has wonderful developer ergonomics. Typed languages are easier for machines to guarantee the correctness of. We built a type checker for Ruby (and I believe it is slated for OSS release sometime).

c.f.

🎉🎉 PHP 7.3 is here!

Here are the things I'm excited about.

🚂 Trailing commas in function/method calls!

This will certainly be a required styling choice for me. Same delightful benefits of trailing comma in multi-line PHP arrays, and JavaScript objects.

🧵 Less disgusting heredoc syntax!

Inlining heredoc strings in any way right now is grrrosssss. Now we get sensible capabilities. Everything that was wrong with it is now fixed!

(Ignore the bad syntax highlighting)

☠️ Finally, not-so-silent json_decode error detection!

This really sucked before, now it just sucks a bit less (who wants to pass a 4th param and pass 2 default params first? (helper function anybody?)

📜 Not horrible functions for getting the first and last item (or key) from an array!

Before you either strung a bunch of functions together or messed with internal array pointers. This is a much-needed improvement.