Kamal 1.0 has shipped. Deploy your web apps anywhere from bare metal to cloud VMs with zero-downtime, rolling restarts, asset bridging, and more. No advanced degree in container orchestration needed. https://t.co/ILkHFgfb48
There are 3 types of frontend developers:
- Devs who love JS and dislike TS
- Devs who love TS and dislike JS
- Devs who dislike TS but dislike JS even more
Most new Linux users do not understand the difference between
- Terminal
- Command line
- Shell
- Prompt
Here's what you should know about it 👇
Terminal: It is a graphical application that runs a shell by default. There can be many terminal emulator applications like Terminator, Konsole etc.
Shell: It is difficult to "visualize" separately from the terminal. The terminal runs a shell, usually Bash shell. Like terminals, there are various shells as well, zsh, bash, fish etc.
Prompt: This is what you see before the space where you type the commands. There is no set standard for the prompt. In some old terminals, you would just have a blinking cursor to the place where you can type the commands. In modern terminals, prompt gives you some information like username, hostname and current working directory.
Command line: It is not something specific to Linux. Every operating system has a command line interface. Many programming languages have command line interfaces. It’s a term for the interface where you can run and execute commands.
Typically, you type the commands in a terminal after the prompt and the commands are interpreted by the shell.
@dhh What happened with “Until the end of the internet” ? When Google deprecates things is bad, but unsupporting TypeScript is ok? Isn’t it double standards? https://t.co/yw5wmSFAqR
Top 5 Software Architectural Patterns
In software development, architecture plays a crucial role in shaping the structure and behavior of software systems. It provides a blueprint for system design, detailing how components interact with each other to deliver specific functionality. They also offer solutions to common problems, saving time and effort and leading to more robust and maintainable systems.
However, with the vast array of architectural styles and patterns available, it can take time to discern which approach best suits a particular project or system. Aims to shed light on these concepts, helping you make informed decisions in your architectural endeavors.
To help you navigate the vast landscape of architectural styles and patterns, there is a cheat sheet that encapsulates all. This cheat sheet is a handy reference guide that you can use to quickly recall the main characteristics of each architectural style and pattern.
Watch the full video explanation here: https://t.co/oFLYb7byVO
Scrum is a cancer.
I've been writing software for 25 years, and nothing renders a software team useless like Scrum does.
Some anecdotes:
1. They tried to convince me that Poker is a planning tool, not a game.
2. If you want to be more efficient, you must add process, not remove it. They had us attending the "ceremonies," a fancy name for a buttload of meetings: stand-ups, groomings, planning, retrospectives, and Scrum of Scrums. We spent more time talking than doing.
3. We prohibited laptops in meetings. We had to stand. We passed a ball around to keep everyone paying attention.
4. We spent more time estimating story points than writing software. Story points measure complexity, not time, but we had to decide how many story points fit in a sprint.
5. I had to use t-shirt sizes to estimate software.
6. We measured how much it cost to deliver one story point and then wrote contracts where clients paid for a package of "500 story points."
7. Management lost it when they found that 500 story points in one project weren't the same as 500 story points on another project. We had many meetings to fix this.
8. Imagine having a manager, a scrum master, a product owner, and a tech lead. You had to answer to all of them and none simultaneously.
9. We paid people who told us whether we were "burning down points" fast enough. Weren't story points about complexity instead of time? Never mind.
I believe in Agile, but this ain't agile.
We brought professional Scrum trainers. We paid people from our team to get certified. We tried Scrum this way and that other way. We spent years doing it.
The result was always the same: It didn't work.
Scrum is a cancer that will eat your development team. Scrum is not for developers; it's another tool for managers to feel they are in control.
But the best about Scrum are those who look you in the eye and tell you: "If it doesn't work for you, you are doing it wrong. Scrum is anything that works for your team."
Sure it is.
While everyone is speculating on Twitter’s blue tick, Elon has taken private one of the largest data sources on earth to train AI on human interactions and thoughts. And you thought Google capture was clever/invasive.
In AI, he who has the largest proprietary data sets wins.
Rendering on the web is a spectrum. Static HTML? SSR? Streaming? Here we cover options & trade-offs: https://t.co/zrV4L9gJmm & https://t.co/IupiSfNvqN
Being busy all the time is not cool anymore. We should stop glorifying the Hustle Culture, overbooked calendars, and multitasking.
I did this for a long time, which harmed me and my team— check out my blog post for the whole story.