jorgeleo

jorgeleo

mese scorsodiscuss

curios minds... why to do that port?

jorgeleo

mese scorsodiscuss

i can sell you my MBP, but no refunds if it doesn't work

hahaha

jorgeleo

mese scorsodiscuss

and redo the thermal paste

jorgeleo

mese scorsodiscuss

I have personally replaced the battery a couple of times already... but a good clean up is a good idea

jorgeleo

mese scorsodiscuss

i decided to do an experiment and try to run an LLM in my old 2013 MBP. i7, 16 gb mem, 1 tb hd.

Installed Linux mint Xfce Edition for lightness, installed ollama, start to test different models. Gemma4 e4b runs perfectly fine, exposed it to the network, connected to it with my current notebook and use vs code codex to start to run inference.

For about 30 minutes of bliss, this setup work at a reasonable speed... then the MBP shut it self down. It was so hot that it trigger the safety mechanism, the fans sounded like the laptop was about to take off.

I though on leaving it on inside the fridge, but then the WIFI wouldn't reach.

On the other hand, my wife saw all this and offer to buy me an M5... the experiment didn't work as intended, but it did work.

jorgeleo

2 mesi fadiscuss

I was all for trying it until I saw this in the License Agreement:

"4.1. Zed's Use of Customer Data Customer hereby grants Zed a non-exclusive, worldwide, royalty-free, fully paid-up, non-sublicensable (except to service providers and Customer’s designees), non-transferable (except as set forth in Section 15.1) right to use, copy, store, disclose, transmit, transfer, display, modify, create derivative works from, collect, access, store, host, or otherwise process (“Process”) any materials that Customer inputs into or otherwise makes available to the Service (including prompts and other written content) (collectively, “Customer Data”) solely: (a) to perform its obligations set forth in the Terms, including its Support obligations as applicable; (b) to derive and generate Telemetry (see Section 4.4); and (c) as necessary to comply with applicable Laws. Except as required by applicable Laws, Zed will not provide Customer Data to any person or entity other than Customer’s designees (including pursuant to Section 7) or service providers."

Sorry, no I don't agree to make my source code and the product I am working to give you "non-exclusive, worldwide, royalty-free, fully paid-up, non-sublicensable (except to service providers and Customer’s designees), non-transferable (except as set forth in Section 15.1) right to use, copy, store, disclose, transmit, transfer, display, modify, create derivative works from, collect, access, store, host, or otherwise process (“Process”) any materials that Customer inputs into or otherwise makes available to the Service (including prompts and other written content)"

jorgeleo

6 mesi fadiscuss

I did the same experiment as you, and this is what I learned:

https://www.linkedin.com/pulse/concrete-vibe-coding-jorge-va...

The bottom line is this:

* The developer stop been a developer, and becomes a product designer with high technical skills.

  * This is a different set of skills than than a developer or a product owner currently have. It is a mix of both, and the expectations of how agentic development works need to be adjusted.

* Agents will behave like junior developers, they can type very fast, and produce something that has a high probability to work. They priority will be to make it work, not maintainability, scalability, etc. Agents can achieve that if you detail how to produce it.

  * The working with an agent feels more like mentoring the AI than ask and receive.

* When I start to work on a product that will be vibe coded, I need to have clear in my head all the user stories, code architecture, the whole system, then I can start to tell the agent what to build, and correct and annotate in the md files the code quality decisions so it remembers them.

* Use TDD, ask the agent to create the tests, and then code to the test. Don't correct the bugs, make the agent correct them and explain why that is a bug, specially with code design decisions. Store those in AGENTS.md file at the root of the project.

There are more things that can be done to guide the agent, but I need to have clear in an articulable way the direction of the coding. On the other side, I don't worry about implementation details like how to use libraries and APIs that I am not familiar with, the agent just writes and I test.

Currently I am working on a product and I can tell you, working no more than 10 hours a week (2 hours here, 3 there, leave the agent working while I am having dinner with family) I am progressing at I would say 5 to 10 times faster than without it. So, yeah it works, but I had to adjust how I do my job.

jorgeleo

6 mesi fadiscuss

https://www.linkedin.com/posts/jorgevaras_i-cave-in-and-i-tr...

https://apps.apple.com/us/app/nosync-dj/id6752585119

jorgeleo

4 anni fadiscuss

<sarcasm> I like your suggestions... I would add that they are more effective if you keep a background noise with whips cracking sounds and random screams </sarcasm>

Submissions

[untitled]

comments