Albert Dugba🇬🇭🚀

Congrats!

Starting a new job today

You’re really raising the bar for tech content. Go Jason. 🔥🚀

awww I grew up listening to some wild jazz from here. May she RIP

v0 - D3 Bubble Chart – v0 by Vercel A v0 template

I created this data-visualization with v0
v0.dev/chat/communi...

📣 Time to announce "create-tsrouter-app" or CTA, a drop-in CRA replacement:

- Powered by @vite.dev, TanStack Router, built by
@jherr.dev
- TypeScript/Tailwind/File-Route templates (more coming)
- Full control over Vite and (soon) upgradeable to TanStack Start

www.youtube.com/watch?v=10J6...

Day 6
I covered goroutines and channels
#100daysofcode #go #buildinpublic

Day 5 #100DayOfGo
I covered:
1. Maps
2. Interfaces
3. Net/Http

I spent a good amount of time on the go documentation reading about the net/http package

Congrats let me be your +1 subscribers 😀

Esbuild is such a powerful build tool

This is a good read.

I also learnt about pointers in Go.They store the memory address of another variable that can be useful especially when you want to mutate the data or state, it mutates the original data which is performant

Day 4, on Structs
Structs in a data structure in go. Surface to say, they're just like an object in JavaScript where you define the shape or interface of something. You can embed multiple structs in another struct which is straightforward. You can also have a receiver function on them
#100daysofCod

bittersweet news: today is my last day at Bluesky. 💙 i’m very thankful to the team for letting me learn many new things on the job (including React Native). i’m wishing them luck in the improbable — but inevitable — task of making decentralized social media usable and competitive.

Happy new month. We go again

I also got a hung of receiver functions, they're basically like an oop concept, methods defined on that type

the content must be converted from byte slices back to strings.

Now let's talk about retrieving that data from the file system. The "os" has a utility that can be used to get the data "os.ReadFile"
Reading a data from the file system returns the []byte slice and an error

In the slice of todos, since we have a slice of todos in a string type,

the slices of todos needs to be converted to string and then to a byte slice before writing to a file

```
os.WriteFile(fileName, []byte(t.toString()), 0666)
```

to save to the file system. Before that, let's talk about byte slices. So byte slices is the normal slices but with a type of byte which is another data type commonly used to handle binary data. Now in our case, persisting the list of data todos needs to be in a type byte slice. but first,

Writing to the filesystem in go requires the use of the 'os' package which has so many utilities which provides platform related interfaces. Writing to a file uses the syntax `os.WriteFile` which creates and overrides an existing data
In my little todo program, I have slices of todos that I needed

Day 3 I learned about
1. Reading and writing to the file system
2. Receiver functions
3. Error handling
#100DaysofGo #100DaysOfCoding #Golang #programming

in slices, there is only way to loop through data which is the `for loop` like this which is straightforward

3. Functions: Just like in any other programming languages, functions in go is declared with the func keyword with the name and the body

depending on what the function is doing you might need to add a return type

for example a function returning a string should have a return type of string

be used within functions, not at the package level.

2. Slices and Arrays: So slices are just dynamic arrays just like we have in javascript which can grow and shrink in size whereas arrays are like [tuples] in typescript: they have a fixed size element

1. Variables: In go I learned that, there are two primary ways to declare variables:
- using the var keyword and using the short variable

The `var` is used to specify a variable with a specific type which can be done at the package level and inside functions

The variable with the `:=` can only be

Day 2: Picking back up where I left off. I covered
1. Variables
2. Slices and Arrays Data types
3. Functions

#100DaysOfCode #100daysOfGo #coding #software

So running the code looks for the main package to start the execution process into the machine code. I also learnt that it needs to be followed by a main function which serves as the entry point of the program. I also learnt about the the fat which is like console.log for JavaScript

Go code snippet

Day 1
So I started learning go today. I started by installing the go via home-brew. I learn about;
- package main: The package main is the entry point to every go program which compiles the go program into a machine code
#golang #go #programming #learning #coding #developer #100DaysOfCode

Thank you