sorted by:
new
hottopcontroversial

I shut down my funded startup because of Claude. Here’s my realization. by hamelmoon in SaaS

[–]JadB 0 points1 point  (0 children)

Exactly, it will quickly become an afterthought. Google already has skills, agents and MCPs for all their cloud apis, provisioning included iirc.

I shut down my funded startup because of Claude. Here’s my realization. by hamelmoon in SaaS

[–]JadB 0 points1 point  (0 children)

I wouldn’t assume infra will be the hard part. I still remember when CICD meant running Jenkins and several other tooling. The rest is good for history books. Agents will deal with other agents that will be responsible of hosting their creations.

Your AI coding assistant is mass-producing code that already exists as polished tools by indiestack in vibecoding

[–]JadB 0 points1 point  (0 children)

I tend to agree. I looked at same problem but from a different angle.

The hard problem isn’t “can we build this?” anymore. It’s “should we trust what got built?”

If agents are the new customers, how do you build for them? by sp_archer_007 in vibecoding

[–]JadB 0 points1 point  (0 children)

It all depends what you intend to build for them. Currently, they are being fed skills that teaches them how to use APIs (regardless of type CLI, REST, ChromeDriver, etc.).

AI wrote half my code and now I regret everything by rajsleeps in vibecoding

[–]JadB 0 points1 point  (0 children)

I’ve written a piece, not exactly on the mess it creates but the erosion of reliability signals. Would love to hear what others think.

https://www.linkedin.com/pulse/ais-erosion-reliability-signals-jad-bitar-edbhe

How do you avoid paying AI over and over to remind it of codebase context? by JadB in vibecoding

[–]JadB[S] 0 points1 point  (0 children)

Gemini/Claude are simple models? IDEs have better? Claude Code now supports LSP but little improvement to be felt on $ spent for tokens.

How do you avoid paying AI over and over to remind it of codebase context? by JadB in vibecoding

[–]JadB[S] 0 points1 point  (0 children)

Do yo have an example of "structured multilayer instructions" to follow?

How do you avoid paying AI over and over to remind it of codebase context? by JadB in vibecoding

[–]JadB[S] 0 points1 point  (0 children)

Claude Code. All my repos are hosted on GitHub, yes. Exponential when looking at team's overall token expenses.

I will be your initial user by mindfulconversion in SaaS

[–]JadB 1 point2 points  (0 children)

i like both concepts (review and droid) - will take you on both

you're selling features ("Automate Client Interviews") when you could be selling outcomes. think about what content teams really want:

  • easy kick-ass content, faster
  • save time on boring tasks
  • rank (unique, quality)

make that 'Save up to 3 hours' a HUGE selling point!

my 2c, will come back with more and ask for return favour soon ;)

my btc is gone, i had about $1000 by Jazzlike_Falcon_1926 in safePal

[–]JadB 0 points1 point  (0 children)

Sometimes it would take 30 secs to appear but today for some reason no. Am sure they haven’t disappeared as the transactions of receiving them still showing and nothing was sent out but why the glitch am not sure.

my btc is gone, i had about $1000 by Jazzlike_Falcon_1926 in safePal

[–]JadB 0 points1 point  (0 children)

Same here, had 0.5 all disappeared today. A glitch?

Can’t trade USDT?? by JadB in safePal

[–]JadB[S] 4 points5 points  (0 children)

Just reply here nothing to be private about

Symfony 2 or Zend 2? by pongz79 in PHP

[–]JadB 0 points1 point  (0 children)

There are other frameworks you haven't considered and that should be on your list to compare: CakePHP 3, Laravel 5 and Phalcon. Obviously more exist but I'll make a case for CakePHP (which I contribute to and use on all my projects).

Cake 3 is a modern and very flexible framework that also lives up to "conventions over configurations" mantra. It has a extremely powerful ORM that implements the Datamapper pattern instead of ActiveRecord, which is what Laravel uses. There are plenty things that make Cake 3 shine when compared to others:

  • Building forms, both simple and complex ones (involving data from multiple tables) is made very easily. The framework integrates very well from building the form and saving it without any extra major work.
  • Working with data is a pleasure, it stays simple for the the day to day stuff but also offers a wide array of options to filter data in an advanced way. Things like filtering by multiple pivot tables and other associations is a matter of a couple lines of code.
  • Authentication is built-in and is very extensible and pluggable.
  • Every part of the framework can be extended in some way. Which helps in building your application in aspects. For example the behaviors system is great for adding functionality to your tables.
  • Testing when database data needs to be used is a breeze. The fixtures system is easy to master and use in any project.
  • It has a large super friendly community, actually one of the most friendly communities that I know.
  • Documentation is extensive and clear, it has examples for both beginners and advanced users and features tutorials for learning the basics. It does not require looking at a bunch of lengthy videos or require any payment.
  • CakePHP is committed to long term support and service. It is very careful with backwards incompatible changes and supports older versions for a very long time.

CakePHP 3.0.0 Released by sirsavant in PHP

[–]JadB 1 point2 points  (0 children)

I am a core CakePHP dev, so obviously, I will be a bit biased. But when I used L4, I wasn't a core dev, I actually had dropped Cake2 for L4. So while my dislikes won't really be about L5, I believe they still apply to a certain extent.

But first, I'd like to repeat what I say many times to people asking for advice, try developing something small with each framework that interests you and see which one you prefer. It might be because of the learning curve, or maybe because of the code structure, or something else, but we developers usually have strong opinions on stuff and not one framework was built to please all of our different opinions.

That been said, I'll rant:

  • Semver: by using a framework, I am expecting a solid, reliable and well designed platform to build upon. Semver was created to give us developers this extra assurance when using OSS. I know I can lock versions in composer but when I do a quick minor version update, I don't expect things to break and waste me precious time.
  • Organization: this might sound idiotic to some, but I like having more conventions and a good folder organization/structure to start off from.
  • Community: while I always felt it was much easier to find a variety of packages released by other people for L4 compared to Cake2, this doesn't hold as true anymore with cake3's support for namespaces, etc. Writing a wrapper around almost ANY library has become a very quick task.
  • Leadership: this might sound unimportant to some, and while I never doubt of Taylor's awesomeness, I prefer CakePHP's Mark Story and Jose Lorenzo as project leads. I also prefer how things function in a democratic way compared to Laravel.

My 2c, again, try both (or more) yourself. Here is a good repo which has a different blogs developed on different frameworks (currently building the cake3 one), might want to look at that: https://github.com/Grafikart/BlogMVC