𝔻ℝ𝔸𝔾𝕆𝕊ℝ𝕆𝔹𝔼ℝ𝕋ℕ • he/him

Senior Engineer II @Bookingcom •🧔🏻🇷🇴🇬🇧🏳️‍🌈🚴🏻‍♂️  • Tech • Politics • I build @KINNContactsApp • BE Module Lead @CommandShiftHQ. All opinions my own

[𝔻ℝ𝔸𝔾𝕆𝕊ℝ𝕆𝔹𝔼ℝ𝕋ℕ • he/him @dragosrobertn]

👋 there!

Some of you may know that in my free time I work on @KINNContactsApp - a contacts manager for iOS which helps you keep in touch with people.

If you like it, please leave a review https://t.co/gOM2b6fI4a

[Mitchell Hashimoto @mitchellh]

I strongly believe there are entire companies right now under heavy AI psychosis and its impossible to have rational conversations about it with them. I can't name any specific people because they include personal friends I deeply respect, but I worry about how this plays out.

I lived through the great MTBF vs MTTR (mean-time-between-failure vs. mean-time-to-recovery) reckoning of infrastructure during the transition to cloud and cloud automation. All those arguments are rearing their ugly heads again but now its... the whole software development industry (maybe the whole world, really).

It's frightening, because the psychosis folks operate under an almost absolute "MTTR is all you need" mentality: "its fine to ship bugs because the agents will fix them so quickly and at a scale humans can't do!" We learned in infrastructure that MTTR is great but you can't yeet resilient systems entirely.

The main issue is I don't even know how to bring this up to people I know personally, because bringing this topic up leads to immediately dismissals like "no no, it has full test coverage" or "bug reports are going down" or something, which just don't paint the whole picture.

We already learned this lesson once in infrastructure: you can automate yourself into a very resilient catastrophe machine. Systems can appear healthy by local metrics while globally becoming incomprehensible. Bug reports can go down while latent risk explodes. Test coverage can rise while semantic understanding falls. Changes happens so fast that nobody notices the underlying architecture decaying.

I worry.

[𝔻ℝ𝔸𝔾𝕆𝕊ℝ𝕆𝔹𝔼ℝ𝕋ℕ • he/him @dragosrobertn]

@PezRadar Hey Adam,
May be related to the PC issue but playing on PS5 encountering permanent freezes that require game to close since updating to 2.0.4.

Couch co-op is a guaranteed freeze within 3-5 seconds of the second player logging in.

[Ben Lang @benln]

Sam Altman's life advice:

[Ashley Franklin @DifferentAshley]

I never recovered when I stumbled upon this:

[eva @_glorianas]

2016: brexit will give you a better quality of life
2024: if 18 year olds don't want to spend their free time staffing the public services we refuse to fund we'll send them to prison

[Juanjo Valiño @juanjovn]

🎥 The easiest way to create video previews for the App Store:

1. Record from your iPhone with Quicktime: File > New Movie Recording. Select your iPhone Screen

2. iMovie: File > New App Preview. Edit your video (Max 30s)

3. Share Button > App Preview

🥳 Congrats, you've just saved hours fighting with annoying errors when uploading to the App Store Connect

[Jason Kint @jason_kint]

Called it! - classic Facebook move on Thxgiving eve. Unsealed nearly every redaction 233 pages in 40+ state AGs lawsuit alleging FB knowingly harmed children's mental health with addiction for profit. Email me, I'll send to you. Yellow = newly unsealed. 20 tweet summary here. /1

[Andrew Nalband @nalband]

The world’s most popular book on habit change:

Atomic Habits

I've spent the past 100 days summarizing and visualizing the best ideas in the book.

Here's what I learned:

[Alex Napier Holland 🦍 @NapierHolland]

Here’s a visual summary of ‘Atomic Habits’ by James Clear.

(More below)

[Owen Jones @owenjonesjourno]

I presumed everyone knew by now that the tunnels under al-Shifa hospital were built by Israel in the 1980s?

Apparently not!

[Seb Vidal @SebJVidal]

⚠️ Private API of the day:

UINavigationBar’s _UINavigationBarLargeTitleView subview has an _accessoryView property that acts as a sort of bar button item that aligns with the large title label.

This is used in all sorts of system apps like Health, Music, and Podcasts. Enjoy! 🥳

[𝔻ℝ𝔸𝔾𝕆𝕊ℝ𝕆𝔹𝔼ℝ𝕋ℕ • he/him @dragosrobertn]

@RaresCruceat In work — always tests and more than just tests: TDD. In personal/ fun projects, depends on the size of the task. But mostly some tests coverage.

[anna 🖤 @acbdev]

Normalise asking “What’s the tea” for status updates during standup

[Sebastian Sellmair @Sellmair]

After 3 years of blood, sweat and tears:
Kotlin Multiplatform is finally stable 🎉

I never thought that it will take us so much time to pull this off. Let me explain what we did 🧵

[𝔻ℝ𝔸𝔾𝕆𝕊ℝ𝕆𝔹𝔼ℝ𝕋ℕ • he/him @dragosrobertn]

🙌

[Marcio @costhapdev]

Do not include your API keys in the binary. Use a backend to forward requests and add the key.
If for some reason you have no choice but to include them in the binary then pin the identity/certs of the server https://t.co/HVZZsTrveA to prevent keys from being read when passing through an SSL Proxy.
NB: Pinning still won't prevent keys from leaking, it will only make it bit harder to obtain it.

[𝔻ℝ𝔸𝔾𝕆𝕊ℝ𝕆𝔹𝔼ℝ𝕋ℕ • he/him @dragosrobertn]

Interesting question

[Alin C @AlnCht]

How do you protect your API keys used in your app? Do you have any examples?

[𝔻ℝ𝔸𝔾𝕆𝕊ℝ𝕆𝔹𝔼ℝ𝕋ℕ • he/him @dragosrobertn]

If anyone I know or follow on here is at Manchester Tech Festival, don’t be afraid to come say hi. @MancTechFest #MTF2023

[Alex Xu @alexxubyte]

Explaining 9 types of API testing. Next week's topic will be listed at the end.

🔹 Smoke Testing
This is done after API development is complete. Simply validate if the APIs are working and nothing breaks.

🔹 Functional Testing
This creates a test plan based on the functional requirements and compares the results with the expected results.

🔹 Integration Testing
This test combines several API calls to perform end-to-end tests. The intra-service communications and data transmissions are tested.

🔹 Regression Testing
This test ensures that bug fixes or new features shouldn’t break the existing behaviors of APIs.

🔹 Load Testing
This tests applications’ performance by simulating different loads. Then we can calculate the capacity of the application.

🔹 Stress Testing
We deliberately create high loads to the APIs and test if the APIs are able to function normally.

🔹 Security Testing
This tests the APIs against all possible external threats.

🔹 UI Testing
This tests the UI interactions with the APIs to make sure the data can be displayed properly.

🔹 Fuzz Testing
This injects invalid or unexpected input data into the API and tries to crash the API. In this way, it identifies the API vulnerabilities.

Next week, we will talk about:
- Our recommended materials for cracking your next technical interview (YouTube)
- How mobile releases work
- 12 Tips for API security
- What can go wrong with Caching
- Log parsing tips

Subscribe to our weekly newsletter so you won't miss it: https://t.co/uc5M7CdXXC

[Reveal @reveal_app]

It's finally here! We're proud and excited to share with you Reveal's new Insights workspace!

We spent more than a year working on a way we could use Reveal's knowledge of your iOS/iPadOS app to help you both work faster and create better user experiences.

Read on for more…