diff --git a/content/links/20200427.md b/content/links/20200427.md new file mode 100644 index 0000000..03b4980 --- /dev/null +++ b/content/links/20200427.md @@ -0,0 +1,109 @@ ++++ +title = "Links for 2020-04-27" +date = 2020-04-27 + +[taxonomies] +tags = ["links", "facebook", "covid", "work", "juniors", "apprenticeships", +"wfh", "management", "teams", "remote", "rust", "tests", "gnome", "tiling", +"webkit", "energy"] ++++ + +Facebook Screwing Contractors, Hire Juniors, Tips on Work-From-Home, Managing +Remote Teams, Generating Rust Tests, Tiling on GNOME Shell, WebKIT Energy +Consumption, Looking for Work, Don't Defend Bugs + + + +# [Facebook Contractors Must Work in Offices During Coronavirus Pandemic — While Staff Stay Home](https://theintercept.com/2020/03/12/coronavirus-facebook-contractors/) + +There is being not-so-nice, being an asshole, and being Facebook. + +While taking a lot of information from everyone on the web, now they are +protecting _their_ people instead of "people who work for Facebook". The idea +is obvious: While we may look nice to our people, paying for stay-at-home +and/or medical help, whoever is not in our payroll must keep the gears going. + +Maybe that's not true. Maybe it is just hearsay. Maybe it's just bad +propaganda. The problem, though, is that Facebook reputation makes this sounds +true. + +# [The future of work requires a return to apprenticeships](https://www.weforum.org/agenda/2019/12/apprenticeships-future-work-4ir-training-reskilling) + +I've been doing this argument at the office (well, both offices, I'm +outsourced, anyway) for some time: Companies may want to have senior +developers 'cause they don't want to train anyone, but there are no senior +developers available around. Why? Because senior developers are either doing +remote work, getting paid in some foreign currency (and heck if the current +exchange rates for the major currencies doesn't make it worth it), or they +have some very comfortable position in their companies. + +So it's time to train people, not look for people with lots of knowledge which +you won't find anyway. + +# [Things I’ve learned from 12 years of WFH](https://typing.lmorchard.com/2020/03/12/things-ive-learned-from-12-years-of-wfh/) + +At this point, everybody knows how to work-from-home, right? RIGHT? + +No? So here are some tips. + +Some of them is almost "well known" at this point -- some of them I've heard a +long time ago -- but I guess repeating is not that bad. + +# [Free eBook “Managing Remote Teams”](https://knowyourteam.com/m/lessons/161-managing-remote-teams/topics/1301-intro-managing-remote-teams) + +Still on the topic of remote work and work-from-home, maybe you're actually +responsible for managing a team that's going to be remote. So not only you +you're working remote, you have to manage a team remotely. So maybe a free +book could help you with some tips on how to do it. + +# [Generate Rust tests from data files](https://blog.cyplo.dev/posts/2018/12/generate-rust-tests-from-data/) + +Using `build.rs` to generate tests -- at least, the easy ones, in which you +have an input and an output. + +# [‘Pop Shell’ Wants to Bring Proper Tiling Window Features to GNOME Shell](https://www.omgubuntu.co.uk/2020/03/pop-shell-wants-to-bring-proper-tiling-window-features-to-gnome-shell) + +A project to bring window tiling to GNOME Shell. + +I've trying a few, including +[gTile](https://extensions.gnome.org/extension/28/gtile/), but never felt +really comfortable. + +Now there is another plugin claiming they can do tiling on the shell. + +It even allows focusing windows using `` + ``, which is one +of the really good things with i3. + +# [How Web Content Can Affect Power Usage](https://webkit.org/blog/8970/how-web-content-can-affect-power-usage/) + +In a world where everything has a battery and almost everything is in the web, +checking how much the pages are using of energy is really important. + +And it seems WebKIT-based browsers have an inspector for checking this. + +# [Career advice for people with bad luck](https://chiefofstuff.substack.com/p/career-advice-for-people-with-bad) + +The times are not happy. Some companies doesn't seem to be able to survive the +slowing of the economy. So better to be prepared than sorry. + +# [Stop apologizing for bugs](https://blog.danslimmon.com/2019/08/02/stop-apologizing-for-bugs/) + +The point is: If there is a bug, or if you're responsible for a bug, don't +find excuses for it to exist. + +I'd go a step further and say "Don't defend bad code". + +Bugs happen, sure. Some of them are not intentional, but if we keep finding +excuses for them -- there wasn't enough time, people were in crunch time, we +were not aware of this requirement -- then we'll never worry about making +things better. + +--- + +This post was built with the help of + +* [Les Orchard](https://toot.cafe/@lmorchard) +* [HN Tooter](https://mastodon.social/@hntooter) +* [Adrian Cochrane](https://floss.social/@alcinnz) +* [Anna e só](https://friend.camp/@anna) +* [Timo Tijhof](https://mastodon.technology/@krinkle)