Tonight on CodeNight voice chat, we'll be discussing:

- Is bun the revolutionary technology that can replace Node.js for good?

- Why is Wi-Fi usage not allowed in Telebirr for security reasons?

Join us tommrow night 2:00 LT to learn more from experts in the field and share your own insights.

Bun is a new JavaScript runtime that promises to be faster and more efficient than Node.js. It's still under development, but it's already gaining popularity among developers. Is bun the future of JavaScript runtime? We'll discuss the pros and cons of bun and Node.js, and try to answer the question: can bun replace Node.js for good?

Telebirr is a mobile money service in Ethiopia. It's used by millions of people to send and receive money, pay bills, and buy goods and services. But why is Wi-Fi usage not allowed in Telebirr? We'll discuss the security risks associated with using Wi-Fi with Telebirr, and what users can do to stay safe.

Whether you're a seasoned developer or just starting out, CodeNight is a great place to learn about the latest trends and technologies in the field. We hope to see you there!

Hello Everyone

CodeNight voice chat is starting in a minute! We'll be covering some interesting topics tonight.

To join, simply click on the following link:
https://news.1rj.ru/str/CodeNight?videochat=46e67ca85d255d53fd

We hope to see you there!

P.S. Don't forget to invite your friends and coworkers who might be interested on this week topics

Predicting the future isn't magic, it's artificial intelligence

               — Dave Waters

This week's Dagu session focuses on Business in DATA/ML/AI (Dagu 2.13) with Micheal E. Kebede

Michael has paved a remarkable career path at the forefront of tech and research. 🎓 Academic: Michael holds a Bachelor's in Economics, cultivating analytical and problem-solving skills vital for his data-driven journey. Currently pursuing a Master's in Data Science, he's poised to harness data's power innovatively. 📊 Professional: Michael's hands-on experience in tech and research sectors has honed his data expertise. His analytical prowess unlocks insights from vast datasets, aiding informed decision-making.

📅 Friday - Oct 6, 2023
⏲ 9:00 PM | 3:00 LT
📍 https://meet.google.com/pmj-tfvj-rmc


#Rotary #District9212 #RotaractEthiopia #WeAreOne #CreateHopeInTheWorld #rclewet #PD #Warka #Dagu


Follow Us 👇
Telegram | Instagram | Linkedin

For those who want to build something but don't know how

https://github.com/davidetaibi/Microservices_Project_List

Write more useless software

https://ntietz.com/blog/write-more-useless-software/

System design: Netflix

https://link.medium.com/6YMTAuzq3Db

The Mind Behind Windows: Dave Cutler Interview

https://www.youtube.com/watch?v=xi1Lq79mLeE

Ps. For further info read the book Show Stopper: The Breakneck Race to Create Windows NT and the Next Generation at Microsoft

Resilience

System X can adapt to unanticipated disturbances.

"Resilience is seen not as a property, but as a capability: A capability to recognize the boundaries of safe operations, a capability to steer back from them in a controlled manner, a capability to recover from a loss of control if it does occur. And a capability to detect and recognize the phase of operation when the margins are skipped or crossed."

Sidney Dekker, Drift Into Failure

📍Exciting news! We are happy to announce that Zayride has now fully integrated our services and started using GebetaMaps API services. Glad to have you on board.

@gebetamaps


LinkedIn | Twitter | Instagram | Website

If you're a junior software engineer or just getting started in SWE, you need to understand this...


The language or framework in which you develop is not the primary technical challenge of programming. So many people just getting started seem to think "ok great, so if I learn Python I'll be able to build software." Please understand that understanding a programming language is one practically insignificant aspect of programming.

Here is a non-exhaustive list of some of the concerns you address when writing software:

* Clearly defining/understanding the problem specification
* Understanding how the problem impacts the user
* Understanding if your solution will delight the user
* Composing a simple and extensible code architecture
* Building and choosing architectural components that will solve your problem over time, such as data stores, caches, proxies, queues, cloud services, etc.
* Choosing the right build and workflow tools
* Testability (unit tests, integration tests, e2e tests)
* Observability (metrics, logs, traces)
* Performance
* Readability
* Continuous Integration
* Deployment Strategy
* Probing / Synthetics strategy
* Familiarity of team with the chosen technology stack
* Admin tooling support
* Documentation
* Knowledge domain gaps in the problem area (and how to fill them)
* Reliability strategy
* Understanding the context of the decisions in the existing system
* Understanding the logic of complex algorithms in production

The sooner you accept this fact, the better. Yes, it's great to write code in a manner idiomatic to your given language and write syntactically correct code (compilers can help with the latter). That said, this is kind of table stakes. So, please take this into consideration if you decide to enter this field; it's more involved than you think despite what bootcamps might tell you.

credit to Demitri Swan

You can find me on
LinkedIn | Twitter | GitHub