Forwarded from Eyu's Terminal
#Internship #employment
Backend - any students with spring boot experience , there is an internship for y'all .DM me at @eyuz_1
Showcasing your projects is appreciated 👍
Backend - any students with spring boot experience , there is an internship for y'all .DM me at @eyuz_1
Showcasing your projects is appreciated 👍
👀4
yoooo 800 subs, guys your are the best thank you so much, and who's the 800th sub drop a comment🔥
U guys will have a give away when we hit 1k😊
@devwitheyob
#TechVibe #800subs
U guys will have a give away when we hit 1k😊
@devwitheyob
#TechVibe #800subs
🎉7🔥2
any chance experienced blockchain developer here, I want to ask some questions please dm me or drop a comment
Why did I quit facebook lol😭😭, I had over 5k followers🫢 when I was at highschool, I just saw it now😁
@devwitheyob
#random
@devwitheyob
#random
😁2😭1
One of the many use cases for agents today is adding new features to existing applications, as well as refactoring and migrating codebases. Because they can operate with full context, they are often better able to understand systems, extend them effectively, and make changes with greater confidence.
@devwitheyob
#AI
@devwitheyob
#AI
❤5
Article of the day
The Object Pool Design Pattern is a creational pattern that reuses existing objects instead of creating new ones every time they are needed. The pool manages a limited number of objects, gives one to the client on request, and accepts it back when the client is done using it.
This is especially useful when object creation is costly or when only a certain number of objects should exist at once. It is commonly used for database connections, threads, sockets, and other resource-heavy objects.
In real-world applications, the client does not create or destroy these objects directly. Instead, it simply requests one from the pool and returns it after use. This can improve performance, reduce resource waste, and make the system more efficient.
@devwitheyob
#DesignPatterns #ArticleOfTheDay
The Object Pool Design Pattern is a creational pattern that reuses existing objects instead of creating new ones every time they are needed. The pool manages a limited number of objects, gives one to the client on request, and accepts it back when the client is done using it.
This is especially useful when object creation is costly or when only a certain number of objects should exist at once. It is commonly used for database connections, threads, sockets, and other resource-heavy objects.
In real-world applications, the client does not create or destroy these objects directly. Instead, it simply requests one from the pool and returns it after use. This can improve performance, reduce resource waste, and make the system more efficient.
@devwitheyob
#DesignPatterns #ArticleOfTheDay
👍4
Forwarded from Robi makes stuff (Robi)
after the story about the random dude that used AI to reverse engineer his dog's cancer and bought 3000$ worth of equipment to engineer a treatment for it that worked, i think humanities end would be from some random person with the same budget making super ebola-aids the same way.
TechVibe
Lately I’ve been struggling to stay focused and productive 😭. I spend a lot of time working, but it still feels like I’m not getting much done. I remember when I was a second yr student, I could watch 5-6 hours of videos, coding, and even work on projects…
Guys, I’ve been thinking about this a lot, like how we can actually level up as engineers, not just rush to get a job or quick income. I personally prefer focusing on learning deeply and getting really good first.
So here’s an idea, what if a small group of us (like 5–10 AAU specially 4k students) meet every day and just grind together? we could go to Abrhot, do LeetCode, read tech articles, work on projects, actually build stuff, review each other’s work, share ideas, prep for interviews, and even share opportunities. And not just that, we actually become friends too, build a strong circle, and create a motivating environment around us where everyone is pushing each other to grow.
Also, after AI, I feel like most of us are losing motivation to really learn. We just ask AI to do things for us, and honestly I hate that feeling.
I feel like this would help us stay consistent, motivated, and learn way faster, especially with feedback and different perspectives.
But the main thing is consistency. Like seriously, no skipping. We need to be patient and also support each other.
I really think this could take us to another level.
What do you guys think?
@devwitheyob
#TechVibe #letsBuildTogether
So here’s an idea, what if a small group of us (like 5–10 AAU specially 4k students) meet every day and just grind together? we could go to Abrhot, do LeetCode, read tech articles, work on projects, actually build stuff, review each other’s work, share ideas, prep for interviews, and even share opportunities. And not just that, we actually become friends too, build a strong circle, and create a motivating environment around us where everyone is pushing each other to grow.
Also, after AI, I feel like most of us are losing motivation to really learn. We just ask AI to do things for us, and honestly I hate that feeling.
I feel like this would help us stay consistent, motivated, and learn way faster, especially with feedback and different perspectives.
But the main thing is consistency. Like seriously, no skipping. We need to be patient and also support each other.
I really think this could take us to another level.
What do you guys think?
@devwitheyob
#TechVibe #letsBuildTogether
🔥23❤8