Ibo Dc

-- Founded @doardsofficial --

[Ibo Dc @ibo_dc]

After facing exactly the same problem ourselves, we at Doards decided to do something about it.

We built our own completely FREE and public API, making publicly available data easily accessible to everyone.

From countries, currencies, and car manufacturers to complex aviation and aerospace data — almost 200 tables with millions of records.

And especially with AI, this makes a huge difference. Instead of searching websites, downloading files, or guessing information, AI agents can access structured data directly through APIs, saving time, tokens, and costs.

No fees. No approval process. Just free access for everyone.

🌐 API: https://t.co/KC15we209u

💻 Open-source GitHub: https://t.co/VVW7B6LQfl

We need more open APIs, not more barriers to innovation.

[Ibo Dc @ibo_dc]

The problem with German software startups isn’t “just” bureaucracy, taxes, etc. etc. Let me give you another major problem and example: access to open data and APIs.

ALL successful US startups have a developer page where you can register and use their APIs. In 90% of cases, free of charge, so you can build your own software on top of them or simply connect your existing software with their services.

And they benefit from this too. If their customers can easily connect their tools with your ERP, CRM, or any other software, their own product becomes more useful and attractive as well.

But no, here in Germany we of course have to make that paid AND DEFINITELY NOT PUBLIC.

DATEV wants several thousand euros in fees because they want to “review” MY WORK, THE CODE I WRITE AND THE TIME I SPEND ON IT, decide whether it’s okay, and only then give me access to the API.

And if it’s not okay, it’s not even your problem anyway. My fckng software simply won’t work and you’ll get, at most, an error message.

[Ibo Dc @ibo_dc]

@devbenbo Hi Ben, nice to hear that. Juat let me know anytime if you need help or something fails

[Ibo Dc @ibo_dc]

Just wanna publish one of my public projects for the developer community.

Built this over the weekend because I had this problem myself and I’m pretty sure a lot of developers still using VS Code have it too.

Most developers are using Claude and Codex now. The problem starts when you have one huge chat, all the context is there, everything is working perfectly, and then...

Your tokens are gone.

Now you wanna continue in Codex instead of Claude, or the other way around, but you can’t just move the whole conversation with all the context and continue working.

So I built exactly that.

You can take your current chat, create a handoff, move it to the other agent and just continue from where you stopped.

Claude to Codex.

Codex to Claude.

No starting from zero again. No manually explaining your whole codebase, what you changed, what you tried and what still needs to be done.

I also added it as a VS Code plugin, so you can use it directly while coding.

It’s public on GitHub.

Just check it out, run it and tell me what you think.
https://t.co/zijua56gCd

Attached a small video showing how it works 👇

[Ibo Dc @ibo_dc]

@pdaether 🔫🔫🔫

[Ibo Dc @ibo_dc]

The problem with German software startups isn’t “just” bureaucracy, taxes, etc. etc. Let me give you another major problem and example: access to open data and APIs.

ALL successful US startups have a developer page where you can register and use their APIs. In 90% of cases, free of charge, so you can build your own software on top of them or simply connect your existing software with their services.

And they benefit from this too. If their customers can easily connect their tools with your ERP, CRM, or any other software, their own product becomes more useful and attractive as well.

But no, here in Germany we of course have to make that paid AND DEFINITELY NOT PUBLIC.

DATEV wants several thousand euros in fees because they want to “review” MY WORK, THE CODE I WRITE AND THE TIME I SPEND ON IT, decide whether it’s okay, and only then give me access to the API.

And if it’s not okay, it’s not even your problem anyway. My fckng software simply won’t work and you’ll get, at most, an error message.

[Ibo Dc @ibo_dc]

(Yeah, Google and Meta are examples of companies that may ask you to submit a video so they can check whether everything works correctly. But that’s it: a video, a quick review, and free of charge.)

[Ibo Dc @ibo_dc]

I will publish more open source Projects... "from Developers to Developers"

[Ibo Dc @ibo_dc]

@danellisona Linkedin itself

[Ibo Dc @ibo_dc]

@ZeynepAryay Sooooo true. Going to Sales from Coding .. 🔫

[zeynep @ZeynepAryay]

Nobody talks about how hard it is to spend your whole life writing code and then become the person who has to sell.

I never thought sales would be part of my job. For the first three months I was bad at it, and I lost deals I should have won.

The mistake I kept repeating was treating a sales call like a demo. I would show what we built, walk through the parts I was proud of, and wait for the prospect to be impressed. They usually weren't, because I was answering questions they hadn't asked yet.

Four things that helped:

Give yourself permission to be bad at it for a while. You spent years getting good at engineering, and nobody expected you to be good at that on day one either. Sales works the same way, except the feedback loop is slower and more expensive.

Book demo calls with other companies, including tools you have no intention of buying, and pay attention to how the person on the other side qualifies you. You'll notice they ask far more questions than they answer, and that almost all of those questions come before any product shows up on the screen.

Rehearse before it counts. Mock calls with a colleague, or even saying your pitch out loud alone, will expose the parts of your story that don't hold together. Finding those gaps in practice is much cheaper than finding them in front of a prospect.

Listen longer than feels comfortable. Prospects describe their problem in their own words, and those words are almost always better than the ones you wrote yourself. I now reuse the exact phrasing customers give me when I write outreach.

Engineering taught me to build the answer before anyone asks for it. Sales asks you to do the opposite, and unlearning that habit took me longer than learning anything new.

[Ibo Dc @ibo_dc]

@gorkemcetin @barisakin Şöyle böyle bir sorunum var, acaba package update ile mi geldi, aynı versionda yaşayan var mı diye soruyorsun…

Son kalan kale Stack Overflow. Ayda yılda bir kullanan bilir.

[Ibo Dc @ibo_dc]

Has a point... some things are just much, much easier to do manually.

[kapilansh @kapilansh_twt]

VIBECODING IS HARDER THAN MANUAL CODING
VIBECODING IS HARDER THAN MANUAL CODING
VIBECODING IS HARDER THAN MANUAL CODING
VIBECODING IS HARDER THAN MANUAL CODING
VIBECODING IS HARDER THAN MANUAL CODING
VIBECODING IS HARDER THAN MANUAL CODING

agree ?

[Ibo Dc @ibo_dc]

Butttttt I never find the time to post or write anything, I’ll try to change that....

[Ibo Dc @ibo_dc]

I think building in public will create a lot of the next generation of billionaires, or at least very successful entrepreneurs.

Over the next few days, I’m going to share my next big thing.

[Ibo Dc @ibo_dc]

@hannah24_app Network...

[Ibo Dc @ibo_dc]

@raulgcc1 @peterthiel Yeah, good point. But thanks to LLMs, human judgment might also be getting worse.

[Ibo Dc @ibo_dc]

I wanna ask @peterthiel if he really still thinks AI will take over humans not before the 22nd century... like he suggested in Zero to One.

[Ibo Dc @ibo_dc]

@ycombinator @atrlergn

[Ibo Dc @ibo_dc]

Applied to @ycombinator again.

This time with something realllyyy different—and genuinely exciting. Let’s see what happens.

Once we get accepted, I’ll publish the video we made with @atrlergn 👀

[Ibo Dc @ibo_dc]

@egekodluyor @peterthiel Icelim canimm ☕️☕️ kahve + kod sessioni olmasin ama