Václav Stolín

Every second counts.

My recommended materials for cracking your next technical interview Coding - Leetcode - Cracking the coding interview book - Neetcode System Design Interview - System Design Interview Book 1, 2 by Alex Xu, Sahn Lam - Grokking the system design by Design Guru - Design Data-intensive Application book Behavioral interview - Tech Interview Handbook (Github repo) - A Life Engineered (YT) - STAR method (general method) OOD Interview - Interviewready - OOD by educative - Head First Design Patterns Book Mock interviews - Interviewingio - Pramp - Meetapro Apply for Jobs - Linkedin - Monster - Indeed Over to you: What is your favorite interview prep material? -- Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages): bit.ly/bbg-social

{{ toYaml .Values.imagePullSecrets | indent 8 }}

Explaining JSON Web Token (JWT) to a 10 year old Kid. Imagine you have a special box called a JWT. Inside this box, there are three parts: a header, a payload, and a signature. The header is like the label on the outside of the box. It tells us what type of box it is and how it's secured. It's usually written in a format called JSON, which is just a way to organize information using curly braces { } and colons : . The payload is like the actual message or information you want to send. It could be your name, age, or any other data you want to share. It's also written in JSON format, so it's easy to understand and work with. Now, the signature is what makes the JWT secure. It's like a special seal that only the sender knows how to create. The signature is created using a secret code, kind of like a password. This signature ensures that nobody can tamper with the contents of the JWT without the sender knowing about it. When you want to send the JWT to a server, you put the header, payload, and signature inside the box. Then you send it over to the server. The server can easily read the header and payload to understand who you are and what you want to do. Over to you: When should we use JWT for authentication? What are some other authentication methods? – Subscribe to our weekly newsletter to get a Free System Design PDF (158 pages): bit.ly/3KCnWXq

when they ask how Kubernetes works

When a pod doesn'y have memory limits and brings the whole node down

Explaining 8 Popular Network Protocols in 1 Diagram. The method to download the high-resolution PDF is available at the end. Network protocols are standard methods of transferring data between two computers in a network. 1. HTTP (HyperText Transfer Protocol) HTTP is a protocol for fetching resources such as HTML documents. It is the foundation of any data exchange on the Web and it is a client-server protocol. 2. HTTP/3 HTTP/3 is the next major revision of the HTTP. It runs on QUIC, a new transport protocol designed for mobile-heavy internet usage. It relies on UDP instead of TCP, which enables faster web page responsiveness. VR applications demand more bandwidth to render intricate details of a virtual scene and will likely benefit from migrating to HTTP/3 powered by QUIC. 3. HTTPS (HyperText Transfer Protocol Secure) HTTPS extends HTTP and uses encryption for secure communications. 4. WebSocket WebSocket is a protocol that provides full-duplex communications over TCP. Clients establish WebSockets to receive real-time updates from the back-end services. Unlike REST, which always “pulls” data, WebSocket enables data to be “pushed”. Applications, like online gaming, stock trading, and messaging apps leverage WebSocket for real-time communication. 5. TCP (Transmission Control Protocol) TCP is is designed to send packets across the internet and ensure the successful delivery of data and messages over networks. Many application-layer protocols build on top of TCP. 6. UDP (User Datagram Protocol) UDP sends packets directly to a target computer, without establishing a connection first. UDP is commonly used in time-sensitive communications where occasionally dropping packets is better than waiting. Voice and video traffic are often sent using this protocol. 7. SMTP (Simple Mail Transfer Protocol) SMTP is a standard protocol to transfer electronic mail from one user to another. 8. FTP (File Transfer Protocol) FTP is used to transfer computer files between client and server. It has separate connections for the control channel and data channel. – Subscribe to our newsletter to download the high-resolution PDF. After signing up, find the download link on the success page: bytebytego.ck.page/3581072b8e

Hard times create strong programmers Strong programmers create frameworks Frameworks create weak programmers Weak programmers create hard times

Java 21 is now available! #Java21 #JDK21 #OpenJDK Download Now: social.ora.cl/6018P4fbj Release notes: social.ora.cl/6019P4fbd API Javadoc: social.ora.cl/6011P4fb5 Features: social.ora.cl/6013P4fb9 Inside Java on JDK21: social.ora.cl/6016P4fbY

Keeping up with the times

"If you don't design right from the beginning, every piece of the code you write is a patch" – Leslie Lamport

👨‍💻Managing difficult software engineers👨‍💻 The Procrastinator The Lone Wolf The Negative Nancy The Over-Promiser The Know-It-All The Silent Type The Perfectionist The Unreliable One The Conflict Instigator The Burned-Out Employee vadimkravcenko.com/shorts/managin…

Lmao I love Linux

Software estimates are one of the oldest lies we tell ourselves. We all know they don't work, but pretend they mean something and later feel enraged when shit hits the fan. I focused a big part of my undergrad on software estimation. After graduating, I wrote plenty about the topic. Then, I started working for a company where I spent years researching how to make better estimates. We sold multiple millions of dollars of software using the tools I built. I read everything there's to read. I could recite Steve McConnel's "Software Estimation" book from top to bottom. Here is the most important lesson I learned: People can't estimate software. It doesn't matter who they are or how much experience they have. Estimating software reliably is science fiction. And the best part: They will ask you to estimate something. They will tell you they understand it's not exact. They will promise they won't hold you accountable. And then they will. They always do. There are two solutions for this. Let's start with my recommendations for those who don't have a choice: 1. Remove "quick," "simple," "straightforward," "easy," and every similar word from your dictionary. Never use them. Don't let others use them when referring to your work. 2. Never volunteer an estimate. Everything you say will be used against you. 3. When forced, estimate work you know you can complete today. Always estimate with a range: "It will take me 2 - 4 hours." 4. Estimate anything you won't do today in days and weeks. Say, "I should finish that feature sometime this week." Do not estimate future work in hours. But we all know your manager will force you to give an estimate. Here is what you should do: 1. Estimate how long you think it will take you to complete the task. 2. Multiply the number by 3. This will be the lower range of your estimate. 3. Double the lower range of the estimate. This will be the upper range. Example: If you think something will take you 1 day of work, say "between 3 and 6 days." Here is the funny part: It won't take you between 3 - 6 days. This is as much bullshit as any other method you can think of. The true solution for this problem: Work for a company that doesn't care about estimates.

Use Kubernetes, they said. It is fun, they said.

člověk, co má ve jméně Scala, píše knihy o Kotlinu (-: leanpub.com/kotlin_functio…