HackerTrans
トップ新着トレンドコメント過去質問紹介求人

jcmartinezdev

no profile record

投稿

[untitled]

1 ポイント·投稿者 jcmartinezdev·3 か月前·0 コメント

The case for becoming a manager

newsletter.thelongcommit.com
58 ポイント·投稿者 jcmartinezdev·4 か月前·54 コメント

I Think a New Role Is Emerging in Tech

newsletter.thelongcommit.com
3 ポイント·投稿者 jcmartinezdev·4 か月前·0 コメント

I Have 30 Years of Career Left. AI Made Me Rethink All of Them

newsletter.thelongcommit.com
28 ポイント·投稿者 jcmartinezdev·4 か月前·17 コメント

The Quiet Surrender to AI

jcmartinez.dev
6 ポイント·投稿者 jcmartinezdev·5 か月前·0 コメント

コメント

jcmartinezdev
·23 日前·議論
This is really old. JWTs are very safe.
jcmartinezdev
·2 か月前·議論
What's the next stop? it's gotta be auth0
jcmartinezdev
·3 か月前·議論
Even though those pop ups and paywalls are annoying, you shouldn’t be injecting custom CSS and JS like that. It’s just wrong.

And the location… well, if one day they need you, they’ll sure be glad they know your each steps and current location .

It’s not a bug, it’s a feature.
jcmartinezdev
·4 か月前·議論
Rule 6: Never disagree with AI slop
jcmartinezdev
·4 か月前·議論
Mistral is doing some really great stuff lately. Sure, it's hard to compete with OpenAI and Anthropic and their models, but they are taking up some interesting takes and designing their product in unique ways.

I like a lot what they are doing and I'll be watching them a lot more closely. I'd love to work for them btw!
jcmartinezdev
·4 か月前·議論
We are all on the same boat now, whatever it takes us!
jcmartinezdev
·4 か月前·議論
And that’s the thing… it’s good at writing down my ideas in way that I can’t as a non native English speaker.

But it needed the judgement, the experienced and suffered input to know what to help me write
jcmartinezdev
·4 か月前·議論
When that happens, we'll having nothing else to do.
jcmartinezdev
·4 か月前·議論
That's true! that make me feel better lol. The internet is so sensitive to AI slop, it's hard to know what's the right balanced of usage when writing.
jcmartinezdev
·4 か月前·議論
yeah, I wrote it myself, but since I'm not a native English speaker, I do use AI to "fix" and "polish". I think AI made me a worst writer in a way lol.

it's my bad, I should have been more careful at keeping the content how I wrote it, without much of the fine tuning GPT did.
jcmartinezdev
·4 か月前·議論
I worry about that too, but I'm not sure we are close to that yet. Maybe we'll end up working on legacy systems where AI would break more than it would fix, or maybe we would become prompters. Idk!
jcmartinezdev
·5 か月前·議論
Auth0 is constantly releasing new features, including a new major offering now for AI agents. Plus is still very active in the development community, with open source like OpenFGA, frameworks, contributions to standards and so much more.

Not sure where the maintenance mode is coming from...
jcmartinezdev
·5 か月前·議論
I've seen solutions implementing authorization in multiple ways, some still rely on the underlying services that map to the tools, guaranteeing the AT sent to those services is acting on behalf of the user.

Other's do checks at the tool level, systems like openfga can help make that easier by centralizing the authorization policies.
jcmartinezdev
·5 か月前·議論
There are multiple ways, you can use known authorization methods like RBAC, or if you want something more fancy ReBac (tools like openfga, https://openfga.dev).

But there's only so much that you can do with that, if you need to call third party APIs on the user's behalf I'd recommend going with a solution revolving around custom token exchange (https://datatracker.ietf.org/doc/html/rfc8693).

You can check something like Auth0 offers: https://auth0.com/ai

Which would cover things like token exchange for third party APIs, human in the loop, and also authorization methods.
jcmartinezdev
·5 か月前·議論
This is a really solid primer. I appreciate that the author didn't just jump straight to the most complex solution (CDC/Event Sourcing) but actually laid out the progression of strategies.

While "Sequential Dual-Write" is technically flawed, I think it's fair to admit that it's where 90% of projects start (and stay) until the pain becomes real.

That said, the section on the Transactional Outbox is the highlight here. It really is the most pragmatic middle ground for most engineering teams.It's as good as it gets without kafka.

Great read!
jcmartinezdev
·5 か月前·議論
For what it looks, this is something where DCR (https://openid.net/specs/openid-connect-registration-1_0.htm...) could be helpful.

Some auth providers like Auth0 have support for it: https://auth0.com/docs/get-started/applications/dynamic-clie....

There are some caveats and security concerns when using DCR, so you should research more into that. Another option may be CIMD (https://www.ietf.org/archive/id/draft-parecki-oauth-client-i...) though I'm not totally familiar with it.

What you also mentioned, like using proxys, or wildcards, is also widely used, at least for what I've seen.
jcmartinezdev
·5 か月前·議論
I'm hiring for a senior developer content advocate, and Okta/Auth0 has more open positions.

Here's my currently open position: https://www.okta.com/company/careers/marketing/senior-develo...
jcmartinezdev
·6 か月前·議論
In Germany you also have the UG which is like a small GmbH, with 1 eur minimum capital requirement, that is if you like like the 1k (and up to 2k) it cost to set up.
jcmartinezdev
·6 か月前·議論
Some tax consultants are very shady, and some are really arrogant. I'm currently looking for one as we had some disagreements on pricing with my previous one, and many won't even take me due to my volume, or maybe because I ask to speak English, idk...

But sometimes I feel they are doing me a favor by taking my company, rather than me feeling like I'm hiring them as a service.
jcmartinezdev
·6 か月前·議論
Can you recommend a tax consultant that charges 200 EUR/month including preparing the yearly statements?

I’m nearly at 3.5k/year and I have barely 10 invoices a month that I need to process between incoming and outgoing lol