Georges

 engineer & manager at ///@adidas. Tinkering with many technologies on daily basis. I am a Hiker, Traveler, Coder and Coffee & Beer lover 🍺 | 📍España

[Georges @jamousgeorges]

@jamonholmgren My pick: .agents/ → .agents/skills/ → agents/agent-1.md. Product-specific config can stay under .codex/, .claude/, etc. .ai feels too generic to me.

[Georges @jamousgeorges]

@flaviocopes Agree. The chaos is ugly, but it’s the cost of shipping at AI speed. Early ecosystem, zero standards, lots of MVPs. Hopefully we converge on something shared soon — I’d love to see .agents/ become the standard.

[Georges @jamousgeorges]

Getting way too comfortable relying on Codex lately.

Letting go feels weird—but the results keep getting better the more it’s dialed in, with less back-and-forth.

[Georges @jamousgeorges]

@ShresthaPrajeet @steipete This tool uses codex’s binary locally to get that information, it does not communicate to codex by itself. Check the code/website privacy note for more info.

[Georges @jamousgeorges]

@steipete @arafo93 The ilusion of thinking

[Georges @jamousgeorges]

Loved organizing our internal #iOS ecosystem meetup at #adidas HQ in #amsterdam . It was exciting to discover new ideas and learn from everyone. Talks were full of each presenter’s personality and area of passion.

[Eduardo Bocato @dubocato]

Great time at adidas iOS apps ecosystem internal meetup in Amsterdam this week! I presented talks on app architecture, SwiftUI navigation & TCA from @pointfreeco, and domain modeling over three days, along with many others from my colleagues. Kudos to all! #iOS #adidas #amsterdam

[Eduardo Bocato @dubocato]

Great time at adidas iOS apps ecosystem internal meetup in Amsterdam this week! I presented talks on app architecture, SwiftUI navigation & TCA from @pointfreeco, and domain modeling over three days, along with many others from my colleagues. Kudos to all! #iOS #adidas #amsterdam

[Georges @jamousgeorges]

@AdamWhitcroft I really like it 👍, the level of details and work is apparent, congrats. I might also steal some ideas and implement them in my own app ☺️

[Georges @jamousgeorges]

@zebra_dev @timedepositapp yes makes sense, its not that complicated either. 👍

[Georges @jamousgeorges]

@Astrodevil_ 👋 Hi @Astrodevil_ i recently released an app i have been working on for a while. It started it to help me take care of my little german shepherd 🐕 puppy (now he’s 8years old!), and also as a tribute to a family dog we lost tragically at the age of 7.

https://t.co/qsYYtll4OD

[Alex Napier Holland 🦍 @NapierHolland]

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

(More below)

[thameem @th2049]

How many of you knew that you could put apps in the finder toolbar? Just hold the command key and drag it on to the toolbar. Works with files and folders as well! 🤯

[CoderFrankfurt @coderfrankfurt]

Someone has this domain just for that purpose.

[gbae the app developer @daboigbae]

As a programmer - is clean code important?

[Dr Milan Milanović @milan_milanovic]

𝗢𝗪𝗔𝗦𝗣 𝗧𝗼𝗽 𝟭𝟬 𝗔𝗣𝗜 𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆 𝗥𝗶𝘀𝗸𝘀

Here is the list of the top 10 API security risks in 2023.

𝟭. 𝗕𝗿𝗼𝗸𝗲𝗻 𝗢𝗯𝗷𝗲𝗰𝘁 𝗟𝗲𝘃𝗲𝗹 𝗔𝘂𝘁𝗵𝗼𝗿𝗶𝘇𝗮𝘁𝗶𝗼𝗻 - APIs tend to expose endpoints that handle object identifiers, creating a wide attack surface of Object Level Access Control issues.

𝟮. 𝗕𝗿𝗼𝗸𝗲𝗻 𝗔𝘂𝘁𝗵𝗲𝗻𝘁𝗶𝗰𝗮𝘁𝗶𝗼𝗻 - Authentication mechanisms are often implemented incorrectly, allowing attackers to compromise authentication tokens or to exploit implementation flaws to assume other user's identities temporarily or permanently.

𝟯. 𝗕𝗿𝗼𝗸𝗲𝗻 𝗢𝗯𝗷𝗲𝗰𝘁 𝗣𝗿𝗼𝗽𝗲𝗿𝘁𝘆 𝗟𝗲𝘃𝗲𝗹 𝗔𝘂𝘁𝗵𝗼𝗿𝗶𝘇𝗮𝘁𝗶𝗼𝗻 - The lack of or improper authorization validation at the object property level.

𝟰. 𝗨𝗻𝗿𝗲𝘀𝘁𝗿𝗶𝗰𝘁𝗲𝗱 𝗥𝗲𝘀𝗼𝘂𝗿𝗰𝗲 𝗖𝗼𝗻𝘀𝘂𝗺𝗽𝘁𝗶𝗼𝗻 - Satisfying API requests requires resources such as network bandwidth, CPU, memory, and storage.

𝟱. 𝗕𝗿𝗼𝗸𝗲𝗻 𝗙𝘂𝗻𝗰𝘁𝗶𝗼𝗻 𝗟𝗲𝘃𝗲𝗹 𝗔𝘂𝘁𝗵𝗼𝗿𝗶𝘇𝗮𝘁𝗶𝗼𝗻 - Complex access control policies with different hierarchies, groups, and roles, and an unclear separation between administrative and regular functions, tend to lead to authorization flaws.

𝟲. 𝗨𝗻𝗿𝗲𝘀𝘁𝗿𝗶𝗰𝘁𝗲𝗱 𝗔𝗰𝗰𝗲𝘀𝘀 𝘁𝗼 𝗦𝗲𝗻𝘀𝗶𝘁𝗶𝘃𝗲 𝗕𝘂𝘀𝗶𝗻𝗲𝘀𝘀 𝗙𝗹𝗼𝘄𝘀 - APIs vulnerable to this risk expose a business flow - such as posting a comment - without compensating for how the functionality could harm the business if used excessively in an automated manner.

𝟳. 𝗦𝗲𝗿𝘃𝗲𝗿 𝗦𝗶𝗱𝗲 𝗥𝗲𝗾𝘂𝗲𝘀𝘁 𝗙𝗼𝗿𝗴𝗲𝗿𝘆 - Can occur when an API is fetching a remote resource without validating the user-supplied URI.

𝟴. 𝗦𝗲𝗰𝘂𝗿𝗶𝘁𝘆 𝗠𝗶𝘀𝗰𝗼𝗻𝗳𝗶𝗴𝘂𝗿𝗮𝘁𝗶𝗼𝗻 - APIs and the systems supporting them typically contain complex configurations, meant to make the APIs more customizable.

𝟵. 𝗜𝗺𝗽𝗿𝗼𝗽𝗲𝗿 𝗜𝗻𝘃𝗲𝗻𝘁𝗼𝗿𝘆 𝗠𝗮𝗻𝗮𝗴𝗲𝗺𝗲𝗻𝘁 - APIs tend to expose more endpoints than traditional web applications, making proper and updated documentation highly important.

𝟭𝟬. 𝗨𝗻𝘀𝗮𝗳𝗲 𝗖𝗼𝗻𝘀𝘂𝗺𝗽𝘁𝗶𝗼𝗻 𝗼𝗳 𝗔𝗣𝗜𝘀 - Developers tend to trust data received from third-party APIs more than user input, and so tend to adopt weaker security standards.

Check the details in the comments.

_______
If you like my posts, please follow me, @milan_milanovic, and hit the 🔔 on my profile to get a notification for all my new posts.

Grow with me 🚀!

#technology #softwareengineering #programming #techworldwithmilan #api

[Georges @jamousgeorges]

@ios_dev_alb of course

[Georges @jamousgeorges]

@official_JemAl Yes it is fine if you need persistency.
However it costs to access it, so you would also need memory caching for faster access between the services and the disk.

[Robert Scoble @Scobleizer]

Steve Jobs, when he formed his first iPhone team of about a dozen people, told them "you are not allowed to hire anyone who has worked on a phone before."

I didn't really grok that until I saw this.

What "rules" are about to be broken due to AI?

All of them.

A NeRF has infinite camera positions, for instance.

What would Orson do with THAT?

[Dave Anderson @scarletinked]

I found a great trick for fixing cognitive diversity in my decision-making.

As a people manager, one of your key responsibilities is ensuring that you have succession planning firmly in place.

🧵