-
Notifications
You must be signed in to change notification settings - Fork 332
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
eb27094
commit d1e71d7
Showing
1 changed file
with
105 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,105 @@ | ||
**Jerod Santo:** | ||
|
||
What up, nerds? I'm Jerod and this is Changelog News for the week of Monday, February 3rd, 2025. | ||
|
||
Last week's freak out about DeepSeek subsided after [people realized](https://semianalysis.com/2025/01/31/deepseek-debates/#training-cost) that its $5.6 million price tag was "just the GPU cost of the pre-training run" and the *actual total cost* is likely up in the billions where we'd expect it to be. | ||
|
||
This week's freak out is all about the tariff-induced trade war. What will next week's freak out be? Hang tight, friends. I'm sure the writers will come up with *something*... | ||
|
||
Ok, let's get into this week's developer news worth your attention | ||
|
||
**Break:** | ||
|
||
**Jerod Santo:** | ||
|
||
[Everyone knows your location](https://timsh.org/tracking-myself-down-through-in-app-ads/) | ||
|
||
After learning of a massive data leak that exposed 2k+ apps secretly collecting geolocation data without user consent, Tim "Sh" looked into the list and found three apps he has installed on his iPhone in the list. That gave him an idea... could he track himself down externally, e.g. to buy his geolocation data leaked by some application? | ||
|
||
So, he grabbed an old iPhone 11, restored it to factory defaults with a brand new Apple ID, set up Charles Proxy to record all traffic coming in/out, installed a single game (Stack by KetchApp), and logged all his findings. The results are troubling, but not surprising. He even made a flowchart of the data coursing its way through the network. Finishing with | ||
|
||
> This is the worst thing about these data trades that happen constantly around the world - each small part of it is (or seems) legit. It's the bigger picture that makes them look ugly. | ||
**Break:** | ||
|
||
**Jerod Santo:** | ||
|
||
[Comfortably monitor your Internet traffic](https://sniffnet.net) | ||
|
||
After a story like the last one, I figured you might want a quick and easy way to monitor your network traffic... Sniffnet is a cross-platform app (written in Rust) that looks like a great, free option. Here's what sets it apart: | ||
|
||
> Sniffnet is a technical tool, but at the same time it strongly focuses on the overall user experience: most of the network analyzers out there are cumbersome to use, while one of Sniffnet's cornerstones is to be usable with ease by everyone. | ||
**Break:** | ||
|
||
**Jerod Santo:** | ||
|
||
[What makes a good team?](https://cate.blog/2025/01/21/what-makes-a-good-team/) | ||
|
||
It's easy to know a bad team when you see one. Likewise, good teams are often evident. Most teams, however, are somewhere in the middle. So what actually makes a team *good*? Cate Huston takes a crack at answering that by listing out attributes of good teams. | ||
|
||
Clarity of purpose (people understand why the team exists) and defined work streams aligned with that purpose (people understand what the team is doing, and why) are where she starts. Layer in good communication and connectedness, and Cate thinks you're off to a great start. From there, it's all about fundamentals: | ||
|
||
> **Good delivery fundamentals** – the team delivering its purpose, consistently and over time | ||
> | ||
> **Good people fundamentals** – the necessary ongoing maintenance work for any team | ||
> | ||
> **Good process fundamentals** – the base level organization that facilitates team effectiveness | ||
**Break:** | ||
|
||
**Jerod Santo:** | ||
|
||
It's now time for Sponsored News! | ||
|
||
[How coding AIs will support large-scale engineering](https://www.augmentcode.com/blog/how-coding-ai-will-support-large-scale-software-engineering) | ||
|
||
This post is from Scott Dietzen, CEO of Augment Code. The TL;DR: | ||
|
||
> Large, long-lived software projects are essential for human endeavor, but profoundly hard to craft and evolve. Today’s coding AIs come up well short of solving the real pain points of software engineering. Augment Code is empowering teams to overcome these challenges — from inspiration to software excellence easily and quickly. | ||
His "7 essential beliefs for delivering an AI for software engineering" are well illustrated. The seventh one will shock you! Just kidding, I hate when people do that. The seventh one is, "AI will actually increase demand for software engineers"... | ||
|
||
**Break:** | ||
|
||
**Jerod Santo:** | ||
|
||
[Seven things I know after 25 years of dev](https://zverok.space/blog/2025-01-27-7things-euruko.html) | ||
|
||
Victor Shepelev, drawing on 25 years of coding experience and 10 years of war experience. Yes, actual war. Victor is a Ukrainian who serves in the Armed Forces. This post is a loose transcript of a keynote he gave at the [EuRuKo conference](https://2024.euruko.org/) in September 2024. I'll give you his seven things, but definitely click through for some deep insights on each one: | ||
|
||
1. You outgrow every framework | ||
2. Patterns and methodologies fail | ||
3. Scale only grows with time | ||
4. Pay attention to stories | ||
5. The goals are truth and clarity | ||
6. This might be a lonely experience | ||
7. Never give up seeking truth | ||
|
||
**Break:** | ||
|
||
**Jerod Santo:** | ||
|
||
[Writing a good design document](https://grantslatton.com/how-to-design-document) | ||
|
||
I made a short plea for design documents (just give us a paragraph, please!) while discussing documentation strategies [on Friends](https://changelog.am/77) a couple weeks back. In this post, Grant Slatton does a much better job of discussing the topic, because he actually tells you *how* to do it (well). What's a design document? | ||
|
||
> A design document is a technical report that outlines the implementation strategy of a system in the context of trade-offs and constraints... Think of a design document like a proof in mathematics. The goal of a proof is to convince the reader that the theorem is true. The goal of a design document is to convince the reader the design is optimal given the situation. | ||
Grant lays out your goal when writing, how to organize it, editing, and more. Then, he drops a bunch of nice tips he's learned over the years: use short paragraphs, use an appendix, etc. Useful stuff! | ||
|
||
**Break:** | ||
|
||
**Jerod Santo:** | ||
|
||
That's the news for now, but also scan the companion newsletter for even more stories. Including, Block introduces codenasem goose, JavaScript Temporal is coming, and an expense tracker that lives in your terminal. | ||
|
||
Oh, and this is episode 130 so that means it's time once again for some [Changelog++](https://changelog.com/++) shout outs! | ||
|
||
**SHOUT OUT** to our newest members: Maryam M, Ceri H, Samuel R, Seth H, David J & Marcel B! | ||
|
||
_We appreciate you_ for supporting our work with your hard-earned cash! | ||
|
||
If [Changelog++](https://changelog.com/++) is new to you, it is our membership program you can join to ditch the ads, get in on bonus content, receive a free sticker pack in the mail & get shout outs like the ones you just heard. Learn all about it at changelog.com/++ | ||
|
||
Have a great week! Leave us a 5-star review if you dig our work, and I'll talk to you again real soon. |