tech

2021-01-08 · open the original ↗

• WinForms on .NET Core is useless without its drag-and-drop designer. Campbell, an architect in .NET tooling, says WPF developers often write XAML by hand and use the designer as a preview, but WinForms culture is built on the designer; WinForms was ported to .NET Core 3 and the designer, which works in Visual Studio today, has been brought online gradually.
• The designer builds a live, uncompiled form from InitializeComponent. It creates the form's base type, then turns the InitializeComponent code into a CodeDOM model and deserializes that again into real objects through reflection. What the user sees is a real form under a transparent window, the "sneeze guard", that captures clicks for dragging and dropping.
• The designer must run out of process on the target .NET. Visual Studio runs on .NET Framework, so objects created there would miss new .NET Core APIs; the form is created in a separate .NET Core process and its window parented into Visual Studio across processes, which he says invites deadlocks. The team is also making APIs that were synchronous since .NET 1.0 asynchronous, anticipating a possible network boundary with something like GitHub Codespaces.
• Data tooling and third-party controls are the unfinished parts. The data sources window, which loads assemblies and creates instances by reflection, does not work yet, so setting up data binding through it does not either. Control vendors face significant breaking designer API changes: modal editing dialogs must live in Visual Studio while their UI logic runs in the other process, which for Campbell meant refactoring thousands of lines out of click handlers in Microsoft's own dialogs.
• WinForms persists through skill sets, legacy code and sheer ease. Campbell cites about eight years as the only .NET desktop framework before .NET Framework 3 around 2006–2007, its simplicity for quick tools, and XAML being a "mind flip" few even at Microsoft knew. He says Microsoft has built four or five UI frameworks on .NET since he joined, about 14 years ago from DevExpress, while WinForms stayed the fallback shipped with Windows. The host says control vendors tell him they still sell far more WinForms controls than controls for other platforms.

2021-01-06 · open the original ↗

• Azure Storage Explorer is a free Microsoft desktop tool. Giard downloads it from azure.microsoft.com/features/storage-explorer and installs it with the defaults; the version shown came out in December 2020. It can connect to a local storage emulator or to storage accounts in the cloud.
• A connection string is Giard's simplest way to connect. Of the several connection methods, he copies a connection string from the storage account's Access keys in the portal and gives it a display name. The account then shows nodes for blob containers, file shares, queues and tables, and changes made in the tool show up in the portal's in-browser storage explorer, and vice versa.
• Blob containers support uploads of files or whole folders. Giard creates a container, uploads a file and then a folder of two text files; a refresh may be needed to see them. Opening a blob downloads it and opens it in the program registered for its extension, and blobs can be multi-selected for deletion, copied, and inspected for history and statistics.
• Table entities need a partition key and row key. The combination must be unique within the table, and other properties can be typed, such as integer or Boolean. Entities can be added one at a time or imported from a CSV, whose rows need not share the same properties, then edited, deleted or exported back to CSV.
• Its main advantage is juggling several storage accounts. Giard says the portal means separate tabs or constant switching, while in the Explorer multiple accounts are each a click away.

2021-01-05 · open the original ↗

• The kit is a complete computer built into a keyboard. It is a Raspberry Pi 4 with its ports moved to the back. The $100 (MSRP) kit includes the keyboard unit, a USB-C power supply, the official mouse, a roughly 250-page beginner's guide, a micro SD reader, a 3 ft micro HDMI cable and a 16 GB card preloaded with Raspbian. Inside are 4 GB of RAM, a 1.8 GHz quad-core 64-bit CPU and wireless. On the back are Ethernet (the host is unsure it is gigabit), two unlabelled micro HDMI ports, two USB 3.0 ports, one USB 2.0 port and GPIO. It has no power switch.
• It plays HD video well but is no media PC. It is claimed to play 4K video, but the host found 4K playback stutters, so he would not use it as a 4K media PC. Full-screen 1080p YouTube played fine, although it was sluggish to get started compared with a desktop PC. Setup took him through a first-boot partition resize and a wizard covering locale, the default password, screen black bars and Wi-Fi.
• He recommends it as an all-in-one beginner's learning computer. He finds it friendlier than a bare Pi board, which needs a case and other parts gathered separately: this needs only power and a monitor. He suggests it for learning to code and the GPIO, or for email and web browsing.

2021-01-05 · open the original ↗

• GitHub Actions is an alternative to Azure DevOps pipelines, tied to GitHub. Benkovich, a consultant who helps clients move applications to Azure, says both script build, test, packaging and deployment steps in YAML; Azure DevOps pipelines can work with code in Bitbucket, GitHub, Team Foundation and elsewhere, while GitHub Actions requires the code to be in GitHub.
• Right-click publish works but is not repeatable. Clicking through the publish dialog, which the host notes has been in Visual Studio for about 10 years, is hard to repeat or hand off. A preview setting in Visual Studio 16.8 or later, "GitHub Actions support in publish", lets the same publish wizard generate a GitHub Actions workflow instead, so every commit to the chosen branch triggers the deployment.
• The generated workflow deploys without the developer writing YAML. In his demo the wizard downloaded the Azure publish profile, stored its credentials as a secret in the GitHub repository, and created an editable workflow file in the repo; after a commit, the build and deploy to Azure ran in about a minute. His point is that "I don't have to be a DevOps engineer to do this"; the feature works only with GitHub today, and he speculates it may someday come to Azure DevOps pipelines.
• The generated workflow can be extended with marketplace actions. He added a third-party replace-tokens step before the build that injects GitHub variables such as run ID, run number and commit SHA into a CSHTML page, and uses the same idea to stamp dates and versions on his documentation. Visual Studio's editor does not connect to the actions marketplace, but editing the workflow file on GitHub offers IntelliSense over marketplace actions.

2021-01-01 · open the original ↗

• .NET Conf exists to hand the community a microphone. Lozano, its executive producer, says it shows .NET through both the product team and the community, and 2020 was its 10th year. It began in 2010 as MVC Conf, became ASP Conf, and was renamed .NET Conf three or four years in at Scott Hunter's suggestion. Day one is product team from 9 to 5 Pacific. From 5 p.m. Pacific on day two, community speakers run around the clock for 24 hours, with hosts taking shifts near each region's time zone; 2020 drew many speakers from Africa and Asia.
• They ran a virtual conference a decade before 2020 made it normal. In 2010 it ran live on Live Meeting, whose rooms were capped at about 1,400 people, a cap they exceeded during a Hanselman keynote. Bandwidth was the main problem until two or three years ago, so speakers also recorded locally with Camtasia, and some sessions, such as one from a speaker in China, were pre-recorded.
• Browser-only streaming makes presenting virtually as easy as on stage. For 2020 Channel 9 produced the event on StreamYard, which uses WebRTC in the browser and needs nothing installed, and restreamed it to YouTube, Channel 9 and other feeds. Lozano's reason is that developers are finicky about installing software, and asking them to configure a tool like OBS raises the bar to present far above plugging into a projector.
• A keynote crashed an under-scaled host, prompting a move to Azure. During a Scott Guthrie keynote, the third-party server hosting the event's web page with the embedded Channel 9 player buckled under the load and returned 503s. It took about 15 minutes to fix with more RAM and a reboot. People already watching kept the stream, but nobody new could get in, and the event moved to Azure the following year.
• Presenters' failures should be met with kindness and preparation. Lozano tells speakers that errors happen and their content can be collected later, because the schedule cannot wait for a fix. After a chaotic 2019, he booked 15-minute tech checks back-to-back on two days, from 7 a.m. to 6 p.m. Central, two to two and a half weeks before the event, plus a day for stragglers, and did 65 of them. He says the conference takes first-time presenters and works with them.

2020-12-30 · open the original ↗

• Wi-Fi 6 is worth buying new, but rarely worth a forced upgrade. The host says its gains are in capacity in dense environments, not speed to one client: a home with 20–30 devices will see little over Wi-Fi 5, one with 50–100 might. He would go Wi-Fi 6 for a first UniFi purchase, to replace pre-802.11ac gear or ISP-supplied Wi-Fi, or to replace access points three to four years old.
• The rated aggregate throughput is one no client will ever see. The 1.5 Gbps figure is 1.2 Gbps on 5 GHz (2x2 MU-MIMO) plus 300 Mbps on 2.4 GHz (2x2 MIMO) added together, and the U6-Lite's only uplink is a single gigabit Ethernet port, so the host says even a perfect environment will not reach it.
• The U6-Lite reuses the nanoHD's form factor, but it is indoor-only. At $99 MSRP (U6-Lite-US), it takes the nanoHD's mounting bracket and skins, runs on 802.3af or 48 V passive PoE at 12 W maximum, and is rated -30 to 60 °C, but it has no weather seal. Ubiquiti recommends ceiling mounting for dense client loads and wall mounting toward the area you need covered for range.
• In the host's tests the U6-Lite beat the 3x3 UAP-AC-Pro throughout. Testing one access point at a time in the same wall position, with four Intel AX200-based clients, he measured it about 50–100% faster in iperf. Some Windows clients got more than twice the throughput on OpenSpeedTest, and four clients downloading at once together reached 213 Mbps against roughly 163 Mbps on the AC Pro.
• Aggregate throughput collapsed when four clients downloaded at once. A desktop that reached about 650–700 Mbps alone was one of four machines totalling only 213 Mbps when all pulled files simultaneously, with all clients on 802.11ax. The host suspects the overhead of scheduling packets to several clients on a 2x2 access point, and expects the 4x4 U6-LR to do better.

2020-12-23 · open the original ↗

• Unit tests should replace hot-reload checking in Blazor. Charbeneau, a Progress Software developer advocate for Telerik UI for Blazor, calls the design-time loop Blazor's weak point: because the app must recompile, saving a change reloads the whole browser tab rather than re-rendering just the edited component as JavaScript hot reloading can. Developers who check their work by eye in the browser are doing manual tests that are never saved; unit tests give the same fast iteration and also remain as regression tests for the life of the application.
• bUnit tests rendered components by comparing HTML semantically, not as strings. He says whitespace or class attributes in a different order do not fail a test, and the library has helpers for button clicks and for checking single attributes, such as that accessibility attributes are present. The tests run without loading the app in a browser. bUnit covers the UI only, and it can also test several components together, such as cascading dropdowns with a mock behind them.
• The whole test suite can be C#, written in one style. Back-end and shared logic go in xUnit or NUnit, components go in bUnit, and services can be mocked with JustMock, a Progress product with a free option, so no HTTP calls hit a real back end. He contrasts this with Angular or React, where validation written in a C# API is rewritten in JavaScript and tested in TypeScript under Jest and its configuration files.
• bUnit does not remove the need for end-to-end tests. He names Selenium and his employer's Telerik Test Studio, whose recorder lets a QA tester point and click to build functional tests in C#, then run them on Edge, Chrome and Firefox, with screenshot comparison, OCR of rendered PDFs and responsive-design checks. Such tests are slow, so he places them before a release, and xUnit and bUnit during coding; with all three tiers he calls an application "pretty much bulletproof".

2020-12-18 · open the original ↗

• Hand-drawn slides revived his speaking when he felt ineffective. Neal says that around 2015 he was burnt out and thought about taking a year off, because audiences were kind but did not seem to act on his talks. A YouTube talk at Google by Dan Roam, author of Show and Tell, on simple stick-figure illustration led him to draw slides for a new Kanban talk at Orlando Code Camp with a cheap stylus and an old iPad. He says he knew within minutes that it was a game changer: the audience was more engaged.
• Drawing a slide fixes what he will say, so he needs no notes. He likens it to handwritten school notes that bring back more detail than they contain: while drawing he thinks through his points, and when the slide comes up he recalls them, so he uses no bullet points. His workflow is to export each drawing as a transparent PNG onto a plain white PowerPoint slide, mostly in black and white for the best contrast on an unknown projector.
• The drawing app mattered more than the hardware. He uses an iPad Pro and Apple Pencil, though he says any recent iPad now works, with Sketches Pro for slides (its pens improve his poor handwriting) and Procreate, which has a steeper learning curve, for avatars, stickers and swag. He used a Surface Pro for three or four months and found the pen good but the Windows drawing apps far behind at the time; today he would pick Adobe Fresco or Concepts.
• Practice, not natural talent, is what builds the skill. Neal is self-taught and draws 10 to 20 minutes almost daily, as writers write every day, and says his style emerged over time rather than by design. He studies drawings he likes the way a developer reverse-engineers an app, by asking how he would reproduce them with his own techniques. He tells anyone starting a craft that with patience and practice they will be surprised by their progress in six months or a year.
• A pretend Twitter sale turned drawing into a paid side business. Around Christmas 2017 he offered avatars for $20 or $25 as if he normally charged $30 to $40, though no one had paid him before. He was filling orders into early February and refunded some unhappy buyers, and the proceeds bought him a new iPad. Since then he has drawn stickers, t-shirt designs and conference artwork, including work for Connect.Tech in Atlanta used across its venues.

2020-12-14 · open the original ↗

• Data engineering is a new role still being formally defined. Bunting defines it as moving data from disparate sources into a common store, in Azure usually a data lake, then cleaning, transforming and joining it so data scientists and analysts can use it. Hulen says it takes over much of the database administrator's data work, and that he went through a job task analysis with Microsoft the month before to define the role for new training and certification. He grounds the demand in his figures that 90% of today's data is unstructured and 90% of the world's data was accumulated in the last two years, and in the "four Vs": volume, variety, velocity and veracity.
• Synapse Analytics is more than a bundle of existing Azure tools. Hulen describes it as one web-based workspace for data engineers, scientists and analysts. It combines dedicated SQL pools (the successor to Azure Data Warehouse), serverless Spark pools, serverless SQL pools that extend PolyBase from SQL Server 2016, Synapse pipelines built on Azure Data Factory's code, and Power BI. When the host suggests it is a repackaging, Bunting says the tight integration makes it a new product: he can query lake files in T-SQL without a database, and use a dedicated pool for heavy reporting, which can be paused because compute is separate from storage.
• Synapse Link gives analytics on Cosmos DB without spending its resource units. Hulen says heavy analytical queries against Cosmos DB's transactional store can be prohibitively expensive. With Synapse Link, a hidden columnar analytical store in Parquet format is kept automatically, replacing the manual change-feed-to-data-lake approach, and can be queried from Spark or T-SQL. He says this is available only with Synapse.
• Versioning data means keeping a copy of every enrichment stage. Bunting says they almost never work against the source system: they copy raw data into the lake in a format close to the source (XML, CSV, JSON), then write each transformation to its own folder level, with file- and folder-level permissions to keep users out of the raw data. Hulen adds that Synapse Studio had just gained Git integration, which he noticed the week before, so pipelines, notebooks and SQL files can be committed and branched as JSON or YAML artifacts.
• Data engineers should stop using SQL for everything. Hulen says Python and SQL are the main languages, and that Python's open-source libraries can do in one or two lines what takes dozens in SQL; the guests' firm, Solliance, develops Synapse training for Microsoft and stresses this mindset shift. Bunting points to C# in Synapse's Jupyter notebooks for .NET developers, and to notebooks being pre-connected to the data lake, where Databricks needs account keys and configuration first.

2020-12-12 · open the original ↗

• The label's product number tells Word the whole layout. Hanselman uses Avery labels he reads as 8660; picking that vendor and number under Mailings > Start Mail Merge > Labels sets the label size and how many fit across, so note the number on the package first. He presents the video as a remake of a 2008 blog post he says is still one of his most-asked-about.
• The address list is an Excel sheet with a header row. Columns are name, address, city, state and zip; in Word he chooses Select Recipients > Use an Existing List, picks the sheet, and confirms that the first row contains headers.
• Design one label, then propagate it with Update Labels. After connecting the list, Word shows only "Next Record" placeholders, which he calls the confusing part; he builds the first label from Insert Merge Field entries, using Shift+Enter instead of Enter for tighter line spacing, and Update Labels copies it to every label. Preview Results then shows real addresses.
• Test one page before burning through a sheet run. He checks the printer's marking for which side prints, loads the labels face up and square in the tray, and prints a single page first so a wrong orientation does not waste hundreds of labels.
• Only Finish & Merge performs the actual merge. Printing from the design screen prints the merge commands, so his test page came out as "Next Record" text; Finish & Merge > Print Documents produces the real addresses, and he says he could have limited that to record one for the test.

2020-12-11 · open the original ↗

• UniFi Access needs a UDM Pro and an 802.3bt switch. As of December 2020 the UDM Pro is the only platform that runs it. The Access Hub draws up to 40 W because it powers the readers, a G3 Flex camera and a 12 V lock, and only a few UniFi switches supply 802.3bt; the host used an XG 6 PoE. He tested on UDM Pro firmware 1.8.3 with Access 1.2.25.
• The $499 starter kit is the sensible buy, at one per door. It holds the hub ($199 alone), the Pro reader ($299), the Lite reader ($99) and 20 cards ($40), and one hub serves only one door. The host's own estimate is $1,000–1,500 per door with labour and lock hardware, excluding the UDM Pro and switches, which he thinks is in line with other access control systems.
• Doors keep working when the hub loses the controller. The host unplugged the switch from the UDM Pro, and cards and visitor passes still opened the door, so access rules live on the hub. Swipes made while it was offline were stored and uploaded once it reconnected, so a UDM Pro reboot or maintenance window does not lock users out.
• The security weak points are physical and network, not software. The hub must be locked away because flipping one wire between NC and NO opens the lock, and a maglock opens on power loss, so it needs battery or generator backup. A UK security consultant who wrote in warned against maglocks on fire-linked exterior doors and favoured door strikes. The host adds a segregated VLAN with no internet access.
• The host rates it a strong first release for small sites, not enterprise. He would use it for a retail store or small office with a few doors, given the network expertise to segment it. His gripes are software: holidays are all-day or nothing, so no half days; expired visitor cards are not returned to the pool; and editing existing users in the portal failed for him.

2020-12-08 · open the original ↗

• Replacing ISP equipment came first; an extra access point fixed the dead zone. At a family friend's house the host put the Comcast modem in bridge mode behind a UDM, which left one lower-level room without Wi-Fi. A roughly 120 ft outdoor cable run along the existing coax to a spare UAP-AC-Lite took just over three hours and gave 66 Mbps down and 5 Mbps up where there had been nothing.
• Off-the-shelf Wi-Fi 6 desktops were scarce and overpriced for testing. Best Buy had none with Wi-Fi 6. At Costco the host bought a Lenovo Legion T5 for $699, down $200 from $899, with a GTX 1660, a 256 GB SSD and a 1 TB drive. He later regretted it, after finding two spare PCs and ordering Wi-Fi 6 PCIe cards, since he says Wi-Fi 6 USB adapters did not yet exist.
• The host hires out large cabling jobs to licensed electricians. He says he is not certified in low-voltage electrical work and handles only small runs himself. His kit for those includes a Platinum Tools pass-through crimper he rates highly, a rotary stripper for outdoor Cat6, a spare access point, a cheap gigabit switch and a USG. He prefers screw-in cable clamps because nail-in ones work loose over time.
• A nanoHD in a hot attic should stay within its rated temperatures. The host mounted one on a rafter at home and cites a rated range of 14–158 °F, against an attic he expects to reach 120–130 °F in summer. A pre-made 10 ft cable fell about a foot short, so he made one up to a keystone patch panel instead.

2020-12-08 · open the original ↗

• An IP address is a phone extension, unique only within its network. Hanselman starts offline, with "name not resolved" in the browser and an instant ping failure, and uses ipconfig to show there is no address; after joining his demo Wi-Fi he gets 192.168.3.109. Addresses like 192.168.x.x or 10.x are reserved for inside use, like movie 555 numbers, so viewers can have the same one.
• Addresses are leased, not owned. His phone showed a 12-hour lease, and after a disconnect his laptop happened to get .109 back, which he likens to a phone store reissuing your old number or not; a static lease pins a device to one address.
• The default gateway is the router and the only way out. The router has a LAN side inside the house and a WAN port (usually yellow) outside, and its LAN address (192.168.3.1 here) hosts its admin page. His laptop, Raspberry Pi, iPhone and Apple Watch could all join and see each other, but nothing reached the internet until the WAN port was plugged in; he chained this router behind his house router, where its WAN address was 192.168.1.142. He also recommends wired over Wi-Fi for reliability and changing the router's default password.
• DNS turns names into numbers, and you can check its answers. The router runs a local DNS server that caches answers and falls back to upstream servers; nslookup against 8.8.8.8 (Google) or 1.1.1.1 (Cloudflare) should return the same address for a site. The hosts file under Windows\System32\drivers\etc overrides DNS, which he uses to point local.hanselman.com at 127.0.0.1 while developing, but he warns an entry for something like google.com could silently misdirect you.
• You need not use your ISP's DNS. He says some ISPs practise DNS hijacking, sending mistyped names to their own search page; he runs a Pi-hole, a Raspberry Pi acting as DNS server that blocks advertising, and says it blocks about 10% of his household's traffic. His demo router runs OpenWrt.

2020-12-03 · open the original ↗

• Students get the problems a company would give a new hire. Cooper, who has worked at the Illinois Science and Technology Institute (ISTI) for over six years, says companies in its STEM Challenge, run since the 2013–14 academic year, are asked what a project team hired tomorrow would work on, not what would be fun for students. This year 13 companies across Illinois are each paired with up to four high schools: 20 schools (usually 18 to 25) and about 900 students. Over a semester, company mentors work with students each week on an open, interdisciplinary problem with no right answer, using design thinking, which she says builds communication, teamwork and deadline skills.
• The program values process over product, so mentors flag unworkable ideas. Problems this year include reusing coal ash for an energy company near East St. Louis, medication adherence, safer sensor-equipped construction sites, and challenges from Northrop Grumman and the new partner John Deere. She says students tend to jump to apps, but one team working on the patient journey for adults with Alzheimer's built a board game instead, and students in Williamsfield, near Peoria, worked with a solar company on what is now a solar energy community there.
• The program targets students underrepresented in STEM. Cooper says about 75% of students tell ISTI's yearly evaluation that it is their first ongoing contact with a professional ("you can't be what you can't see"). The end-of-year showcase is not a contest, both because competition was found to put off underrepresented students and because different industries' solutions cannot be compared; one team per school presents.
• Schools wait on a list, and the limit is companies. She says demand from schools exceeds supply, so ISTI recruits companies near schools it wants to reach and in regions it does not yet serve, such as Moline and Rock Island, new this year. Each company commits mentors to weekly contact for a semester. Teachers commit to a year-long process: professional development in the fall, planning, mentor training, then work in earnest from January.
• An existing mentoring platform made the pandemic pivot small. Its Mentor Matching Engine, built in 2012, connects students and background-checked mentors by discussion and video, with a teacher in every project. With it this year's kickoff, company site visit and final presentations, the usual three or more in-person events, went virtual along with training and the showcase. It also runs as a separate program where students pick their own research projects, which she puts at 23 high schools and over a thousand students.

2020-12-03 · open the original ↗

• A Raspberry Pi 4 no longer needs beta firmware to boot from USB. The host says much of the online guidance, which calls for a beta bootloader, is out of date. An up-to-date Raspbian install can be copied from the microSD card to a USB 3 drive and set to boot from it.
• Use an SSD or SATA M.2 drive, not a thumb drive or NVMe. A flash stick is little more reliable than the microSD card it replaces. The M.2 enclosures he shows, including the Argon One M.2 case, accept SATA M.2 drives but not NVMe. His first Argon USB 3 jumper was faulty, and an ordinary short USB 3 cable worked in its place.
• Copy the card to a blank drive, then set USB boot order. Delete any existing partitions on the target in GParted, clone the card with SD Card Copier, and choose Advanced Options > Boot Order > USB Boot in raspi-config. Then shut down, remove the card and power on; the Pi waits about 20 seconds for the card before booting from USB.
• Update the Pi before copying, or the boot-order setting fails. The boot-order option returned an error until the host ran apt upgrade, which also moved it from Boot Options to Advanced Options. Anything installed on the card after the copy, such as hdparm, is missing on the drive and has to be installed again.
• External storage was far faster than microSD in a quick hdparm read test. The microSD card read at 44.5 MB/s, a 2 TB Seagate USB SSD at 108 MB/s, and a 128 GB SATA M.2 drive at 347 MB/s. The host calls this a rough before-and-after check, not a rigorous benchmark.

2020-11-25 · open the original ↗

• Remote teaching needs more communication bandwidth and less friction. Kellerman, a senior lecturer in mechanical engineering at the University of New South Wales teaching classes of 300 to 500, demos a setup that joins one Teams meeting from three devices and switches XSplit scenes (camera, full-screen PowerPoint with ink, OneNote worked examples, a physical beam held in front of the slides) with a Logitech remote mapped to hotkeys. He says moving to a dedicated space for classes, rather than one chair all day, restores the intentionality of walking to a meeting room.
• Digital delivery can bring every student to the front. In his account, students solve a free body diagram on paper, post a photo to the Teams chat, and he taps each one on his big touch screen and critiques it moments later, with students in Mongolia, Italy and the US. He argues it is easier to get 500 people to the front of a class virtually than in a lecture theatre.
• Students can take lab measurements in augmented reality. With students barred from the lab, his team made a 3D capture of the lab and digitized and animated an experimental rig inside SharePoint Spaces, then in private preview, so students take measurements from the rig instead of watching a video.
• These setups should become buttons for ordinary teachers. Kellerman says engineering's job is democratizing the possible, and that the hardware cost is justified: a Microsoft contact told him a cubicle costs $9,000 per employee per year, so equipping home workers amortizes in a year. Hanselman adds that switching webcams through device settings is enough friction to stop an average teacher.
• Integrating separate apps is, he predicts, the next decade's frontier. His example: a bot searches the machine-generated, time-indexed transcript of a recorded Teams lecture and answers a student's chat question with a link to the moment, say 53 minutes 22 seconds in. He did not code it; Sydney firm Antares Solutions builds his ideas, and he says knowing what is possible and learning what you need is what an engineering degree teaches.

2020-11-24 · open the original ↗

• Teach cloud concepts, not the names of products. Hanselman says Azure is usually introduced as a diagram of services to memorize, and that moving a machine from under your desk into a cloud VM ("lift and shift") gets none of the cloud's benefits. He uses Azure as the example but says the concepts hold for any cloud.
• Every service ultimately rests on storage and virtual machines. A VM does not know it is virtual, and a byte written to cloud storage is copied several times, possibly worldwide. That storage may be slower than a desktop SSD and need not sit next to the VM, so disk-heavy code in Chicago should not be talking to storage in Ireland.
• Higher layers hide the VMs but do not remove them. App Service, containers, Kubernetes and serverless functions ("think about your servers less") all run on VMs someone else patches; he walks this up a "Pizza as a Service" chart from on-premises to SaaS. Even with a provider's SLA (five nines is about five minutes of downtime a year), making a site resilient stays the architect's responsibility.
• Knowing what is underneath lets you pack it tighter. An App Service plan is a VM, and he calls one app per plan a fundamental misunderstanding. His $32-a-month, 2 GB basic Windows plan runs six sites at about 60% memory, his Linux plan runs his blog, home page and podcast at around 12% CPU, and he can scale up or drag a slider to scale out.
• Cloud observability gives one person an IT department's tools. On basic plans with out-of-the-box Application Insights he sees response times, availability tests, costs (about $400 in his dashboard) by resource, and failed requests that show bots probing his non-WordPress, non-PHP blog for PHP files. Azure Front Door routes hanselman.com and /blog to separate app services, configuration he says once took flown-in specialists.

2020-11-23 · open the original ↗

• Treat ADHD as traits to manage, not a yes-or-no diagnosis. Kergosien says the clinical definition dwells on the negative (he cites the DSM-5 as requiring several, he thinks five, areas of impairment for at least six months), whereas his talk asks which tendencies go with this kind of brain and when each helps or hurts. Knowing yourself, and re-checking that as you learn more, lets you choose your situations; if your efforts never fix a struggle such as mundane tasks, he says that can free you to look for a different job or activity.
• The same ADHD traits can be strengths in the right setting. He lists hyperfocus alongside distractibility; an "out of sight, out of mind" form of object permanence that he says could even make losing a loved one less difficult; a fearlessness he says is common among successful entrepreneurs; and a brain that notices more around it, which distracts but also feeds intuition. He suggests some people work late at night simply because there are fewer distractions.
• Lean harder on lists and reminders than most people do. Kergosien says people with strong ADHD often end up using project-management techniques on their own lives, which for him led into leadership roles, and that checking items off supplies a reward that helps build the habit. He was diagnosed borderline as a child and again as an adult, and takes his prescribed medication selectively because it makes him worse at observing his surroundings and switching tasks; he also decides in advance, the way someone with alcoholic tendencies avoids the bar, not to start an absorbing project when he will need to stay alert.
• Rein in perfectionism by defining "done" before starting. He says the urge to make everything 110%, which developers call gold plating, leads him to take on less so as not to spread himself thin. His remedies are breaking work into micro tasks, setting milestones that mark when a task meets its needs, and routine check-ins, such as every few days on a month-long task or every 10 minutes on an hour-long one.
• Explaining the struggle turns a frustrated partner into an ally. Kergosien says he could walk past a full trash can 20 times without once thinking to take it out, which his wife read as not caring. Talking it through did not remove the difficulty, but it let her help rather than assume, and he says both benefited.

2020-11-22 · open the original ↗

• The healthcare cloud bundles existing services around an interoperability standard. Naik, a Microsoft data and AI specialist for health customers, calls Microsoft Cloud for Healthcare the company's first and only industry cloud: Dynamics 365, Power Apps and Teams on the common data model, using Azure's FHIR service as a standard, API-accessed schema so payers, providers and processors can share records. He names Epic as the first customer, using Teams with its application for telehealth; on the host's paraphrase, he agrees that Microsoft supplies the raw tools and partners assemble the solutions for each provider.
• COVID raised hospitals' costs while cutting their main revenue. Naik says elective surgeries, where most hospitals make their money, fell by 70%, while costs rose to treat COVID patients and protect caregivers. He presents the product as Microsoft's answer: better patient engagement, coordination of care teams, and operational insights, within Azure's HIPAA and HITRUST certifications; he also claims Azure has the highest market share in healthcare.
• The health bot already runs a public COVID symptom checker. Naik says the CDC website's symptom-checker bot is built on Microsoft's bot framework. Providers can also use the health bot to schedule patients' next appointments and to work with insurers and payment processors, alongside ready-made Teams apps, portals, dashboards and workflow templates.
• Speech and text analytics aim to cut doctors' charting time. Naik says speech-to-text, sentiment analysis and text analytics from Cognitive Services can let doctors and nurses spend more time listening to patients and less time typing notes. He ties this to patient satisfaction, citing the common complaint that the doctor typed more than listened.
• The product is now generally available as a per-user licence. Naik says it went into preview in May, when it was announced at Ignite, and reached general availability on October 28 as its own licence at $95 per user per month. HealthBot and Cognitive Services are billed separately as metered Azure services, and he refers buyers to their account executive on pricing.

2020-11-17 · open the original ↗

• Pull lightweight polyline first, then pull the cable with it. The host, who calls himself a novice at fishing walls, failed to push two Cat6 cables up an insulated exterior wall with both the magnet puller and the rods; the cables came off the rod and he skinned a knuckle. Polyline tied to the magnet shuttle slid through the insulation easily and then pulled the Cat6 behind it.
• A wall cavity's capped top blocks any pull into the attic. Pushing rods up from his office only hit the timber the host describes as a 4x4 capping the cavity, and roof and HVAC ducting made it impractical to drill down into that exterior wall. He moved the cross-connect about six feet over to an uninsulated interior wall that he could reach from the attic.
• Drill down from the attic, then drop the shuttle in free fall. He bridged the joists with plywood, drilled a 3/4-inch hole through the top timber, and dropped the magnet shuttle on about eight feet of polyline. He found it from the office with the magnet, drilled there, and pulled the Cat6 down to a keystone wall plate.
• The attic now holds a UniFi USW Industrial switch. The host chose it to cope with his attic's winter cold and summer heat, mounted with a 1U 24-port Cable Matters keystone patch panel on a backboard he built. The cable tested good and the switch adopted into UniFi, giving him a point to fan Cat6 out across a house that is wired mostly with coax.
• The magnet puller impressed him most; the camera rarely helped. The tools were sent free by TechToolSupply.com. The host rates the MagnaPull "the star of the show" and thinks the 30-foot push-pull rod kit could have done most of the same work. The Wi-Fi Cable Ferret camera worked but was of little use in his walls; he leaves its verdict open.

2020-11-17 · open the original ↗

• Set up your physical workspace deliberately. Answering a beginner C# programmer in Ethiopia who gets exhausted and stops coding, Hanselman says overwhelm hits veterans too. He calls the first remedy "nesting": choose your posture and layout so you can work long without hurting yourself, and keep things within reach that "feed your spirit".
• Speed up the developer's inner loop. He demos replacing stop-rerun-refresh with dotnet watch run, noting every language has a file watcher or a tool like watchexec. His rule: once you do something twice, see if you can automate it, and by five or ten times make it a script.
• Learn the few hotkeys that stop repetition, not all of them. He shows multi-caret editing and zooming in VS Code, snapping windows with PowerToys FancyZones, alt-click and Ctrl+W in Windows Terminal, and start . to jump from a prompt to Explorer. He says to put three to five on a sticky note and practise them until they are like a kata.
• Keep small utilities synced and on your PATH everywhere. His utils folder in Dropbox holds zoom and clipboard tools, wget and a resolution batch file, and it is on the PATH on every machine, so a new tool is available on laptop and desktop at once.
• When overwhelmed, step back and build systems you can succeed in. He suggests declaring tab bankruptcy, writing the problem on paper, and rubber-ducking it aloud. He sets goals he can keep, such as not blogging daily so a missed day doesn't sting, and says to know when and how you work best.

2020-11-03 · open the original ↗

• This video advertises Crosstalk's own hosted FreePBX service. The host calls it a "craft" hosting service: Crosstalk says it does not cram systems onto overloaded virtual machines. It also says it will first discuss whether hosting suits a business at all, and tells some customers it does not.
• Cloud hosting suits businesses with phones at several locations. The host says one hosted server lets sites share a phone bill and dial each other by extension. If one site's internet goes down, the others carry on and can take its calls. Each site still keeps its own numbers, 911 service, auto attendant and outbound routes.
• Crosstalk Cloud 50 costs $75 a month; Cloud 100, $120. The phone counts are sizing guides, not caps: Cloud 50 suits up to 50 phones and Cloud 100 suits 50 to 100, and the 51st phone does not stop calls. The host concedes other providers charge less and says the premium pays for support.
• Each server ships hardened, with full admin access and backups. Crosstalk sets up a firewall, a Let's Encrypt certificate for HTTPS and the Sysadmin Pro module, and adds the FreePBX Endpoint Manager on Cloud 100 only. Customers get both the web GUI and SSH. Backups are VM snapshots plus an off-site FTP copy of the configuration only, so voicemails and call recordings are never stored off-site.
• Updates are tested before they reach customers; there is no contract. Crosstalk says it tests new FreePBX module releases on its own servers, under version control, before rolling them out with Linux updates. It claims a 100% uptime guarantee, and rentals are month-to-month. It also advises on SIP trunks, its own Crosstalk SIP among them.

2020-11-02 · open the original ↗

• Cloud projects fail from missing ground rules, not bad code. Hepworth, a cloud consultant at Black Marble, says the projects he is called in to rescue went wrong because the technical solution was disconnected from the business's needs and constraints: a surprise bill that blew the budget, a deployment in Central US when the data must stay in Europe, or a preview service with no SLA. He argues governance can start as a few sentences and grow, like bowling-alley guardrails, and that it runs through operation, disaster recovery and business continuity, not only the start of a project.
• Developers should start governance themselves and draw in the business. He gives technology choice as an example: a team of long-time .NET specialists writing its new cloud app in Go takes on risk it may not be able to debug or deploy. If their organisation has no governance, he urges developers to propose guardrails and ask business owners of compliance, data and budgets to lead, saying this is good for both their careers and the business.
• Published frameworks offer a checklist for a cloud operating model. Hepworth points to the Cloud Adoption Framework, which assesses an organisation's maturity and supplies starter governance documents, and the Well-Architected Framework, which questions an application on backup, DR, resilience, data management and risk. He gives aka.ms/governancedocs as the entry point, "if memory serves", and the host checked that it led to Azure's governance documentation.
• Security should loosen development and lock down production. He recommends separate subscriptions, with a loosely regulated development subscription that alerts rather than blocks, and production that developers cannot touch and only automated tooling deploys to. He also recommends least privilege, just-in-time administration (a manager-approved, audited, time-limited elevation of perhaps a couple of hours), encryption at rest, a ready-made identity provider such as Auth0 or Azure AD rather than one you write yourself, and device management such as Intune.
• Policy tooling lets you show a regulator each rule enforced. Hepworth describes grouping subscriptions under management groups and applying Blueprints, which bundle access rules, ARM-template resources such as Key Vault, and Azure Policies written in JSON, for example blocking deployments outside Central US in production but only alerting in development. The portal then reports compliance across all resources and can remediate some failures; baseline policies, compliance-specific blueprints such as UK OFFICIAL, and samples in the github.com/azure/azure-policy repo (located by the host) give a fast start.

2020-11-02 · open the original ↗

• The Dream Machine simplifies Ubiquiti's confusing pro-level lineup. Hanselman ranks the range consumer to professional: AmpliFi mesh kits for non-technical parents, then UniFi, which needed both a Cloud Key for the controller software and a Security Gateway for routing, a split he calls confusing. The Dream Machine combines router, Wi-Fi and controller. He says he never activated a Ubiquiti affiliate signup and gets no kickbacks, though Amazon affiliate links may appear.
• He moved to a Dream Machine Pro for failover internet. With family video calls, terabytes of video uploads for his Microsoft job and conference keynotes, he needed reliability. The roughly $400 Pro adds a camera hard drive and two WAN ports, carrying Comcast plus a fiber line at $60 a month that takes over if Comcast drops. He says link aggregation is being worked on or in beta, and 4G backup is an option.
• Make exactly one device hand out IP addresses. Plugging a new router behind the ISP's all-in-one box creates double NAT, a network behind a network. He says to put the ISP device in bridge mode, or use DOCSIS to bring your own modem, so the UniFi gear gets the external address and runs DHCP.
• A small wall-mounted rack tidied wiring from 2007. He hung a 12U enclosure high in a closet, cut a gang-plate hole to pull out Ethernet laid when the house was built, sleeved the cables and racked the UDM Pro, switches and couplers, using about 22 ports. He calls the coax he also ran a mistake, and uses PoE switches to power a Raspberry Pi with a PoE hat and G3 Flex cameras.
• Mapping tools make an existing network easier to track. Ubiquiti's iPhone app scans a device's QR code and shows in augmented reality what is plugged into each port. For finding lost wires he recommends a Klein Tools network tester with six remotes, suggested by Stack Overflow's Nick Craver.

2020-10-28 · open the original ↗

• YubiKeys are faster to use than phone authenticator apps. With Yubico Authenticator open on the desktop, the host double-clicks a code, touches the key and pastes from the clipboard, which he estimates cuts 25–50% off each 2FA entry. The video carries a YubiKey affiliate link; he says he bought his YubiKey 5 NFCs in 2018, before joining the programme, and switched after a Yubico engineer walked him through them.
• Hardware keys beat SMS and app codes for businesses. The host calls SMS 2FA insecure and dependent on connectivity. Authenticator apps mean supporting employees' personal phones and migrating codes to new devices, and multi-device tokens (Authy) multiply copies of the "something you have". A key has no battery and needs no network.
• FIDO standards go beyond what one-time passcodes can do. He describes FIDO U2F (password plus a key touch, the usual website case) and FIDO2, made of CTAP (key to device) and WebAuthn (browser to site), while saying he is not an expert. He demonstrates U2F on Dropbox with an optional key PIN, a long OTP string on Vultr, and a security-key login on GitHub.
• Keep a second key, but TOTP backups must be set up manually. A QR code loads only one key, so he copies each site's secret key into both YubiKeys by hand; U2F sites accept several keys natively, often up to about five. He keeps the spare in a safe, puts a Tile tracker on his keychain, and says to always save backup codes.
• One key holds 32 TOTP and 25 FIDO credentials. The host uses fewer than 20 TOTP slots. For Windows sign-in: Yubico Login handles local accounts, Azure AD supports FIDO2 (he advises a PIN rather than passwordless), on-premises Active Directory uses smart-card mode, and Microsoft accounts with a key prompt for it at login.

2020-10-19 · open the original ↗

• The G4 Bullet upgrades the G3 Bullet's resolution and housing. It is 1440p (2688×1512) against the G3's 1080p, with an aluminium-alloy body, IPX4 and IK04 ratings, an operating range of −20 to 40 °C, 802.3af PoE only (no 24 V passive), and UniFi Protect only. MSRP is $199 against $149. The host says the G3 was the camera Crosstalk sold most, around five times any other, back when it sold UniFi Video systems.
• In daylight the G4 and G3 Bullets look about the same. With all three cameras set to a 6,000 kbps bitrate, the host found little difference in sharpness between the two Bullets. The roughly $450 G4 Pro (4K) gave a much wider field of view and more saturated default colour. He cautions that his footage was re-encoded to 1080p for YouTube.
• The G4 Bullet's onboard IR is far better than the G3's. On his night test the G3 showed ghosting and went dark beyond a few feet, which he says makes the G4 worth the extra $50. The G4 Pro's onboard IR was much clearer than either Bullet's, but at about 25 feet he could not recognise a person on either G4.
• The host recommends adding an external IR illuminator to the G4 Bullet. He sets the camera to switch to night mode without its own IR LEDs and lets a $35–40 illuminator light the scene. That setup, just under $250 in total, matched the G4 Pro's night clarity and brightness in his test. The Pro still wins on resolution and field of view, for example for reading licence plates.

2020-10-13 · open the original ↗

• MoCA adapters turn a house's existing coax into Ethernet. The host's 1990s house has coax to most rooms, so he used a two-pack of MoCA 2.5 adapters ($179, 4.7/5 on Amazon) to reach his garage. Each adapter has two gigabit ports and runs on 5 V micro-USB. MoCA 2.5 is backward-compatible with 2.0 and 1.1. The video carries Amazon affiliate links.
• Simple inline wiring makes the adapter a single point of failure. In a point-to-point setup the cable service runs through the adapters' in/out ports, and the adapters are not passive. If the garage adapter loses power, which is not on a UPS there, the whole house loses internet.
• The host recommends coax splitters so internet bypasses the adapters. A two-way splitter at each end sends one leg to the cable modem and one to the adapter's MoCA port. That keeps the modem path and the MoCA link separate on the same wiring, so a dead adapter cuts only the garage LAN. Splitters cost a couple of dollars and can fan out to more adapters.
• He measured about 95 Mbps across the MoCA link. The figure was the same on a speed test and on iperf: full upload, but about a sixth of the expected download. He offers no explanation and calls it ample for one or two access points and cameras needing 5–10 Mbps. A G4 Bullet streamed 1440p over the link, which reported a 1 Gbps port connection.
• Change the adapter's default password and IP address. The adapters ship at 192.168.144.200 with admin/admin, so you reach the GUI by giving your PC an address in that subnet. He set a strong password and a static IP on his own LAN. Network changes take effect only after a reboot.

2020-10-12 · open the original ↗

• A terminal is just the window; the shell does the work. Hanselman compares terminals (Windows Terminal, xterm, iTerm) to web browsers and shells (PowerShell, cmd, bash, fish, zsh) to what they talk to. He dismisses the "religious argument" over which shell is best: use the one that makes you happy. He says he ends up in PowerShell most often, but likens the choice to Honda against Toyota.
• Every shell differs, and aliases smooth over the gaps. He runs the same commands side by side in PowerShell, cmd and bash (Ubuntu under WSL2): in PowerShell, ls, dir and gci are all aliases for Get-ChildItem, so newcomers from DOS or Linux "suddenly feel comfortable". He wrote a clear.bat containing cls so clear works in cmd, and aliased please to sudo. A familiar command in an unfamiliar shell is "like going to Italy and saying a Spanish word": it may or may not work.
• A handful of commands is enough to get around. He covers pwd/cd (with cd .., tab completion and cd -, which doesn't work everywhere), mkdir, touch against PowerShell's New-Item/ni, and cat against cmd's type. A single > redirect clobbers a file and >> appends to it. Shells also handle quotes differently: cmd wrote the quote marks into the file, which a bash user would not expect.
• Pipes chain small tools into bigger work. Text search is cat … | grep in bash, type … | findstr in cmd, and Get-Content … | Select-String (aliases gc, sls) in PowerShell. Process lists come from ps, Get-Process and tasklist; bash showed fewer processes because he wasn't administrator. Help comes from man, --help or /?, which again differ per shell. He notes that whole books cover bash and PowerShell scripting.
• History tools and administrator rights vary by OS. Up-arrow history works in all three shells. cmd's F7 draws a history list, a feature he wishes his other shells had, and bash has Ctrl+R reverse search. Administrator rights depend on the operating system underneath: on Windows he Ctrl+Shift-clicks in Windows Terminal to open an elevated shell, while on Ubuntu it is sudo.

2020-10-07 · open the original ↗

• The UniFi Lite switches are light-duty PoE switches. The USW-Lite-8-PoE ($109 MSRP) has eight gigabit ports, four of them 802.3at PoE+ at 30 W each. The USW-Lite-16-PoE ($199) has 16 gigabit ports, eight of them PoE+. Both share a single 60 W power budget, which the host says suits phones and cameras drawing 4–5 W each. Neither offers 24 V passive PoE.
• The host prefers the Lite 8 to the older US-8-60W. Both cost $109 with the same PoE layout; he favours the Lite for its easier snap-on wall mount and newer looks. For heavier PoE loads he points to the US-8-150W ($199), which has PoE on all eight ports, 150 W, two SFP ports and 24 V passive.
• The Lite 16 has no direct UniFi equivalent. It is a desktop, non-rackmount switch. The rackmount alternative is the Gen 2 USW-16-PoE at $299: 1U, a 1.3-inch touchscreen, the same eight PoE ports and two SFP ports.
• Buy the UniFi switch if your network already runs UniFi. The host compares a $79 unmanaged TP-Link 8-port PoE switch, a $135.49 layer-2 managed Cisco 8-port PoE switch and a $137.99 managed Netgear with SFP. The competitors offer PoE on all eight ports but no UniFi central or remote management. He judges both Lite switches reasonably priced.
• Adoption took under 60 seconds, with firmware newer than his controller. The controller found the switch automatically; SSH with ubnt/ubnt is available for manual set-inform. The switch shipped with firmware newer than the host's controller (5.13.32), which offered a downgrade; he was holding off 6.x because of reported issues. The topology map wrongly showed his NAS on the new switch at times.

2020-10-05 · open the original ↗

• "Stack" names four related ideas that build on each other. Hanselman separates the stack data structure, stack memory allocation, stack frames in the call stack, and the stack overflow recursion can cause. He pitches the video at "100 level". Edge cases such as tail-call recursion are nice-to-know rather than need-to-know if "your job is putting text boxes over data".
• A stack is last in, first out. He pushes books onto a pile, then a C# Stack<string> with "hello", "world", "!". The dump lists them in reverse order, and one pop removes "!" and leaves two items, which he steps through in the Visual Studio debugger.
• Locals live on the stack; objects live on the heap. Each thread gets its own stack, so local values can differ between threads, while an object on the heap is shared by everything holding a reference. A Visual Studio memory snapshot shows one Person of 40 bytes. Passed by reference, the person's age change to 100 is seen everywhere. An integer passed by value is copied onto the method's stack, so the caller's copy stays at 99 after the method increments it.
• Nested calls deepen the call stack without being recursion. He watches Visual Studio's call stack window as Main calls functions that each wait for the next to return. In the chained version (happy, then little, then function) the call stack grows deeper, but he notes this is not recursion.
• Deep recursion overflows a fixed-size stack; loops avoid it. A countdown from one million that calls itself overflowed after about 19,000 calls. He says the stack is fixed in size, unlike the heap, which is bounded by the processor architecture. An iterative loop, which he says is what a compiler would generate, finishes using no extra stack. He says F# applies tail-call optimization automatically and C# does not, "even though it possibly could".

2020-10-05 · open the original ↗

• Productivity comes from intentionality, not more hours. Hanselman says wasting time is fine when chosen, and the problem is losing four to six hours while frustrated at not doing the thing you wanted; his example is time-boxing a newly re-released Super Mario to a half-hour timer, then spending 90 minutes on a YouTube video. Saying no is "the biggest control" you have, and he books himself two-hour "focus time" meetings on his calendar.
• A trusted list frees the mind that undone tasks occupy. He compares unrecorded to-dos to the "System" process using 20% CPU in Task Manager, and says writing them down, on paper when overwhelmed (his "Sync to Paper" article), gives you permission to stop worrying; he also consciously lets go of things like never watching The Wire. In Microsoft To Do he keeps a pool of about 70–76 items and adds three to five to "My Day" rather than 30.
• Turn off every notification that isn't worth an interruption. Hanselman says we granted each app permission to pop a toast and can revoke it per app; anything truly important would come by a phone call, not a toast sitting at the same level as a BuzzFeed item. His phone is on silent, Teams has scheduled quiet hours, and his wife and kids have their own text sounds.
• Multitasking is a lie; people are single-threaded. He says multitasking is just fast context switching with a real if unmeasured overhead per switch, so four 30-minute tasks in two hours go better as four uninterrupted sprints than as 14 switches. The only useful background thread is the subconscious that solves problems in the shower.
• Operationalize or hand off recurring chores to reclaim time. He pays a local kid $20 to mow his lawn, which he says buys back an hour and a half of his weekend, and calls getting an editor for his podcast a "game changer" that lets him focus on content. He concedes the setup cost of a new system often feels bigger than just doing the task yourself, and says to push past it.

2020-09-29 · open the original ↗

• The "everything you need" starter kit is not standalone. As of recording, a UDM Pro is the only device running UniFi Access software, so one is required; the hub also needs 802.3bt (PoE++) power because it drives the lock, readers and a camera. The host found this out after preparing a 16-port Switch Lite that cannot supply it.
• Extra doors needing a Pro reader are cheaper as whole kits. The kit is $499 against $637 for the parts separately (hub $199, Access Reader Pro $299, Reader Lite $99, 20 NFC cards $40). That is roughly the hub plus the Pro reader, so a second kit brings the Lite reader and cards free.
• The hub keeps door control away from the door, which the host rates a security plus. Each hub controls one door and wires to mag locks, powered or unpowered strikes, or a siren through side contacts, and it powers each reader over its own Cat5e/Cat6 run. He contrasts integrated units such as an Axis reader with built-in strike, which could be hotwired if pulled off the wall.
• The hub has separate reader ports, and the host cannot explain why. It has ports for the indoor NFC/Bluetooth Reader Lite, the weatherproof Reader Pro and a camera (a G3 Flex in the diagram). He guesses at different power needs or doors scanned on both sides, and assumes Bluetooth means phone-app unlocking.
• The host thinks the Reader Pro reuses Ubiquiti's FrontRow camera design. That is his own speculation from the matching form factor; he does not know whether Ubiquiti sold the product off. This video is an unboxing only, with setup and configuration left for a follow-up.

2020-09-28 · open the original ↗

• Racism is built into institutions, not just individual hatred. Block, citing Ibram Kendi's How to Be an Antiracist, says there is no middle way and that "I don't see race" denies the problem; he points to redlining as zoning written so Black people could not live in neighbourhoods, which he says produced the segregated Long Island towns he grew up near. He puts denial down to avoided accountability and to privilege, contrasting a Black colleague who teaches his children how to survive a traffic stop with his own assumption that a stop is about a cop's quota.
• The goal is equity, not equality. Block says equality gives everyone the same thing, while equity takes account of different experiences and barriers to access in order to level the field; asked for an example, he and the host settle on workplace jokes that land differently on their target.
• Allyship starts with listening and looking inward, then intentional action. Block's steps are to listen without rushing to judgment, admit you do not know, avoid taking up the airspace, and get to know people who do not look like you outside diversity meetings. He also says to expect mistakes and approach them with a growth mindset, and that good intent does not reduce the harm done.
• Tech's bias shows in hiring, mentoring, referrals and AI. Block cites an interviewer asking to touch a Black woman's hair, callback data on Black-sounding names, people mentoring those who look like them, and his own past referral hiring as structural racism. On AI he cites Amazon shelving a résumé-screening system in 2018 over bias, and an ID-verification service that failed to recognize a dark-skinned Black woman's face.
• Renaming "master" terminology matters because perception outweighs intent. Block says people objecting to master/slave terms and GitHub's move to "main" are what counts, whatever the original authors meant, and he rejects calling the change performative: small changes add up. He notes he works for Microsoft, which owns GitHub, and created his first repo with "main" as its default.

2020-09-27 · open the original ↗

• Orchestration means giving containers roles and managing their life cycle. Hanselman frames it as an orchestra or "herding cats": a cluster manager (the "master") coordinates nodes, which are worker machines that may be physical or virtual, and each node runs pods. A pod is a group of containers plus the IP addresses and storage they need. The container stays "the doer" and never knows it is being scaled, restarted or constrained.
• Kubernetes is driven by declarations, not programs. A YAML file is "a bill of lading", in his words: name a pod, its image and its port, and cap its CPU and memory without the container knowing. For local development he stresses imagePullPolicy: IfNotPresent, so the cluster does not go looking for the image in a cloud registry. He contrasts create (make a new one) with apply (make it or change it), and demos a replica set of three .NET containers.
• The cluster is a sealed box until you punch holes in it. Pod IPs are internal, so you group pods into services. Kubernetes runs its own internal DNS, so code can call http://shoppingcart without knowing how many instances sit behind it. He reaches the apps through kubectl proxy on port 8001, a temporary port-forward from local port 81 to port 80, and a NodePort (31914 outside, 80 inside). He shows that Kubernetes itself is "a bunch of other containers" in namespaces other than the default.
• Docker Desktop on WSL 2 gives you a local cluster. His setup is WSL 2, Docker Desktop and its "enable Kubernetes" checkbox, followed by a few minutes' wait. In the demo a .NET service and a Node service run side by side in separate pods, because "containers don't care" what language they are written in.
• Should you learn Kubernetes? "Can't hurt," he says. The hard parts, in his view, are the vocabulary and YAML, and the commands he finds most useful are describe, explain and get. He also mentions rolling deployments that drain traffic from version 1 pods onto version 2. His prediction is that much of this "will be hidden from you" in future, and you will just deploy your app.

2020-09-25 · open the original ↗

• NVMe caching matters for application servers, not backup-only use. The host recommends the DS220+ or DS620slim, with no NVMe slots, for plain backup. He recommends the DS420+ (four bays, not expandable) or DS720+ (expands to 7 drives) as starter application servers for Docker, VMs, Plex or Surveillance Station. He rates the DS1520+ (five bays, up to 15 drives with two DX517 expansions) a strong mid-range home NAS.
• A starter DS1520+ build came to $1,384. Synology sent the unit free, and the host gives its price as about $650. He bought three 8 TB Seagate IronWolf drives at $215 each and one Samsung 970 EVO NVMe at $90. Filling all five bays and both NVMe slots adds about $530, for roughly $2,000.
• A single NVMe drive gives a read cache only. The host had not known this before buying his drives. The first drive is read-only cache, and a second adds a write cache; the pair is neither mirrored nor striped. So he advises fitting both slots to fully deck it out, depending on how write-heavy the workload is.
• Four-port 802.3ad bonding works only once the switch side is set. After the NAS bond was created it kept answering pings but reported a failed 802.3ad connection until he set ports 17–20 to aggregate on his Gen 2 UniFi 24-port switch. It then showed 4,000 Mbps, and desktop backups ran at near the PC's 1 Gbps wire speed.
• Pi-hole in bridge mode was more trouble than putting it on the LAN. The bridged container sat on a 172.17 subnet, which needed a gateway and static route in pfSense. It went down for about two hours when the NAS IP changed and the gateway was not updated, so he plans to recreate it on his main LAN.

2020-09-25 · open the original ↗

• The Cloud Adoption Framework is a library to draw from, not rules. Martensson describes it as Microsoft's curated guidance from customers running Azure at scale, covering business and organizational change as well as technology. Implemented "A to Z" as written, he says, it fits no one, and a full Azure landing zone as described is probably not what anyone needs at first; the framework itself has a "start small and expand" section.
• Adopting cloud needs anchoring in the organization, not just a boardroom decision. He says a top-down "we have to do this cloud thing" decision causes major internal fallout, with jobs changing and training needed. The framework's planning guidance is meant to address this, and he says teams years into Azure can still find gaps with it.
• Plan access and onboarding early, or unwinding it later hurts. In his experience developers are often given access to everything because it is easier, which within six months leaves unexplained changes and fails any compliance or security audit. Taking access away later upsets people. He says to work out early how a new team gets access and who may deploy to production, and to lay out subscriptions and management groups expecting to change them.
• Start with a small real application in production. Martensson says a sandbox teaches little, whereas a real workload produces monthly bills that can be weighed against business value. Large decisions, such as whether to buy an ExpressRoute dedicated connection at a "hefty price" or connect over the internet, can come later. Giard adds that a first project should avoid the most mission-critical systems because it will make mistakes.
• Bring in experienced help before going far down the wrong road. Martensson, an Azure MVP for over 10 years and a regional director, acknowledges that as a consultant he is promoting his own trade. He says tens of thousands of words of guidance do not tell an inexperienced team what to skip, and he has seen organizations whose late fixes cost far more than early guidance would have.

2020-09-24 · open the original ↗

• William Farr is the unsung statistical hero of COVID-19. Short says Farr, who joined the UK's General Records Office around the 1841 census and died in 1883, began recording cause of death, which lets occupations such as nurses and bus drivers be ranked by risk. Short says the "curve" politicians want to flatten is Farr's Law: infection rises exponentially, then drops quickly once everyone who can be infected has been, giving a sharp bell curve.
• Absolute death counts only give historical context. Short says reported totals, which he reads on air as 174,000 US deaths and 777,000 worldwide after first misreading them, raise questions of trust (Russia's under 16,000) and of the ability to measure (rural India). They cannot compare countries, which requires deaths per million. The one thing they allow, he says, is a comparison such as US COVID deaths having passed US soldiers killed in Vietnam.
• An average mortality rate hides steeply age-dependent risk. Short says the global rate of around 3.5% is an average. Citing UK work, Short says risk is roughly flat up to an age he puts at perhaps 35–40, then doubles every five years, and comorbidities such as obesity and type 2 diabetes raise it further. Young people who feel safe still endanger the people around them, and he praises younger generations for largely "taking one for the team".
• Testing figures are soft evidence; emergency calls and admissions are hard. Short says more tests find more cases without changing prevalence. The positive rate is what matters, and it can be inflated by "case hunting", such as door-to-door testing in the Manchester hotspot. No one knows the tests' false-negative rate, or how the viral load that tests positive compares with the load that infects. Hard evidence is COVID-related 999/911 calls and hospital admissions.
• Saving lives versus the economy is not either/or. Short recalls, without checking, a statistic that each percentage point of US unemployment adds about 10,000 deaths. He argues for local lockdowns, made possible by Farr-style statistics, with financial support for the locked-down areas, because the economy will not survive another six- or seven-month national lockdown. He says individuals who separate information from data make better decisions.

2020-09-22 · open the original ↗

• The BeaconHD only extends an existing UniFi network. The UAP-BeaconHD-US is a wall-plug 4x4 MU-MIMO mesh unit, not a standalone access point, so it needs an existing UniFi AP or Dream Machine. The host found no European version online, though he hints that something similar sits in Ubiquiti's early-access beta store.
• Adoption took about two minutes on a hosted controller. The unit found the host's hosted UniFi controller by itself and needed only a click to adopt. Next to his Flex HD, it reported a −40 dBm uplink and an estimated 540 Mbps transmit/receive rate.
• It markedly improved his G4 Doorbell's weak Wi-Fi in his own test. The doorbell had been at 60–70% signal to the upstairs Flex HD. With the Beacon about 25 feet away it reached 93%, and a G3 Micro reached 100%. The mesh uplink read 47% (270/324 Mbps) before a firmware upgrade to 4.3.20 and 97% after it.
• The host finds UniFi's per-client Wi-Fi experience figures inconsistent. A client showed 100% while the Beacon's own uplink showed 96%. He suspects the client figure counts only the hop to the Beacon.
• At $129 it undercuts a wired access point. The host compares it with a NanoHD at about $179 and a UAP-AC-Pro at about $139, before the cost of cabling either. He likes it and says he will watch for wireless problems among nearby clients.

2020-09-19 · open the original ↗

• The captions are a different episode from the one titled. This text never mentions the AWS S3 SDK. It is the same walkthrough as "Using the MinIO Java Client SDK [GCast 96]", step for step: MinIO's own Java SDK in a Spring Boot app, uploading and downloading the same test.txt, with the same "the last two videos" opening.

2020-09-18 · open the original ↗

• Crosstalk's previous pick, Bria Enterprise, is costly and cloud-dependent. The host says Crosstalk has sold and recommended CounterPath's Bria Enterprise for its easy install and admin provisioning. But it costs $29 per year per mobile device, and every user's SIP credentials must be entered into CounterPath's cloud portal, where a breach could expose tens of thousands of them.
• The host, whose store sells it, rates Clearly Anywhere better. ClearlyIP launched it for Android and iPhone at $9.99 per user per year, a launch price grandfathered for the life of the licence. Built on the PJSIP stack, it installs on any number of a user's devices, which all ring alongside a desk phone.
• Provisioning stays inside FreePBX, with no third-party cloud holding credentials. Users log in with FreePBX User Control Panel credentials and a domain, or scan a QR code from a ClearlyIP UCP widget. The host suggests a softphone-users group in FreePBX group permissions for central administration.
• Its features go beyond calling, with one firewall prerequisite. It supports BLF quick dials and SMS shared and synchronized across a team's phones, plus video calling, multi-channel call recording and scheduled do-not-disturb. It hands calls from LTE to Wi-Fi seamlessly. Push notifications require the FreePBX responsive firewall to let ClearlyIP's push servers authenticate.
• The host sends 911 to the cellular carrier through number rewriting. He says softphone emergency calls fail to convey location under Kari's Law and the RAY BAUM'S Act regime. His main gap is the lack of company-wide BLF templates, which he has heard are coming but without a date.

2020-09-17 · open the original ↗

• The MinIO Java SDK comes in as a Maven dependency. Giard runs a MinIO server in Docker on port 9000, with his own access key and secret key as environment variables (set up as in episode 94). He then generates a Spring Boot project with no dependencies from Spring Initializr and adds the MinIO SDK dependency to pom.xml. He says he learned the approach from the Java Client API Reference and the Java Client Quick Start Guide under Docs at min.io.
• A service class wraps the MinIO client for upload and download. The client is built from the endpoint, access key and secret key. The code checks whether the bucket exists, creates it if not, and uploads with the client's upload-object method, passing args built with the bucket and file name. Download works the same way with download-object args and saves into the same local folder with a "d_" prefix so the original is not overwritten. Giard notes that hard-coding the credentials "isn't the most secure thing" and that they probably belong in environment variables, but this is a demo.
• A component plus getBean connects the static main method to the service. Giard says it is difficult in Java to call a non-static class from a static method. So a component class autowires the service and holds one read-write method. In main he captures the ApplicationContext that the run call returns, calls getBean for the component, and adds the required throws declarations.
• The first run failed because the service lacked the @Service annotation. The exception said the service could not be found for autowiring, and adding @Service fixed it. Stepping through, the new bucket appeared in the MinIO browser, then the uploaded file appeared in it, and then a d_test.txt identical to the original appeared locally.

2020-09-16 · open the original ↗

• A MinIO gateway fronts another storage service instead of holding data itself. Giard calls it a MinIO agent and contrasts it with the server from the previous episode. The MinIO docs list five gateways, and he uses the one for Azure. It is a docker run command exposing port 9000 under the name "azure-s3", with the argument "minio gateway azure" where the server used "minio server".
• The gateway's access and secret keys must be the Azure storage credentials. In server mode you invent your own keys. Here the access key is the Azure storage account's name and the secret key is the storage account key (he uses key 1 and says key 2 works too). The prerequisites are an Azure account (he thinks the free trial is 30 days) and a storage account created at portal.azure.com.
• Every change made in one interface appears in the other. A bucket created in the MinIO browser shows up as a blob container in Azure Storage Explorer, and a container created in Azure shows up as a bucket in MinIO. Uploads and deletions made on either side are reflected on the other.

2020-09-16 · open the original ↗

• MinIO is object storage comparable to Azure Blob Storage or Amazon S3. It stores objects and other semi-structured data. In server mode it creates a storage repository plus a browser interface for uploading, listing, downloading and managing objects. Giard points to the quick start guide under Docs at min.io, which he says got him running in a hurry.
• Server mode is one docker run command from PowerShell. Docker must be installed (on Windows that needs a reboot) and running. Giard says that if the command fails, Docker may not be set to auto-start or may still be starting up. The container is exposed on port 9000 and needs two environment variables, an access key and a secret key. The defaults work, but he says you probably want your own, and he uses "access key 2" and "secret key 2".
• The MinIO browser organises objects into buckets. Giard logs in at the endpoint with the keys he set, in a private window in case credentials are cached. Buckets are MinIO's term for what he calls containers from Azure Blob Storage, and he likens them to folders. He creates two buckets, uploads files to each (several at once with Ctrl-select), then downloads and deletes objects.

2020-09-16 · open the original ↗

• Pandemic stress is now compounding job stress for developers. Downing, Okta's lead .NET evangelist, says the world has been in a "holding pattern" of rolling lockdowns since about February (she is speaking in August), and that people now do work, socializing and everything else at the same desk. She coped by throwing herself into building applications, but says she sees exhaustion across the industry. She adds that this predates the pandemic: constant change and roles absorbing DevOps, Docker and database administration have been wearing down even developers with 20 years' experience.
• Burnout shows up as cynicism, avoidance, irritability and overwork. From a blog's checklist based on a survey of about 55 developers, she lists cynicism about writing code, lacking the energy or motivation to turn up, irritation at coworkers, avoidant or addictive behaviour, compulsive overwork to keep up, and a belief that the team will collapse without you. She gives her own examples: a snarky remark that prompted a colleague's check-in, and drinking that rose early in the pandemic, which she ties to a family history of alcoholism. She notes that highly capable developers often fail to see burnout coming.
• Recovery starts with a therapist, then deliberate changes. Downing, who says she is not a doctor, says to see a therapist first and to switch if they are not the right fit; she found hers on the fourth try. Her own steps were mentoring excited junior developers from boot camps, putting her limited energy into the most important few of 20 tasks, helping outside tech by fostering huskies and malamutes, limiting online exposure, setting boundaries with her boss, taking micro-vacations and hiking. She cites Tim Ferriss's The 4-Hour Workweek.
• Women in tech face extra pressure to disprove diversity-hire assumptions. Downing says that, depending on where they live, women face an assumption that they were hired to fill a diversity quota, so they feel they must perform at a higher level. Absences for pregnancy or for caring for elderly parents also carry a worry that a man would not "bring that inconvenience" to the company.
• Developers' high stakes and high standards add to the strain. She points to self-driving cars and the Boeing 737 MAX as examples of how code matters, and says even a small JSON library might end up on a plane. Developers hold each other to harsh standards, as in pull-request comments on major SDKs, while knowing how much of the internet is held together "with bubblegum and tape" by a short supply of senior developers, many of them burnt out.

2020-09-16 · open the original ↗

• Background is a form of diversity that tech forgets. Motchoffo, a Black man who grew up in Cameroon and lived in France, says he came to the US about four years ago as a French speaker who barely knew English, with no plan to study computer science. He contrasts this with the usual four years of college followed by a job application. He is now finishing a summer Microsoft internship in a programme he describes as diversity-oriented, which mixes program management and software engineering.
• Losing his family's support left him homeless. He was homeless in Seattle for about a year. Six months after arriving, his family's financial support ended and, as an international student barred from working, he lost his apartment and left school. He slept by a bus station, showered at the gym where his membership still worked, and after about seven months applied for a work permit, which took about four months to arrive. He then worked in a fast-food kitchen in Bellevue.
• He chose rideshare driving to practise English, and it led him into tech. After saving for about a year to buy a car, Motchoffo drove for Lyft and Uber full time so he could talk to people. One passenger told him to "be comfortable in a discomfort position". Passengers who were software engineers introduced him to the field, and he began learning online and working toward an associate degree in computer science.
• A ride he accepted by accident produced the Microsoft internship. At the end of a long day he tapped "accept" by mistake. His passenger's husband worked on the Microsoft internship programme, and her call to him revealed applications closed that day at 5 p.m., two hours away; he applied and started in June. In the internship he found he prefers program management, for its focus on solving customers' problems, while still liking to code.
• Finance blocks university, so he is taking a bootcamp first. He was accepted at the University of Washington but could not get a loan because of his status. An instructor pointed him to the Code Fellows bootcamp, which gave him a full-ride scholarship, and he plans to work and save before returning to school. His advice to people struggling is to keep hope and keep going.