Iss M

Software Engineer Golang

[1NCE @1NCE_IoT]

Explore the intricacies of #IoT connectivity, from understanding your local IP to mastering protocols, with 1NCE #IoTKnowledgebase 💡#Protocols #TechTales

Private IP: https://t.co/4g0L1EXK9f

What is OCCP?: https://t.co/EReMC7L3UW

MQTT, CoAP & LwM2M: https://t.co/zT50G3f1IE

[1NCE @1NCE_IoT]

📢 Exciting news! We are thrilled to announce that 1NCE will be exhibiting at COMPUTEX TAIPEI, the world's leading technology B2B trade show. 🌟 Don't forget to visit our booth S0920a (InnoVEX area) and discover how we can empower your business. See you there!

[Alex Xu @alexxubyte]

Netflix's Tech Stack

[Miki Tebeka @tebeka]

#golang #gem: Use type aliases when refactoring in order not to break APIs.

[1NCE @1NCE_IoT]

📢 We are excited to unveil our latest feature - High Data IoT.💰 Cost-effective rate - only $5 per GB , 🔄 Usage flexibility with a pay-as-you-go model, 🚀 Speed enhancement up to 25 Mb/s, 🌎 Global reach within 168 countries. Explore more: https://t.co/Bg8cYPWr8J
#highdataiot

[1NCE @1NCE_IoT]

🍹Happy Hour is in full swing at 1NCE, located in booth OA3B.20 Outside Area between Halls 3 and 5. Stop by, try our signature cocktails, and let's talk about the future of IoT technology.

#MWC2024 #1NCE #IoTSoftware #IoTConnectivity

[1NCE @1NCE_IoT]

🌟 1NCE invites you to pop by and say hi to us at booth OA3B.20, Outside Area between Halls 3 and 5!

☕️ Swing by for some coffee daily and drinks with 1NCE!

Click here to learn more about 1NCE: https://t.co/supgrtPPzp

#MWC2024 #1NCE #IoTSoftware #IoTConnectivity

[Iss M @gotwiny]

A simple & efficient web crawler.
https://t.co/ge1Muk5gxf
#opensource #golang #SEO #BigData #WebCrawler #DataMining #GitHub #tech

[1NCE @1NCE_IoT]

💡The most essential part is the coverage #1NCE provides for installing 11,000 sensors in Madrid area. 1NCE is about agility, responsibility, and coverage.
Martina Susova, Sensoneo

[Alex Xu @alexxubyte]

The world is a dangerous place.

The diagram below shows some possible network attacks in 7 OSI model layers.

🔹 Application Layer
- Pushing
- Malware injection
- DDos attacks

🔹 Presentation Layer
- Encoding/decoding vulnerabilities
- Format string attacks
- Malicious code injection

🔹 Session Layer
- Session hijacking
- Session fixation attacks
- Brute force attacks

🔹 Transport Layer
- Man-in-the-middle attacks
- SYN/ACK flood

🔹 Network Layer
- IP spoofing
- Route table manipulation
- DDos attacks

🔹 Data Link Layer
- MAC address spoofing
- ARP spoofing
- VLAN hopping

🔹 Physical Layer
- Wiretapping
- Physical tampering
- Electromagnetic interference

Over to you - What did we miss?

--
Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages): https://t.co/uc5M7CdXXC

[Alex Xu @alexxubyte]

Do you believe that Google, Meta, Uber, Twitter, and Airbnb put almost all of their code in one repository?

This practice is called a monorepo.

Monorepo vs. Microrepo. Which is the best? Why do different companies choose different options?

Monorepo isn't new; Linux and Windows were both created using Monorepo. To improve scalability and build speed, Google developed its internal dedicated toolchain to scale it faster and strict coding quality standards to keep it consistent.

Amazon and Netflix are major ambassadors of the Microservice philosophy. This approach naturally separates the service code into separate repositories. It scales faster but can lead to governance pain points later on.

Within Monorepo, each service is a folder, and every folder has a BUILD config and OWNERS permission control. Every service member is responsible for their own folder.

On the other hand, in Microrepo, each service is responsible for its repository, with the build config and permissions typically set for the entire repository.

In Monorepo, dependencies are shared across the entire codebase regardless of your business, so when there's a version upgrade, every codebase upgrades their version.

In Microrepo, dependencies are controlled within each repository. Businesses choose when to upgrade their versions based on their own schedules.

Monorepo has a standard for check-ins. Google's code review process is famously known for setting a high bar, ensuring a coherent quality standard for Monorepo, regardless of the business.

Microrepo can either set their own standard or adopt a shared standard by incorporating best practices. It can scale faster for business, but the code quality might be a bit different.

Google engineers built Bazel, and Meta built Buck. There are other open-source tools available, including Nix, Lerna, and others.

Over the years, Microrepo has had more supported tools, including Maven and Gradle for Java, NPM for NodeJS, and CMake for C/C++, among others.

Over to you: Which option do you think is better? Which code repository strategy does your company use?

--
Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages): https://t.co/4QcX8btXGL

[Iss M @gotwiny]

Domain names collector - Crawl website and find domain name with their availability status.

https://t.co/BQcbLjD4GL

#golang #opensource #web #Crawling #expired #domainnames #SEO #github

[Iss M @gotwiny]

@CODEYko Hahaha what a good question! That way the computer can write the whole code... :D

[Iss M @gotwiny]

@BatsouElef Problem solving.

[Iss M @gotwiny]

@csaba_kissi to tell a machine what exactly to do. and the machine does it.

[Iss M @gotwiny]

@NanouuSymeon The same thing we do every night, try to write better code.

[Iss M @gotwiny]

@NanouuSymeon Yes i do.

[Iss M @gotwiny]

@durosly_ @MrBrandtCox @NanouuSymeon Same here.

[Iss M @gotwiny]

@BatsouElef I learn by working on my own small project. Try to make everything as neet as possible and implementing new technology.
Sometimes i dont have time. Its slow way but when ever i got time i work on them.

[inanc @inancgumus]

Coming in Go 1.20: go test -skip <regexPattern> 🎉

You can skip tests, subtests, or examples using a regular expression.

Proposal → https://t.co/abTS9UqFH7

#golang