#gh300
FRPITA: 6 principles:
Fairness, Reliability, Privacy, Inclusiveness, Transparency, Accountability. AI must treat people fairly, perform safely, respect privacy, empower all, be understandable, and remain accountable to humans.
Seniority isn’t about how much you know of a programming language, or even the business.
It’s about soft skills: Stay curious. Be motivated. Ask the right questions and go find the answers. Take ownership. Deliver, document, get feedback, and seek the value you created.
Then, take ownership: Did the change go live? Are users engaging with it? Get feedback. This not only improves your work, it builds your case for promotions or resume: "I updated the text in Project ABC, making info clearer and removing an extra step for users."
That’s impact.
Just received this gift from my company.
I can remember the first `if` statement I wrote back in 2008. It was in C, with just one `printf` inside. Now, my son is receiving this... It feels like a harvest for me, from the seeds of those lines of code planted.
Itorah instantly reminded me of Legend of Mana - feathers on the head, vivid colors, and dreamy ambiance. Hand-drawn art, amazing soundtrack by https://t.co/h4IYDJYEVF. This is a reminder that we can earn by drawing, creating music, or programming games. Chase your dreams.
I’ve always been fascinated by maps and GPS tech. Check this post about how @HyperARCo solve one of tech’s toughest problems: *accurate indoor navigation*.
A perfect example of perseverance, innovation, and building *with* users.
Hyper has developed the best indoor location technology in the world: 1m-accurate indoor GPS.
But this is an enterprise game. To scale to a billion people, we’re actively exploring selling our tech to a larger org.
Everything I’ve learnt building indoor location over 7 years 👇
Current setup:
Zone 300 headset: physical mute option (no more need to click mute on screen).
Anker C200 webcam: really good to control harsh sunlight, and I don't look like Gandalf returning as The White anymore.
Keychron keyboard: makes me want to spend hours on MonkeyType.
2025 developers shouldn’t just be solitary coders listening to 90s albums. You can be that, but also collaborative and team player. Strengthen your communication skills, understand the business, share your logic, and question generic steps or unclear blocks on system diagrams.
Work on understanding the bigger picture of software architecture by asking critical questions like: What are the API call limits? What are the token expiration dates and retry policies? Where are these third-party APIs running, and how could they impact performance?