Open your terminal.
In the root directory run the command:
sudo nano /etc/bluetooth/main.conf
javascript:(function()%7Bvar numbering%3D0001%2ClinkColor%3D%27%27%2CclickOutside%3Dtrue%2CshowDetails%3Dfalse%2Ci%3D%5B%27%23h5o-outside%2C%23h5o-outside *%7Bbackground-color%3Atransparent%3Bborder%3Anone%3Bborder-radius%3A0%3Bbottom%3Aauto%3Bbox-shadow%3Anone%3Bbox-sizing%3Acontent-box%3Bclear%3Anone%3B%27%2B(linkColor%3F%27color%3A%27%2BlinkColor%2B%27%3B%27%3A%27%27)%2B%27cursor%3Aauto%3Bdirection%3Altr%3Bfloat%3Anone%3Bfont-family%3Asans-serif%3Bfont-size%3Asmall%3Bfont-stretch%3Anormal%3Bfont-style%3Anormal%3Bfont-variant%3Anormal%3Bfont-weight%3Anormal%3Bheight%3Aauto%3Bleft%3Aauto%3Bletter-spacing%3Anormal%3Bline-height%3Anormal%3Bmargin%3A0%3Bopacity%3A1%3Boutline%3Anone%3Boverflow%3Avisible%3Bpadding%3A0%3Bposition%3Astatic%3Bright%3Aauto%3Btext-align%3Aleft%3Btext-decoration%3Anone%3Btext-indent%3A0%3Btext-overflow%3Aclip%3Btext-shadow%3Anone%3Btext-transform%3Anone%3Btop%3Aauto%3Bvertical-align%3Abaseline%3Bvisibility%3Avisible%3Bwhite-space%3Anormal%3Bwidth%3Aauto%3Bword-break%3Anormal%3Bword-spa |
Great question. Let me preface this by saying I HATE talking about RSpec best practices. It's irrelevant to shipping software and tends to churn up a lot of long, useless discussion. However, I think it's useful to consider best practices when there is a demonstrable functional (not stylistic) difference between two approaches that can affect maintainability, flexibility, and speed.
One style I see quite a lot looks a bit like this:
# | |
# Himawari-8 Downloader | |
# | |
# | |
# | |
# This script will scrape the latest image from the Himawari-8 satellite, recombining the tiled image, | |
# converting it to a JPG which is saved in My Pictures\Himawari\ and then set as the desktop background. | |
# | |
# http://himawari8.nict.go.jp/himawari8-image.htm | |
# |
-- show running queries (pre 9.2) | |
SELECT procpid, age(clock_timestamp(), query_start), usename, current_query | |
FROM pg_stat_activity | |
WHERE current_query != '<IDLE>' AND current_query NOT ILIKE '%pg_stat_activity%' | |
ORDER BY query_start desc; | |
-- show running queries (9.2) | |
SELECT pid, age(clock_timestamp(), query_start), usename, query | |
FROM pg_stat_activity | |
WHERE query != '<IDLE>' AND query NOT ILIKE '%pg_stat_activity%' |
I was at Amazon for about six and a half years, and now I've been at Google for that long. One thing that struck me immediately about the two companies -- an impression that has been reinforced almost daily -- is that Amazon does everything wrong, and Google does everything right. Sure, it's a sweeping generalization, but a surprisingly accurate one. It's pretty crazy. There are probably a hundred or even two hundred different ways you can compare the two companies, and Google is superior in all but three of them, if I recall correctly. I actually did a spreadsheet at one point but Legal wouldn't let me show it to anyone, even though recruiting loved it.
I mean, just to give you a very brief taste: Amazon's recruiting process is fundamentally flawed by having teams hire for themselves, so their hiring bar is incredibly inconsistent across teams, despite various efforts they've made to level it out. And their operations are a mess; they don't real