# shadowing Published articles for shadowing. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Taking over the Tech Lead role in your current team DevFeed: [Taking over the Tech Lead role in your current team]() Original publisher: [Read original article]() Author: Anemari Fiser Published: 2024-10-24T06:01:40Z Content type: opinion Language: en Sources: [Level up as a Tech Lead]() Topics: [Tech Lead](), [Support]() Tags: [communication](), [leadership](), [process](), [project](), [shadowing](), [team](), [teams](), [tech-lead]() ### AI overview An account of transitioning into a Tech Lead role after the previous lead rolled off a project. The transition used a two-month plan involving shadowing, handover sessions, gradually taking over meetings and decisions, and assuming difficult stakeholder conversations. The author identifies the lack of clear communication to the team as the main thing they would change. ### Source excerpt Diving into one of the most common pathways to the Tech Lead role. ## Scopes and Scope Functions DevFeed: [Scopes and Scope Functions]() Original publisher: [Read original article]() Author: author@typealias.com (Dave Leeds) Published: 2022-08-22T00:00:00Z Content type: tutorial Language: en Sources: [Dave Leeds on Kotlin - typealias.com]() Topics: [Kotlin](), [Library](), [Code]() Tags: [also](), [apply](), [classes](), [code](), [introduction](), [kotlin](), [learn](), [learn-to-program](), [let](), [library](), [programming](), [run](), [scope](), [scope-function](), [scope-functions](), [shadowing](), [standard](), [standard-library](), [variable](), [visibility](), [with]() ### AI overview A Kotlin tutorial chapter introduces scopes as regions of code where variables, functions, and classes can be declared, then begins explaining Kotlin's five scope functions from the standard library. ### Source excerpt In the last chapter, we learned how to create extension functions, which can be called using dot notation. In this chapter, we'll learn about scope functions, which are five particular functions that Kotlin gives us in its standard library. Before we can understand scope functions, though, it helps to first understand scopes. Introduction to Scopes In Kotlin, a scope is a section of code where we can declare new variables, functions, classes, and more. ## SRE: On-Call Procedure at trivago DevFeed: [SRE: On-Call Procedure at trivago]() Original publisher: [Read original article]() Author: Kenechukwu Nnamani Kene is an SRE engineer; An Avid Learner Follow Published: 2022-07-18T00:00:00Z Content type: tutorial Language: en Sources: [Trivago]() Topics: [site-reliability-engineering](), [incident](), [Availability](), [Microservice](), [Kubernetes]() Tags: [availability](), [devops](), [engineering](), [engineering-culture](), [incident](), [kubernetes](), [microservices](), [on-call](), [onboarding](), [shadowing](), [site-reliability](), [sre](), [uptime](), [zoom]() ### AI overview This article describes trivago's SRE on-call procedure, including onboarding, shadowing, scheduling, and rules for detecting, communicating, and resolving incidents. It also explains the company's microservices and Kubernetes-based infrastructure. ### Source excerpt One of the many responsibilities of a Site Reliability Engineer (SRE), is to ensure uptime, availability and in some cases, consistency of the product. In this context, the product refers to the... ## How Go shadowing and bad choices caused our first data loss bug in years DevFeed: [How Go shadowing and bad choices caused our first data loss bug in years]() Original publisher: [Read original article]() Author: Ryland Goldstein Published: 2021-03-03T04:00:00Z Content type: opinion Language: en Sources: [Temporal Blog]() Topics: [bug](), [data](), [Go Language](), [reliability](), [consistency]() Tags: [applications](), [bug](), [data](), [distributed](), [go](), [how-to](), [reliability](), [shadowing]() ### AI overview A Temporal retrospective describes the company's first data-loss bug in years. The article attributes the incident to Go shadowing and other bad choices, after initially investigating corrupted workflows and suspected persistence-cluster memory issues. ### Source excerpt I'm Ryland from Temporal - an MIT OSS platform for building highly reliable distributed applications. We pride ourselves on the reliability and consistency Temporal provides to our users mission critical applications. ## Own Your Abstractions DevFeed: [Own Your Abstractions]() Original publisher: [Read original article]() Author: Steve Barnegren Published: 2019-09-12T00:00:00Z Content type: opinion Language: en Sources: [Steve Barnegren]() Topics: [Swift](), [Testing](), [Protocol (disambiguation)](), [Filesystems]() Tags: [objective-c](), [protocol](), [shadowing](), [swift](), [test](), [testing]() ### AI overview The article examines a Swift testing technique that mirrors an external concrete type with a protocol and uses mocks for dependency isolation. It argues that this shadowing approach can hide deprecation warnings and encourages designing semantic abstractions instead of replicating awkward APIs. ### Source excerpt If you want to test your Swift code, at some point you're probably going to need to make some mocks in order to isolate a type that you're testing from system apis. For instance, if your type calls UNNotificationCenter, then in your tests you don't want it to call the real UNNotificiationCenter, but rather a mock substitute that you control. ## Identifying and Scaling a Language Market DevFeed: [Identifying and Scaling a Language Market]() Original publisher: [Read original article]() Author: Sherry Xia Published: 2019-06-28T19:00:00Z Content type: article Language: en Sources: [Square Corner Blog](), [Square Corner Blog RSS Feed]() Topics: [Localization (l10n)](), [product analytics](), [User Experience](), [data]() Tags: [analytics](), [data](), [data-science](), [engineering](), [experience](), [insights](), [language](), [onboarding](), [product-analytics](), [scale](), [shadowing](), [support](), [user-experience](), [verification](), [web]() ### AI overview Square used platform language data to identify Spanish-speaking US sellers, found a substantial activation-rate gap compared with English-speaking sellers, and used the findings to guide localization and engineering work. The changes increased the Spanish-speaking sellers' activation rate from about 75% to about 90%. ### Source excerpt Using data to understand where to improve localization ## Functions and Naked Returns In Go DevFeed: [Functions and Naked Returns In Go]() Original publisher: [Read original article]() Published: 2013-10-10T00:00:00Z Content type: tutorial Language: en Sources: [William Kennedy]() Topics: [Go Language](), [Error Handling](), [Compiler]() Tags: [ardan-labs](), [blog](), [code](), [error-handling](), [fmt](), [function](), [go](), [go-error-handling](), [go-programming](), [golang](), [programming](), [scope](), [shadowing](), [variable]() ### AI overview This Go tutorial explains returning multiple values, handling errors through returned error values, ignoring a return value with an underscore, naming return arguments, and using naked returns. It also warns about variable shadowing and explains how braces create new scopes. ### Source excerpt In Go values that are returned from functions are passed by value. Go gives you some nice flexibility when it comes to returning values from a function. Here is a simple example of returning two values from a function: package main import ( "fmt" ) func main() { id, err := ReturnId() if err != nil { fmt.Printf("ERROR: %s", err) return } fmt.Printf("Id: %d\n", id) } func ReturnId() (int, error) { id := 10 return id, nil } The function ReturnId returns a value of type integer and of type error. This is something very common that is done in Go. Error handling is performed by returning a value of type error from your functions and the calling function evaluating that value before continuing. If you don't care about the error for some reason after a function call returns, you can do something like this: id, _ := ReturnId() This time I used an underscore to represent the return value for the second return argument, which was the error. This is really nice because I don't need to declare a variable to hold the value being passed in, I can simply ignore it. You also have the option to name your return arguments: func ReturnId() (id int, err error) { id = 10 return id, err } If you name your return arguments you are creating local variables just like with your function parameters. This time when I set the id variable, I remove the colon (:) from the short variable declaration and convert it to an assignment operation. Then in the return I specify the return variables as normal. Naming your return arguments is a nice way to document what you are returning. There is also something else that you can do with your named arguments, or not do: func ReturnId() (id int, err error) { id = 10 return } This is what is called a naked return. I have removed the arguments from the return statement. The Go compiler automatically returns the current values in the return arguments local variables. Though this is really cool you need to watch for shadowing: func ReturnId() (id int, err error) ## Common Lisp Scoping, Lexical Binding, and Closures DevFeed: [Common Lisp Scoping, Lexical Binding, and Closures]() Original publisher: [Read original article]() Author: Dimitri Fontaine PostgreSQL Major Contributor; Author Published: 2013-01-09T10:07:00Z Content type: tutorial Language: en Sources: [Dimitri Fontaine]() Topics: [Common Lisp](), [Functional programming](), [Programming](), [function]() Tags: [article](), [blog](), [function](), [functional-programming](), [lisp](), [shadowing](), [simple]() ### AI overview An article demonstrates Common Lisp scoping through examples involving lexical binding, variable shadowing, generalized booleans, closures, and REPL-based experimentation. ### Source excerpt Thanks to Mickael on twitter I got to read an article about loosing scope with some common programming languages. As the blog article Lost in scope references functional programming languages and plays with both Javascript and Erlang, I though I had to try it out with Common Lisp too. So, here we go with a simple Common Lisp attempt. The Lost in scope article begins with defining a very simple function returning a boolean value, only true when it's not monday.