TechVibe chats

The Amharic 😭

Let's join guys🙏

One of the things I’m always fascinated by when I meet people older than me, and they don’t necessarily have to be 60+, even someone 5 or 10 years older, is wondering what they were thinking about 10 years ago. Like, how did they survive the things happened back then like corona? What did they learn along the way? What did life look like back then? I find myself comparing their time, experiences, and way of thinking with ours, and honestly, it’s fascinating to think about how much can change in just 10 years. @devwitheyob #thoughts #random

By asking what they were thinking , you are not just learning history you are learning mindset. Keep it man💪

Betam for real

Article of the day Software engineers should avoid endless prompt refinement when working with AI and instead actively write code themselves. Rather than trying to perfect prompts to get AI to generate complete solutions, developers should engage with the code directly by refactoring AI-generated code, writing initial versions for AI review... read the full article 👉 here @devwitheyob #TechVibe #TechVibe #ArticleOfTheDay

Article of the day I am sure, there is a lot more, but hey! couple of hours to learn is not bad for a start. I can say I like some semantics here. It also sort of re-wires my brain a bit. At the end a langauge should be the right tool used for the right job. Here are some of my takeaways from today. Memory Management through Ownership: Unlike Java’s Garbage Collector (GC), Rust manages memory using an ownership system. Each value has a single owner, and when the owner goes out of scope, the memory is freed. Assigning a value to a new variable moves ownership, invalidating the original variable. Borrowing and References: To access data without transferring ownership, Rust uses references, a concept known as “borrowing.” The compiler enforces a key rule: at any given time, you can have either one mutable reference &mut T or any number of immutable references &T, but not both simultaneously. full article 👉 here @devwitheyob #TechVibe #TechVibe #ArticleOfTheDay #RustFundamentals

tele/safari

tele

Sometimes I find myself finishing like 10 things in just two hours. Other times, I pull an all-nighter and get stuck on one thing the whole night 😭 @devwitheyob #TechVibe #random

That's life, guy

I also have noticed that, but most of the time my poor performance is associated with not having a good sleep.

Very good observation

I just saw a YouTube channel that translates MrBeast's content into Amharic, and it has crazy views. This is crazy! 😁 @devwitheyob #TechVibe #random #yt

Fr? show

yeah it is like ቃና

Article of the day I am sure, there is a lot more, but hey! couple of hours to learn is not bad for a start. I can say I like some semantics here. It also sort of re-wires my brain a bit. At the end a langauge should be the right tool used for the right job. Here are some of my takeaways from today. Memory Management through Ownership: Unlike Java’s Garbage Collector (GC), Rust manages memory using an ownership system. Each value has a single owner, and when the owner goes out of scope, the memory is freed. Assigning a value to a new variable moves ownership, invalidating the original variable. Borrowing and References: To access data without transferring ownership, Rust uses references, a concept known as “borrowing.” The compiler enforces a key rule: at any given time, you can have either one mutable reference &mut T or any number of immutable references &T, but not both simultaneously. full article 👉 [ LINK ] @devwitheyob #TechVibe #ArticleOfTheDay #RustFundamentals

waiting for your post when you start learning double linked list in rust 😁

No I'm not actually learning Rust

ohh, ok , well in that case you dogged a bullet lol