We build the future of human-machine interface.

Wisear

The Anti-Luck, Decision Making Framework: Mastering the Art of Making Smart Choices

ভাগ্য বিরোধী, সিদ্ধান্ত নেওয়ার কাঠামো: স্মার্ট পছন্দ করার শিল্পে দক্ষতা অর্জন

Das Anti-Glück-Framework zur Entscheidungsfindung: Die Kunst meistern, kluge Entscheidungen zu treffen

El marco de toma de decisiones anti-suerte: dominar el arte de tomar decisiones inteligentes

Le cadre de prise de décision anti-chance : maîtriser l’art de faire des choix intelligents

भाग्य-विरोधी, निर्णय लेने का ढाँचा: स्मार्ट विकल्प बनाने की कला में निपुणता

運に左右されない意思決定フレームワーク: 賢い選択をする技術を習得する

행운 방지, 의사 결정 프레임워크: 현명한 선택을 하는 기술 익히기

A estrutura anti-sorte para tomada de decisões: dominando a arte de fazer escolhas inteligentes

Система принятия решений против удачи: освоение искусства принятия разумных решений

Şans Karşıtı Karar Verme Çerçevesi: Akıllı Seçimler Yapma Sanatında Ustalaşmak

Khung ra quyết định, chống may mắn: Nắm vững nghệ thuật đưa ra lựa chọn thông minh

反运气决策框架：掌握做出明智选择的艺术

The transaction that first gave Bitcoin any sort of monetary value happened in October 2009 when a Finnish computer science student Martti Malmi (‘Sirius’) sold 5,050 coins for $5.02, meaning each Bitcoin was worth $0.0009. In today’s terms, if he had held on to his coins, he’d be (circa) NZ$555,500,000 richer. Today, we all know “someone who knows someone” who invested around that time and has become a multimillionaire; and we’re kicking ourselves for not doing the exact same thing… With the fourth Bitcoin halving firmly in our rearview mirror and some very recent all-time highs for Bitcoin, new investors (or even existing ones wanting to build or increase their crypto portfolio) might be asking if they’ve waited too long to invest… On the other hand, those who have HODLd - or ‘held on for dear life’ - for a while might be fretting about the lack of an immediate, dramatic change in price over the past weekend. An Immediate Ascent Is Always Unlikely… In the past, halvings have been followed by periods of increased demand and price surges due to the dynamics of supply-demand - but this is never immediate and market dynamics, sentiment, and regulatory factors all influence Bitcoin's price trajectory, making a straight-line ‘ascent’ unlikely. While analysts anticipate an upward trend (which has been the case historically post-halving), the reality is nuanced, and these events are often followed by periods of consolidation and correction - including rallies, reactions, and a lot of volatility on (hopefully) the way up. TLDR: If you were expecting prices to skyrocket overnight, you should have been reading my blogs sooner to get those expectations in check! The Danger of Letting Disappointment Drive Decision-Making Some analysts predicted that the halving would trigger an immediate price slump that would lead to widespread ‘panic selling’; but this hasn’t yet happened... Prices have currently remained buoyant (increasing by 9%); and as a result, investor morale remained buoyant. There was no immediate sell-off… But things often change very quickly in crypto, and this is when underwhelming can lead to panic as pricing drops. In particular, ‘newbies’ who have recently invested in Bitcoin ETFs might not be used to the asset class’s volatility and when pullbacks occur, they could decide that they prefer a move back to more traditional (and more predictable) vehicles. These ‘knee-jerk’ reactions could still lead to a ‘sell-off’, despite looking at only a ‘moment in time’ being a dangerous way of making investment decisions. TLDR: We might not have seen an immediate slump, but this doesn’t mean we shouldn’t be pre-prepared for one with a sound investment strategy to boot. Taking a Broader View on Volatility… The recent halving of Bitcoin block rewards is foundational to Bitcoin’s well-known four-year cycle. This cycle has been historically closely linked to price, with the cycle progressing through ‘Bull’ (rising prices), ‘Bear’ (falling prices), ‘Accumulation’ (a leveling out of prices), and ‘Expansion’ (steady growth). Understanding this cycle is foundational to an ability to take a much broader view of volatility. In terms of ‘what’s next’, we can expect a lot of analysis around any retracements (minor pullbacks or changes in the direction of a financial instrument in terms of price). These retracements are often temporary in nature and do not necessarily indicate a shift in the larger trend. TLDR: In analyzing your next investment move, it’s important to understand what point we are at in the asset cycle. Playing the ‘Long Game’ Seasoned investors all tell us that playing the ‘long game’ is often far wiser than making knee-jerk decisions. As the saying goes, time in the market beats timing the market. Given the crypto market’s volatility, strategies you can employ include: Dollar cost averaging (DCA): Regularly invest fixed amounts regardless of market conditions to average out costs and reduce risk. The hold-on-for-dear-life (HODL) strategy: Hold onto assets long-term despite market fluctuations, focusing on fundamentals rather than short-term movements. Diversification: Spread investments across different assets (such as types of coins) to minimise risk from volatile market swings. ** Too many investors don’t ‘Keep calm and invest on’, getting caught up in ‘timing the market’ in terms of entry or running aground when the market becomes more volatile. An ability to confidently navigate volatility is key to avoiding being a ‘Sirius’ and will help you have the confidence to invest, HODL, and sell successfully. **Disclaimer: Crypto is volatile, carries risk, and the value can go up and down. Past performance is not an indicator of future returns. Please do your own research. The transaction that first gave Bitcoin any sort of monetary value happened in October 2009 when a Finnish computer science student Martti Malmi (‘Sirius’) sold 5,050 coins for $5.02, meaning each Bitcoin was worth $0.0009. In today’s terms, if he had held on to his coins, he’d be (circa) NZ$555,500,000 richer. Today, we all know “someone who knows someone” who invested around that time and has become a multimillionaire; and we’re kicking ourselves for not doing the exact same thing… The transaction that first gave Bitcoin any sort of monetary value happened in October 2009 when a Finnish computer science student Martti Malmi (‘Sirius’) sold 5,050 coins for $5.02, meaning each Bitcoin was worth $0.0009. In today’s terms, if he had held on to his coins, he’d be (circa) NZ$555,500,000 richer. Today, we all know “someone who knows someone” who invested around that time and has become a multimillionaire; and we’re kicking ourselves for not doing the exact same thing… With the fourth Bitcoin halving firmly in our rearview mirror and some very recent all-time highs for Bitcoin, new investors (or even existing ones wanting to build or increase their crypto portfolio) might be asking if they’ve waited too long to invest… halving On the other hand, those who have HODLd - or ‘held on for dear life’ - for a while might be fretting about the lack of an immediate, dramatic change in price over the past weekend. An Immediate Ascent Is Always Unlikely… An Immediate Ascent Is Always Unlikely… In the past, halvings have been followed by periods of increased demand and price surges due to the dynamics of supply-demand - but this is never immediate and market dynamics, sentiment, and regulatory factors all influence Bitcoin's price trajectory, making a straight-line ‘ascent’ unlikely. While analysts anticipate an upward trend (which has been the case historically post-halving), the reality is nuanced, and these events are often followed by periods of consolidation and correction - including rallies, reactions, and a lot of volatility on (hopefully) the way up. TLDR: If you were expecting prices to skyrocket overnight, you should have been reading my blogs sooner to get those expectations in check! TLDR: If you were expecting prices to skyrocket overnight, you should have been reading my blogs sooner to get those expectations in check! The Danger of Letting Disappointment Drive Decision-Making The Danger of Letting Disappointment Drive Decision-Making Some analysts predicted that the halving would trigger an immediate price slump that would lead to widespread ‘panic selling’; but this hasn’t yet happened... Prices have currently remained buoyant (increasing by 9%); and as a result, investor morale remained buoyant. There was no immediate sell-off… But things often change very quickly in crypto, and this is when underwhelming can lead to panic as pricing drops. In particular, ‘newbies’ who have recently invested in Bitcoin ETFs might not be used to the asset class’s volatility and when pullbacks occur, they could decide that they prefer a move back to more traditional (and more predictable) vehicles. These ‘knee-jerk’ reactions could still lead to a ‘sell-off’, despite looking at only a ‘moment in time’ being a dangerous way of making investment decisions. TLDR: We might not have seen an immediate slump, but this doesn’t mean we shouldn’t be pre-prepared for one with a sound investment strategy to boot. TLDR: We might not have seen an immediate slump, but this doesn’t mean we shouldn’t be pre-prepared for one with a sound investment strategy to boot. Taking a Broader View on Volatility… Taking a Broader View on Volatility… The recent halving of Bitcoin block rewards is foundational to Bitcoin’s well-known four-year cycle. This cycle has been historically closely linked to price, with the cycle progressing through ‘Bull’ (rising prices), ‘Bear’ (falling prices), ‘Accumulation’ (a leveling out of prices), and ‘Expansion’ (steady growth). Understanding this cycle is foundational to an ability to take a much broader view of volatility. In terms of ‘what’s next’, we can expect a lot of analysis around any retracements (minor pullbacks or changes in the direction of a financial instrument in terms of price). These retracements are often temporary in nature and do not necessarily indicate a shift in the larger trend. TLDR: In analyzing your next investment move, it’s important to understand what point we are at in the asset cycle. TLDR: In analyzing your next investment move, it’s important to understand what point we are at in the asset cycle. Playing the ‘Long Game’ Playing the ‘Long Game’ Seasoned investors all tell us that playing the ‘long game’ is often far wiser than making knee-jerk decisions. As the saying goes, time in the market beats timing the market. Given the crypto market’s volatility, strategies you can employ include: Dollar cost averaging (DCA): Regularly invest fixed amounts regardless of market conditions to average out costs and reduce risk. Dollar cost averaging (DCA): Regularly invest fixed amounts regardless of market conditions to average out costs and reduce risk. The hold-on-for-dear-life (HODL) strategy: Hold onto assets long-term despite market fluctuations, focusing on fundamentals rather than short-term movements. The hold-on-for-dear-life (HODL) strategy: Hold onto assets long-term despite market fluctuations, focusing on fundamentals rather than short-term movements. Diversification: Spread investments across different assets (such as types of coins) to minimise risk from volatile market swings. ** Diversification: Spread investments across different assets (such as types of coins) to minimise risk from volatile market swings. * * Too many investors don’t ‘Keep calm and invest on’, getting caught up in ‘timing the market’ in terms of entry or running aground when the market becomes more volatile. An ability to confidently navigate volatility is key to avoiding being a ‘Sirius’ and will help you have the confidence to invest, HODL, and sell successfully. ** Disclaimer: Crypto is volatile, carries risk, and the value can go up and down. Past performance is not an indicator of future returns. Please do your own research. Disclaimer: Crypto is volatile, carries risk, and the value can go up and down. Past performance is not an indicator of future returns. Please do your own research.

Making Cents (Sense!) of Post-Halving Pricing…

Technology shapes every facet of our lives from how we communicate to how we consume stories and the Archie Comics universe, a cornerstone of American pop culture, is embracing this transformation. Goldie Chan, a figure renowned in the tech world for her insightful commentary and innovative thinking, is at the forefront of this evolution, bringing a unique blend of tech-savvy storytelling to the heart of Riverdale. Her latest comic, "BETTY & VERONICA FRIENDS FOREVER: FAIRY TALES”: 'The Frumpy Duckling,'" showcases this fusion, blending the nostalgic charm of Archie with contemporary themes and digital-age sensibilities. Chan's venture into Riverdale is not just another comic book story; it's a narrative that reflects our modern world's complexities, wrapped in the comforting aesthetics of the Archie universe. "The Frumpy Duckling," starring Cassie Cloud, is a modern fairytale that echoes the timeless theme of transformation, yet it's imbued with elements that speak directly to the digital generation. References to cottagecore, a trend that gained momentum on social media platforms, alongside a nod to "The Devil Wears Prada," infuse the story with a fashion-forward sensibility that resonates with today's readers. This sneak peek of ‘The Frumpy Duckling” was done by Bill and Ben Galvan, a father-son team, who completed the art for Goldie Chan’s original script. So there exists the generational appeal of the Archie characters is with the Archie Comics internal talent as well. “Writing for Archie is a dream come true. As an avid reader of Archie from my youngest days to a (hopefully) wiser adult, I have grown up with Archie, Betty, Veronica, Jughead, Reggie, Ethel, Sabrina and all the other amazing characters in vast universe of Archie Comics. I love sharing heartwarming, thoughtful and curious stories in Riverdale with these nostalgic and wonderful characters and can’t wait to share my next stories with you all!” offers Goldie Chan, Archie Comics writer. The inclusion of Archie-approved puns like "Let's quack this case" adds a layer of playful engagement, reminding us of the power of language in an age dominated by quick, digital communication. Chan's narrative is a bridge between the print media tradition of comic books and the fast-paced, visually driven culture of social media, showcasing how stories can adapt and thrive in a new era. What makes Chan's contribution to the Archie Comics universe particularly noteworthy is her approach to integrating modern technology themes and digital culture insights into the fabric of her storytelling. This blend of tech awareness with the timeless appeal of Archie represents a significant shift in how stories are told within established universes. Chan is not just writing a comic; she's writing a comic for the digital age, where her characters, though rooted in a classic setting, navigate issues and experiences reflective of today's technologically driven world. "Archie has a distinct place in pop culture of being comfortable and familiar for generations while working to remain fresh and relevant, reflecting current trends.  From passing notes back in the day to texting now, people have the same feelings, people still have crushes and share it all with their best friends. At Archie we allow fans access to all those emotions and universal experiences wrapped up in a fun presentation, this recent one a fairy tale type story of your favorite Archie gang by Goldie." - Mike Pellerito, President and Editor In Chief at Archie Comics. “Since its inception, Archie Comics has always been a reflection of modern society. We keep our fingers on the pulse of pop culture, and want to make sure all our readers can see themselves in our comics; be it trends, fashion, technology, celebrities, or even social issues. Goldie's vibrant personality shines through in her stories, not only continuing our commitment to relevancy but propelling our stories and characters even further forward into the future.” - Jamie Rotante, Senior Director of Editorial, Archie Comics. Her focus on creating woman-focused storylines within this context further amplifies the importance of diversity and representation in media, a conversation that is pivotal in both the tech and creative sectors. By infusing her stories with these themes, Chan is contributing to a broader dialogue about how women are portrayed in media, leveraging the Archie platform to inspire and empower a new generation. The Tech Behind the Tales Chan's work in the Archie universe offers a compelling case study. It's not just the content of the stories that's innovative but also the process behind their creation. The comic book industry, much like the tech industry, has seen significant changes in how content is produced, distributed, and consumed, thanks in part to digital tools and platforms. Exploring her creative process could reveal insights into how digital tools facilitate storytelling, from the use of software for design and layout to social media for marketing and community engagement. Additionally, understanding how Chan leverages her tech background to inform her storytelling could provide valuable lessons for content creators operating at the intersection of these two worlds. Engaging the Digital Generation As we look forward to the release of BETTY & VERONICA FRIENDS FOREVER: FAIRY TALES: 'The Frumpy Duckling,'" it's clear that the future of storytelling lies in the seamless integration of traditional narratives with modern technology. Goldie Chan's work is a testament to the potential of this integration, offering a blueprint for how classic universes like Archie's can evolve to meet the expectations of the digital generation. This approach to comic writing highlights the importance of adaptability, technological literacy, and innovation in storytelling. As the digital landscape continues to evolve, the synergy between technology and tradition in storytelling will undoubtedly become more crucial, with creators like Chan leading the charge. Goldie Chan's innovative return to Riverdale not only entertains but also inspires. It serves as a reminder that in the age of digital transformation, stories have the power to connect us, teach us, and propel us forward, bridging the gap between the world we know and the world we imagine. ** Technology shapes every facet of our lives from how we communicate to how we consume stories and the Archie Comics universe, a cornerstone of American pop culture, is embracing this transformation. Goldie Chan , a figure renowned in the tech world for her insightful commentary and innovative thinking, is at the forefront of this evolution, bringing a unique blend of tech-savvy storytelling to the heart of Riverdale. Her latest comic, "BETTY & VERONICA FRIENDS FOREVER: FAIRY TALES”: 'The Frumpy Duckling,'" showcases this fusion, blending the nostalgic charm of Archie with contemporary themes and digital-age sensibilities. Goldie Chan Chan's venture into Riverdale is not just another comic book story; it's a narrative that reflects our modern world's complexities, wrapped in the comforting aesthetics of the Archie universe. "The Frumpy Duckling," starring Cassie Cloud, is a modern fairytale that echoes the timeless theme of transformation, yet it's imbued with elements that speak directly to the digital generation. References to cottagecore, a trend that gained momentum on social media platforms, alongside a nod to "The Devil Wears Prada," infuse the story with a fashion-forward sensibility that resonates with today's readers. This sneak peek of ‘The Frumpy Duckling” was done by Bill and Ben Galvan, a father-son team, who completed the art for Goldie Chan’s original script. So there exists the generational appeal of the Archie characters is with the Archie Comics internal talent as well. “Writing for Archie is a dream come true. As an avid reader of Archie from my youngest days to a (hopefully) wiser adult, I have grown up with Archie, Betty, Veronica, Jughead, Reggie, Ethel, Sabrina and all the other amazing characters in vast universe of Archie Comics. I love sharing heartwarming, thoughtful and curious stories in Riverdale with these nostalgic and wonderful characters and can’t wait to share my next stories with you all!” offers Goldie Chan, Archie Comics writer. “Writing for Archie is a dream come true. As an avid reader of Archie from my youngest days to a (hopefully) wiser adult, I have grown up with Archie, Betty, Veronica, Jughead, Reggie, Ethel, Sabrina and all the other amazing characters in vast universe of Archie Comics. I love sharing heartwarming, thoughtful and curious stories in Riverdale with these nostalgic and wonderful characters and can’t wait to share my next stories with you all!” offers Goldie Chan, Archie Comics writer. The inclusion of Archie-approved puns like "Let's quack this case" adds a layer of playful engagement, reminding us of the power of language in an age dominated by quick, digital communication. Chan's narrative is a bridge between the print media tradition of comic books and the fast-paced, visually driven culture of social media, showcasing how stories can adapt and thrive in a new era. What makes Chan's contribution to the Archie Comics universe particularly noteworthy is her approach to integrating modern technology themes and digital culture insights into the fabric of her storytelling. This blend of tech awareness with the timeless appeal of Archie represents a significant shift in how stories are told within established universes. Chan is not just writing a comic; she's writing a comic for the digital age, where her characters, though rooted in a classic setting, navigate issues and experiences reflective of today's technologically driven world. "Archie has a distinct place in pop culture of being comfortable and familiar for generations while working to remain fresh and relevant, reflecting current trends.  From passing notes back in the day to texting now, people have the same feelings, people still have crushes and share it all with their best friends. At Archie we allow fans access to all those emotions and universal experiences wrapped up in a fun presentation, this recent one a fairy tale type story of your favorite Archie gang by Goldie." - Mike Pellerito, President and Editor In Chief at Archie Comics. "Archie has a distinct place in pop culture of being comfortable and familiar for generations while working to remain fresh and relevant, reflecting current trends.  From passing notes back in the day to texting now, people have the same feelings, people still have crushes and share it all with their best friends. At Archie we allow fans access to all those emotions and universal experiences wrapped up in a fun presentation, this recent one a fairy tale type story of your favorite Archie gang by Goldie." - Mike Pellerito, President and Editor In Chief at Archie Comics. “Since its inception, Archie Comics has always been a reflection of modern society. We keep our fingers on the pulse of pop culture, and want to make sure all our readers can see themselves in our comics; be it trends, fashion, technology, celebrities, or even social issues. Goldie's vibrant personality shines through in her stories, not only continuing our commitment to relevancy but propelling our stories and characters even further forward into the future.” - Jamie Rotante, Senior Director of Editorial, Archie Comics. “Since its inception, Archie Comics has always been a reflection of modern society. We keep our fingers on the pulse of pop culture, and want to make sure all our readers can see themselves in our comics; be it trends, fashion, technology, celebrities, or even social issues. Goldie's vibrant personality shines through in her stories, not only continuing our commitment to relevancy but propelling our stories and characters even further forward into the future.” - Jamie Rotante, Senior Director of Editorial, Archie Comics. Her focus on creating woman-focused storylines within this context further amplifies the importance of diversity and representation in media, a conversation that is pivotal in both the tech and creative sectors. By infusing her stories with these themes, Chan is contributing to a broader dialogue about how women are portrayed in media, leveraging the Archie platform to inspire and empower a new generation. The Tech Behind the Tales The Tech Behind the Tales Chan's work in the Archie universe offers a compelling case study. It's not just the content of the stories that's innovative but also the process behind their creation. The comic book industry, much like the tech industry, has seen significant changes in how content is produced, distributed, and consumed, thanks in part to digital tools and platforms. Exploring her creative process could reveal insights into how digital tools facilitate storytelling, from the use of software for design and layout to social media for marketing and community engagement. Additionally, understanding how Chan leverages her tech background to inform her storytelling could provide valuable lessons for content creators operating at the intersection of these two worlds. Engaging the Digital Generation Engaging the Digital Generation As we look forward to the release of BETTY & VERONICA FRIENDS FOREVER: FAIRY TALES: 'The Frumpy Duckling,'" it's clear that the future of storytelling lies in the seamless integration of traditional narratives with modern technology. Goldie Chan's work is a testament to the potential of this integration, offering a blueprint for how classic universes like Archie's can evolve to meet the expectations of the digital generation. This approach to comic writing highlights the importance of adaptability, technological literacy, and innovation in storytelling. As the digital landscape continues to evolve, the synergy between technology and tradition in storytelling will undoubtedly become more crucial, with creators like Chan leading the charge. Goldie Chan's innovative return to Riverdale not only entertains but also inspires. It serves as a reminder that in the age of digital transformation, stories have the power to connect us, teach us, and propel us forward, bridging the gap between the world we know and the world we imagine. **

Tech and Tradition in Established Universes: Goldie Returns to Riverdale

প্রতিষ্ঠিত মহাবিশ্বে প্রযুক্তি এবং ঐতিহ্য: গোল্ডি রিভারডেলে ফিরে আসেন

Technik und Tradition in etablierten Universen: Goldie kehrt nach Riverdale zurück

Tecnología y tradición en universos establecidos: Goldie regresa a Riverdale

Technologie et tradition dans les univers établis : Goldie revient à Riverdale

स्थापित ब्रह्मांडों में तकनीक और परंपरा: गोल्डी रिवरडेल में लौटता है

確立された世界における技術と伝統: ゴールディがリバーデイルに戻ってくる

확립된 세계의 기술과 전통: Goldie가 Riverdale로 돌아옴

Tecnologia e tradição em universos estabelecidos: Goldie retorna a Riverdale

Технологии и традиции в устоявшихся вселенных: Голди возвращается в Ривердейл

Yerleşik Evrenlerde Teknoloji ve Gelenek: Goldie Riverdale'e Geri Dönüyor

Công nghệ và truyền thống trong các trường đại học đã thành lập: Goldie trở lại Riverdale

既定宇宙中的科技与传统：戈尔迪重返河谷镇

Older and Younger Adults Are Influenced Differently by Dark Pattern Designs: Conclusion & References

Building a (simple) Blog with Rust

Hi guys. Let’s talk about Pointers and Nil, which are related to one another, and why we must be careful when handling these two things in Go. While it is wise to learn from experience it is wiser to learn from the experiences of others ~ Rick Warren Pointer Pointer is a feature that is quite common in low-level languages ​​such as C/C++. A pointer is an object/variable that stores a memory address, which later the object/variable can access the value of that memory address. Pointers, in simple terms, are where one variable references a value to another place (Pointing). One of the uses of pointers is to save memory usage when using data that is quite large. For example, pass a large array to a function. However, pointers are dangerous because of their challenges, so several programming languages, such as Java, Python, Javascript, etc., remove this feature from being accessed directly by programmers, even though they are still used indirectly. Nil Nil or Null indicates the absence of value or that a variable has no value. Pointers are closely related to nil. In the Go programming language, the default value for pointers is nil. Pointer in Go In the Go, a pointer is explicitly indicated by the codebase’s symbols and . The following is an explanation of these two symbols. * & (reference) is used to get the memory address of a variable & (dereference) is used to get the variable’s value pointed to by the pointer. * var1 := 12

// pointer1 refer to var1
pointer1 := &var1

fmt.Println(pointer1)
// Output: 0xc000012028

// Ask the pointer1, what is the value of the object you refer to
fmt.Println(*pointer1)
// Output: 12

var1 = 33
fmt.Println(*pointer1)
// Output: 33 Memory management in the Go is not as broad as in other languages, such as C/C++, where the programmer must allocate and deallocate the program’s memory. Garbage collector makes several challenges in the C/C++ language no longer exist in Go, for example, dangling pointers (pointers that point to memory addresses that have been cleared), memory leaks, and minimizing human error when programming compared to manual memory management. Pointer Problems in Go The pointer problem is closely related to the nil. One of the common problems in Go is the or, in other programming languages, usually known as . This error occurs when a pointer asks the value of a memory address that refers to nil/nothing. This error will invoke panic error. Panic errors in Go can stop the entire running program. Here is an example. nil dereference error Null Pointer Exception package main

import "fmt"

func main() {
    var pointer1 *int // the value is nil
    fmt.Println(*pointer1)
}

// RESULT:
// panic: runtime error: invalid memory address or nil pointer dereference
// [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x480496]

// goroutine 1 [running]:
// main.main()
//  /tmp/sandbox751150285/prog.go:7 +0x16

// Program exited. Before doing anything to the pointer variable, the variable must be checked whether the pointer is nil. package main

import "fmt"

func main() {
    var pointer1 *int
    if pointer1 != nil {
        fmt.Println(*pointer1)
    }
} This is relatively easy to do once we know we use pointers. This can be seen by using the symbols and in the codebase, which explicitly uses pointers in Go. * & The Dangers of Pointers in Go Handling pointers that are used (where there are symbols and in the source code) is easy because they are visible directly when we are programming, and we can easily find these symbols in the codebase using a text editor. explicitly * & The danger arises when there is use of pointers where even the programmer is unaware that they are using pointers. The two symbols and are not shown in the codebase, so the nil check is often missed. This usually continues in code reviews, where reviewers are also often unaware because it requires high accuracy to detect the implicit use of pointers. For example, see the following code. implicit * & package main

import "fmt"

type UserInput struct {
    Name string
    Age  int
}

type UserRepository interface {
    SaveToDB(UserInput) error
}

type userService struct {
    userRepository UserRepository
}

func (s userService) Create(input UserInput) error {
    return s.userRepository.SaveToDB(input)
}

func main() {
    userService := userService{}
    userService.Create(UserInput{Name: "John", Age: 10})
}

// RESULT:
// panic: runtime error: invalid memory address or nil pointer dereference
// [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x45caf0]

// goroutine 1 [running]:
// main.userService.Create(...)
//  /tmp/sandbox2421441321/prog.go
// main.main()
//  /tmp/sandbox2421441321/prog.go +0x10

// Program exited. In the code above, there is no explicit use of pointers, no and symbols in the source code. Where did the pointer error occur, and for what reason? * & The error occurs in the source code above because the value is nil. This is because when initializing, does not include values from , which has a type of interface. Interface in Go has a default value of nil. This error is not detected at compile time. A panic error will occur when the method is invoked. userService.userRepository userService:= userService{} userRepository userService.Create() This can be solved by creating a constructor function like the following source code. package main

type UserInput struct {
    Name string
    Age  int
}

type UserRepository interface {
    SaveToDB(UserInput) error
}

type userRepository struct {
}

func (r userRepository) SaveToDB(input UserInput) error {
    return nil
}

type UserService interface {
    Create(UserInput) error
}

type userService struct {
    userRepository UserRepository
}

func (s userService) Create(input UserInput) error {
    return s.userRepository.SaveToDB(input)
}

func NewUserService(userRepository UserRepository) UserService {
    return &userService{userRepository: userRepository}
}

func main() {
    // initialize using the constructor
    userService := NewUserService(userRepository{})

    // call method
    userService.Create(UserInput{Name: "John", Age: 10})
} The code above works well and can solve the previous problem. The code above is good if only a few interfaces are used. When using several interfaces, human error is possible, for example. type transactionService struct {
   userRepository    UserRepository
   productRepository ProductRepository
   orderRepository   OrderRepository
   paymentRepository PaymentRepository
}

func (s transactionService) Create(input TransactionInput) error {
    user, _ := s.userRepository.Get(input.UserID)
    product, _ := s.productRepository.Get(input.ProductID)
    balance, _ := s.paymentRepository.GetBalance(input.UserID)
    totalPrice := input.Quantity * balance * product.Price
    _, err := s.orderRepository.Save(Order{
        UserID:     user.ID,
        ProductID:  input.ProductID,
        Quantity:   input.Quantity,
        TotalPrice: totalPrice,
    })
    return err
}

func NewTransactionServiceFail1(
    userRepository UserRepository,
    productRepository ProductRepository,
    orderRepository OrderRepository,
    paymentRepository PaymentRepository,
) TransactionService {
    return &transactionService{
        userRepository:    userRepository,
        productRepository: productRepository,
        orderRepository:   orderRepository,
        // MISTAKE 1: Forget to add a parameter here
    }
}

func NewTransactionServiceFail2(
   userRepository UserRepository,
   productRepository ProductRepository,
   paymentRepository PaymentRepository,
   // MISTAKE 2: Forget to add a parameter of an interface
) TransactionService {
   return &transactionService{
       userRepository:    userRepository,
       productRepository: productRepository,
       paymentRepository: paymentRepository,
   }
} The two constructor functions will not error when initializing the struct but will error when the method is called. This is because there is a nil field in the struct. Create() transactionService A strict code review process is needed to prevent this, but this human error often occurs when many interfaces are used. The solution to this problem is to check when the struct is initialized so we can detect errors earlier. The following is an example implementation of this solution. func NewTransactionService(
    userRepository UserRepository,
    productRepository ProductRepository,
    orderRepository OrderRepository,
    paymentRepository PaymentRepository,
) TransactionService {
    svc := transactionService{
        userRepository:    userRepository,
        productRepository: productRepository,
        orderRepository:   orderRepository,
        paymentRepository: paymentRepository,
    }
    if !Valid(svc) {
        panic("please initialize correctly")
    }
    return &svc
}

func Valid(s any) bool {
    v := reflect.ValueOf(s)
    t := v.Type()

    if t.Kind() != reflect.Struct {
        return false
    }

    for i := 0; i < t.NumField(); i++ {
        field := v.Field(i)
        if field.Kind() == reflect.Interface && field.IsNil() {
            return false
        }
    }
    return true
} Using this solution, the function protects the struct so that no fields have a nil value. In this function, each field is looped and checked whether it is of the interface data type and has a nil value. Just remember to be careful when using functions that use . Valid reflection Another example of a nil interface is the interface. error package main

import "fmt"

func main() {
    var err error
    fmt.Println(err.Error())
}

// RESULT:

// panic: runtime error: invalid memory address or nil pointer dereference
// [signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0x480490]

// goroutine 1 [running]:
// main.main()
//  /tmp/sandbox174934985/prog.go:7 +0x10

// Program exited. Nil Default Value In the Go programming language, data types have default values. For example, a string is "" (empty string), float and int = 0, and boolean = false. Several data types use nil as the default value: interface, pointer, slice, map, and channel. These data types are what we need to handle carefully. package default_value

import (
   "testing"

   "github.com/stretchr/testify/require"
)

type I interface {
   M()
}

func TestDefaultValue1(t *testing.T) {
   var pointer *int
   var slice []int
   var m map[string]any
   var channel chan int
   var i I

   require.Nil(t, pointer)
   require.Nil(t, slice)
   require.Nil(t, m)
   require.Nil(t, channel)
   require.Nil(t, i)
}

// Test: Passed Like the interface in the previous discussion, slice, map, and channel are examples of implicit use of pointers in Go because there is no use of and symbols. Of course, this makes us need to be more careful when using these three data types because it may trigger unusual behavior. & * Slice Slices are a nullable data type in Go, unlike arrays. The slice itself has a default value of nil. Let’s take a look at the following source code. package main

import "fmt"

func main() {
    var s []int
    if s == nil {
      fmt.Println("it is nil", s)
    }
}

// Output: it is nil [] The slice has a nil value in that source code, but when printed, it will produce . That’s quite strange, isn’t it?. Next, let’s compare it with the source code below. [] package main

import "fmt"

func main() {
    s := []int{} // using slice literal
    if s == nil {
        fmt.Println("it is nil", s)
    } else {
        fmt.Println("it is not nil", s)
    }
}

// Output: it is not nil [] Nil slice and Empty slice are represented similarly in Go to reduce ambiguity and consistency in how slices are handled in the Go programming language. This is where we need to be careful because not all behavior will be like this. One of them is the default Go library that differentiates those two cases. encoding/json package main

import (
    "encoding/json"
    "fmt"
)

type Example struct {
    NilSlice   []int `json:"nil_slice"`
    EmptySlice []int `json:"empty_slice"`
}

func main() {
     var nilSlice []int
     emptySlice := []int{}

     example := Example{NilSlice: nilSlice, EmptySlice: emptySlice}
     bytes, _ := json.Marshal(example)
     fmt.Println(string(bytes))
}

// Output: {"nil_slice":null,"empty_slice":[]} This won’t be a problem in Go. Still, it will be problematic when it’s used as an API by other applications that use different programming languages that differ in handling nil and empty arrays. I have experienced this case when migrating the backend to Go while the frontend Javascript application should not have changed. Several errors appeared on the front end due to not handling this case. Map Handle nil on the map is more tricky than the slice. We cannot use a map with a default value of nil because it will cause a panic error. package main

import (
   "fmt"
)

func main() {
   var m map[string]any
   m["key"] = 12
   fmt.Println(m)
}

// RESULT:
// panic: assignment to entry in nil map

// goroutine 1 [running]:
// main.main()
//  /tmp/sandbox3489622551/prog.go:9 +0x2c

// Program exited. Therefore, we should always initialize the map using the map literal or the function. make package main

import "fmt"

func main() {
    var m0 = map[int]int{} // map literanl
    var m1 = make(map[int]int) // make function
    m2 := map[int]int{} // map literal
    m3 := make(map[int]int) // make function

    m0[1] = 1
    m1[2] = 2
    m2[3] = 3
    m3[4] = 4

    fmt.Println(m0, m1, m2, m3)
}

// Output: map[1:1] map[2:2] map[3:3] map[4:4] When we want to use multiple keys, we can use a nested map, which is also quite vulnerable to nil errors. package main

import "fmt"

func main() {
    m := map[int]map[int]int{}
    m[1][1] = 1
    fmt.Println(m)
}

// RESULT:
// panic: assignment to entry in nil map

// goroutine 1 [running]:
// main.main()
//  /tmp/sandbox1619142114/prog.go:7 +0x45

// Program exited. Even though it has been initialized as above, items in the nested map must also be initialized to avoid this error. Another way to prevent this is to use a combined key using a string when multiple keys are needed. package main

import "fmt"

func main() {
    // first way (nested map)
    m := map[int]map[int]int{}
    m[1] = map[int]int{}
    m[1][1] = 1

    // second way (combination keys using a string)
    m1 := map[string]int{}
    m1[fmt.Sprintf("%v_%v", 1, 1)] = 1

    fmt.Println(m, m1)
}

// Output: map[1:map[1:1]] map[1_1:1] Channel Channels in Go are a feature to connect one goroutine with another goroutine, where this channel can be used to exchange information between goroutines. Channel is a data type that uses nil as the default value. Channels with nil value cannot be used because they will cause the program to be deadlocked. package main

import (
    "fmt"
)

func main() {
    var done chan bool

    values := []string{"a", "b", "c"}
    for _, v := range values {
        go func(v string) {
            fmt.Print(v)
            done <- true
        }(v)
    }

    for range values {
        <-done
    }

}

// RESULT:
// cab
// fatal error: all goroutines are asleep - deadlock!

// goroutine 1 [chan receive (nil chan)]:
// main.main()
//  /tmp/sandbox2242567277/prog.go:19 +0x149

// goroutine 6 [chan send (nil chan)]:
// main.main.func1({0x4b1d28?, 0x0?})
//  /tmp/sandbox2242567277/prog.go:14 +0x69
// created by main.main in goroutine 1
//  /tmp/sandbox2242567277/prog.go:12 +0x75

// goroutine 7 [chan send (nil chan)]:
// main.main.func1({0x4b11b8?, 0x0?})
//  /tmp/sandbox2242567277/prog.go:14 +0x69
// created by main.main in goroutine 1
//  /tmp/sandbox2242567277/prog.go:12 +0x75

// goroutine 8 [chan send (nil chan)]:
// main.main.func1({0x493458?, 0x0?})
//  /tmp/sandbox2242567277/prog.go:14 +0x69
// created by main.main in goroutine 1
//  /tmp/sandbox2242567277/prog.go:12 +0x75

// Program exited. So, always use the function when initializing channels. make() package main

import (
    "fmt"
)

func main() {
    done := make(chan bool)

    values := []string{"a", "b", "c"}
    for _, v := range values {
        go func(v string) {
            fmt.Print(v)
            done <- true
        }(v)
    }

    for range values {
        <-done
    }
}

// Output: cab Pass By Reference Function parameters with data types that use nil as a default value do not indicate explicit use of pointers (the symbols and ), so we have to check manually. * & package main

import (
   "errors"
   "fmt"
)

type I interface {
    M()
}

type i struct{}

func (i i) M() {}

func fn(i I, ch chan int, s []int, m map[int]int) error {
    fmt.Println(i, ch, s, m)
    return nil
}

// manual check for safety
func fn1(i I, ch chan int, s []int, m map[int]int) error {
    if i == nil {
        return errors.New("i interface nil")
    }
    if ch == nil {
        return errors.New("ch channel nil")
    }
    if s == nil {
        return errors.New("s slice nil")
    }
    if m == nil {
        return errors.New("m map nil")
    }
    fmt.Println(i, ch, s, m)
    return nil
}

func main() {
    fn(nil, nil, nil, nil)
    fn1(i{}, make(chan int), []int{}, map[int]int{})
}

// OUTPUT:
// <nil> <nil> [] map[]
// {} 0xc000076060 [] map[] Summary Handling related to pointers and nil in the Go programming language requires precision and caution so undesirable behavior, such as panic or deadlock, does not occur. Explicit pointers can be checked quickly, but implicit pointers are more challenging. When using a data type with a default value of nil. The general rule I usually use when initializing variables is using (using the operator), which forces us to provide a value before the variable is used. Uses the function and slice literal ( ) and map literal ( ), and prefers to use a map with string keys when multiple keys are needed. short variable declaration := make() []int{} map[int]int{} Improved code review is critical as an initial filter before merging the code with the main codebase. That’s all from me. I hope you get useful insight. Thank You. Also published . here

Pointer and Nil in Go: Reasons Why You Should Be wary

240 Stories To Learn About Astounding Stories

How are you, hacker?
🪐 has got you covered with fresh content from our trending stories of the day! Set email preference . Want to know what's trending right now?: The Techbeat by HackerNoon here Using Witnet to Overcome The Challenges of Developing A Truly Multichain Oracle Network By [ 4 Min read ]
Tomas Ruiz on overcoming the challenges of developing a truly multi-chain oracle network using Witnet. @oraclesummit Read More. A Deep Dive on Digital Identity: Why You Need to Check Out Genies Traits Framework By [ 9 Min read ]
What if your avatar in the Genies Ecosystem encoded not only your visual representation but also who you are – your personality, quirks, and all? @genies Read More. A Beginner's Guide to Understanding SQL Window Functions - Part 2 By [ 8 Min read ]
let us explore more advanced SQL concepts. It may sound a bit complicated at first glance, but I will provide simple examples suitable for beginners... @yonatansali Read More. Unveiling the Best of 2023: Top Stories, Writers, Tech Categories, and Templates! 📚 By [ 5 Min read ]
We've compiled a 2023 roundup of the top most-read stories, top active writers, top tech categories, and even the top most popular templates. Take a look! @editingprotocol Read More. Product Managers, Designers, and Devs: What Does Their Future Look Like in a World Filled With AI? By [ 6 Min read ]
The predictions for the future of tech jobs and the macro trends that will impact our collective experience @kamilaselig Read More. Improving Testing Algorithms: Mathematical Approaches in Software Testing By [ 7 Min read ]
Test design, Code coverage, MC/DC, Boolean algebra, Pairwise testing, Combinatorial testing, Orthogonal arrays, System states @shad0wpuppet Read More. Cybersecurity Essentials: Practical Web App Security Testing Tips for QA Engineers By [ 10 Min read ]
Cybersecurity for QA - web app security: XSS, Header Injections, CSRF, RCE, Command Injection, Web Parameter Tampering, CORS, Content Security Policy (CSP) @shad0wpuppet Read More. Stand Up for the Champion Startups of the Year! By [ 2 Min read ]
The Startups of the Year 2023 winners are announced! @startups Read More. The Noonification: A Deep Dive Into Semantic Segmentation Evaluation Metrics (1/28/2024) By [ 2 Min read ]
1/28/2024: Top 5 stories on the HackerNoon homepage! @noonification Read More. Reverse Proxying — the Backbone of Microservices Architecture By [ 5 Min read ]
Understand how reverse proxies powers almost every service that we use today from monolith to microservices. It is a vital piece of 21st century infrastructure! @infinity Read More. Protect Yourself From Identity Theft By Using Zero-Knowledge Proof, Solidity, and Ethereum By [ 6 Min read ]
Blockchain technology, specifically Zero-Knowledge Proof (ZKP), Solidity, and Ethereum can provide a secure and efficient solution to prevent identity theft. @wise4rmgod Read More. The Real-Time Internet: Visions of AI-Generated Everything By [ 2 Min read ]
I interview an AI engineering expert on her opinion on Jared Ficklin's vision of the Real-Time Internet, where AI generates applications on demand. @liamshotwell Read More. The Best Complex Frontend Architecture: What You Need to Know About Feature-Sliced Design By [ 8 Min read ]
This article discusses the Feature-Sliced Design architecture, as in my opinion, it is the best for complex frontend projects among the available options. @mmmidas Read More. Multi-Class Classification: Understanding Activation and Loss Functions in Neural Networks By [ 25 Min read ]
Multi-class classification NN is used with the softmax activation function on its final layer together with CE loss. The final layer size = classes_number. @owlgrey Read More. Cybersecurity Tips: Vulnerability Scanners Essentials By [ 6 Min read ]
Cybersecurity Vulnerability Scanners Essentials, OWASP ZAP, Burp Suite, Nessus, Sn1per, Metasploit, SQLMap. @shad0wpuppet Read More. Gamification: A New Era in Workplace Experiences By [ 6 Min read ]
Explore the impact of low employee motivation and the role of enterprise gamification in boosting engagement, eliminating friction, and fostering creativity. @igorpaniuk Read More. Bitcoin Mining 2.0 - NFTs and LBH Revolution By [ 8 Min read ]
Discover How Bitcoin Mining is taking a new dimension with the integration of NFTs and LBH @mubarakmuhammadjamiu Read More. How to Use TensorFlow and Cleanvision to Detect Starfish Threats in the Great Barrier Reef By [ 2 Min read ]
Utilizing AI and machine learning, the project employs TensorFlow, Cleanvision, KerasCV, and YOLOv8 to detect harmful starfish in the Great Barrier Reef. @aravindputrevu Read More. LLMs for Dummies - Walkthrough Guide and Glossary By [ 4 Min read ]
Feel like an idiot trying to remember the terms in AI? Don't know your inference from your instruction? Here's a collection of common machine learning terms. @reneeeshaw Read More. Women in Tech: Interview with Anastasia Mironova, Product Designer at WhatsApp London By [ 9 Min read ]
Interview with Anastasia Mironova: sharing her career journey, perspectives on women in tech, and insights into design leadership 🧑‍💻 What happened in your world this week? It's been said that , , . Feeling stuck? We got you covered ⬇️⬇️⬇️ We hope you enjoy this worth of free reading material. Feel free to forward this email to a nerdy friend who'll love you for it.
See you on Planet Internet! With love,
The HackerNoon Team ✌️ @anamiro Read More. writing can help consolidate technical knowledge establish credibility and contribute to emerging community standards ANSWER THESE GREATEST INTERVIEW QUESTIONS OF ALL TIME

The TechBeat: Using Witnet to Overcome The Challenges of Developing A Truly Multichain Oracle Network (1/30/2024)

WISEAR

wisear.io

11-50 employees

Since 2019

COMPANY RANKING

WISEAR

EVERGREEN INDEX #11974

Representing this company? Click here to claim and customize this page!

Wisear WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!

WISEAR

wisear.io

11-50 employees

Since 2019

COMPANY RANKING

WISEAR

EVERGREEN INDEX #11974

RELATED COMPANIESRANK

STORIES ABOUT WISEAR

Representing this company? Click here to claim and customize this page!

Wisear WIKI

Apply to get your Tech Company News Page live on HackerNoon.com today!