Safak

☁️

[Safak @sfkdev]

@TeslaClubTurkey Aynı durum bizde de geçerli. Paranın tamamını ödemiş olmak ve aracı alamamak büyük mağduriyet. Üstelik hala ne zaman alacağımızın bir garantisi yok.

[Safak @sfkdev]

I am implementing local CI as similarly it’s released in @rails 8.1 recently, using justfile, mill, uv, and mise.

I have been using mostly Gitlab and Jenkins to date but honestly I feel a lot overwhelmed lately with managing complexity. All I need is local-first experience

[Safak @sfkdev]

Any recommendations for a 2-week travel during December? We want to get a realistic experience with my wife before we migrate there for a few years. We’d be living in Porto as my company has an office there

[Safak @sfkdev]

Considering moving to Portugal in a few months with D-3 highly skilled visa. Been following @levelsio experience and watched his podcast with @miguel_milhao recently

[Safak @sfkdev]

@samlambert do you have any plans to support Azure for b2b companies by any chance?

Usually in sectors like retail, our customers see Amazon as competitor so they prefer Azure and we’re stuck with Azure for Postgres

[Safak @sfkdev]

@samlambert Yes exactly. One example is bazel. Never needed in a startup, just use build tools suitable for your language

[Safak @sfkdev]

@markgurman People in Turkey already pays more than 2K for any base model including taxes

[Safak @sfkdev]

@quantscience_ Just use @duckdb

[Safak @sfkdev]

I miss my wife so much that I can’t spend a week without her

[Weston Pace @westoncpace]

Newest blog post out! It's another deep dive into file readers where I talk about all things "fusion": https://t.co/e9PqngD6GL

Except nuclear fusion. If you're looking for that topic then this is definitely the wrong account to follow.

[Werner Vogels @Werner]

I have said it before; you have to do the work. Otherwise, it’s just bs. As more builders choose @rustlang to solve hard problems at scale, it felt time to get my hands dirty. Here’s the Distill CLI, a Rust-powered summarization tool: https://t.co/goAKogsH97 #aws #tinkering

[Thorsten Ball @thorstenball]

Just figured out that btop allows you to click on a process and see its details.

It already was the coolest application. Now it's untouchable.

[Gwen (Chen) Shapira @gwenshap]

I don't want to start a flame war here, but IMO it is a mistake to jump straight to distributed databases (and 90% of the content below is distributed databases) without first learning fundamentals on single node databases.

Here's my 10 things to understand about databases:

1. Relational model. Primary keys, foreign keys, normal form.
2. SQL language. Ideally with advanced SQL (CTE, analytics)
3. ACID and how transactions work
4. Write-ahead log (or binlog) and how it is used. Especially around restarts, recovery and replication.
5. Buffer cache, disk storage layout and how they interact
6. What happens when databases start? when they shut down?
7. Indexes, cluster tables, partitions and other types of database structures.
8. Query parsing, planning and optimizing.
9. MVCC and how to deal with its quirks in your DB of choice
10. Security - authentication, authorization, encryption on wire and at rest.
11. (Bonus) Investigating performance issues and making sense of benchmarks.

Entire world, stuff that 99% of developers use daily. You can be a deep expert without ever looking at distributed databases. And this also serves as strong foundation once you do.

And if you use Postgres, I found this free book super helpful in making sense of things: https://t.co/cPNk493KU5

[Neo Kim @systemdesignone]

If you want to sharpen your system design skills, read these engineering blogs:

[Gwen (Chen) Shapira @gwenshap]

🛠️ Ever dealt with glitches in your SaaS app where actions yield unexpected results? That can be a transaction isolation issue.

I blogged about transaction isolation, how it works in Postgres and how to use the right isolation to build better apps: https://t.co/Qgbd3aSvtX

[Thiago Ghisi @thiagoghisi]

Ten Principles for Growth as an Engineer by Dan Heller:

“These are the most important lessons that I wish I had learned ears earlier than I did; I sure wish someone had sent it to me when I was 22.”

1. Reason about business value: Reason like a CEO. Understand the value of your work to your company, and take responsibility for reasoning about quality, feature richness, and speed. Your job isn't just to write code; your job is to make good decisions and help your company succeed, and that requires understanding what really matters.

2. Unblock yourself: Learn to never, ever accept being blocked; find a way by persuasion, escalation, or technical creativity. Again, your job isn't just to write the code and wait for everything else to fall into place; your job is to figure out how to create value with your efforts.

3. Take initiative: The most common misconception in software is that there are grown-ups out there who are on top of things. Own your team's and company's mission. Don't wait to be told; think about what needs doing and do it or advocate for it. Managers depend on the creativity and intelligence of their engineers, not figuring it all out themselves.

4. Improve your writing: Crisp technical writing eases collaboration and greatly improves your ability to persuade, inform, and teach. Remember who your audience is and what they know, write clearly and concisely, and almost al-wavs include a tl;dr above the fold

5. Own your project management: Understand the dependency graph for your project, ensure key pieces have owners, write good summaries of plans and status, and proactively inform stakcholders of plans and progress. Practice running meetings! All this enables you to take on much bigger projects and is great preparation for leadership.