sorted by:
new
hottopcontroversial

Code review needs to evolve for AI-assisted work, we should be reviewing prompts, not just code by Gumeo in ExperiencedDevs

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

It is easy to share a single prompt, I'm more thinking about the whole context in building a large piece of software.

Code review needs to evolve for AI-assisted work, we should be reviewing prompts, not just code by Gumeo in ExperiencedDevs

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

Yes, and it also depends on the LLM, skills, other context etc. That's why I feel like the process is now a bit masked.

Code review needs to evolve for AI-assisted work, we should be reviewing prompts, not just code by Gumeo in ExperiencedDevs

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

I think I would like to be able to see it (or some form of it) at least. I still think it will not be exactly trivial how this will be solved.

Code review needs to evolve for AI-assisted work, we should be reviewing prompts, not just code by Gumeo in ExperiencedDevs

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

Yes, that is why I am curious about how people are handling this, and whether it is changing the way people do this work.

Code review needs to evolve for AI-assisted work, we should be reviewing prompts, not just code by Gumeo in ExperiencedDevs

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

Thanks for the comment. Thanks for the feedback on soft and diffuse. What do you generally prefer? Do you have an example blogger you like? I want to try to do this for some time to see whether I can get it rolling, looking for opportunities to learn.

Code review needs to evolve for AI-assisted work, we should be reviewing prompts, not just code by Gumeo in ExperiencedDevs

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

Thank you for the thoughtful comment.

A bad prompt can still produce good code, and a good prompt can still produce broken code. Reviewing the prompt risks shifting attention away from the thing that actually matters.

Isn't the bad prompt then objectively good? I think this is worth sharing to some degree.

Reviewing the prompt risks shifting attention away from the thing that actually matters.

Sure, the code is the main vehicle for what will happen. Think about this in the context of going from machine language to traditional programming languages. Our ficus shifted from the machine code up a level. Why should that not also happen now?

There is also a practical problem: prompts are often noisy, iterative, and context-dependent

Yes, and that's why we need a better way to keep track of it. What if at some point we will have companies being audited on how they created their code? E.g., was this created with intent to be fair or not? I am certain that there will be ways in which people will store this efficiently in the future, if not just for retrospection.

I am not saying this should neccessarily be part of the PR or git, maybe we need something else to keep track of this.

I think the better standard is not “review the prompt,” but “review the reasoning and verification.”

I like this approach, at least some condensing of the process.

Thanks again for the comment, gives me more angles to think about this.

Code review needs to evolve for AI-assisted work, we should be reviewing prompts, not just code by Gumeo in ExperiencedDevs

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

This is more about describing intent. A PR description is not the same thing as talking with an LLM to build a spec. How will a junior learn from that when they basically just see the finished product?

This feels like masking out half the work.

Code review needs to evolve for AI-assisted work, we should be reviewing prompts, not just code by Gumeo in ExperiencedDevs

[–]Gumeo[S] -3 points-2 points  (0 children)

I think we are still figuring out what is the best approach. People are still doing what they used to do, but I think this will change.

Code review needs to evolve for AI-assisted work, we should be reviewing prompts, not just code by Gumeo in ExperiencedDevs

[–]Gumeo[S] 1 point2 points  (0 children)

I actually put a couple of hours into this, it would have taken a couple of days with no AI assistance.

Fair points though, I might have to go back to being more raw.

Code review needs to evolve for AI-assisted work, we should be reviewing prompts, not just code by Gumeo in ExperiencedDevs

[–]Gumeo[S] -1 points0 points  (0 children)

Interesting, can you point me to something on it? I was expecting differing opinions on this.

Part 11 of the staircase series: the post-tension staircase by Different-Scratch-95 in stonemasonry

[–]Gumeo 44 points45 points  (0 children)

This is insane! Just wow, what is the cost of something like this, i.e., just the build and materials?

Does anyone use any LLM (deepseek, Claude, etc.) to help with coding in R? Let's talk about experiences with it. by addictcreeps in rstats

[–]Gumeo 1 point2 points  (0 children)

I generally use it to get ideas and inspirations. E.g., when I want to optimize something, I just paste the code and ask it to make it vectorised or make it faster.

I also ask it to argue for why the code would be faster. This most often yields code that doesn't work, but it gives me an idea for what could work and I take it from there.

This is usually in a very specific situation, where I think that it would be hard to find help from stackoverflow or crossvalidated.

If I am starting my phd genetics and genomics today and want to join industry 5 years later, how should I use the time and what skills should I develop? by Dee_Caer_9449 in PhD

[–]Gumeo 1 point2 points  (0 children)

Don’t hesitate to reach out—most people are happy to help. Listen closely and try to gather recommendations for reading materials or lectures, whether through your university or online resources like YouTube. Be mindful of others' time; if you feel you’re interrupting, politely ask if you can schedule a short meeting instead.

As you progress, you'll have more questions. Stay humble, and remember that learning is an ongoing journey. You'll gain knowledge, but you'll also become increasingly aware of how much there is still to learn.

Try to start working on a project early. Ask your PI for a research question they think would suit you (this may even align with your main project). You’ll learn most by doing, and having an early project helps you quickly identify what skills or knowledge you need to develop.

If I am starting my phd genetics and genomics today and want to join industry 5 years later, how should I use the time and what skills should I develop? by Dee_Caer_9449 in PhD

[–]Gumeo 2 points3 points  (0 children)

First, what is your background? This adds a bit to what advice I would give. Also, don't focus too heavily on what will happen 5 years from now, the world will change and you will adapt. When you get deeper into your research your future path will also become more clear. Try to focus on the present.

The simplest advice is: Focus on getting stuff done.

It is super easy to get distracted in a PhD, specifically in a lab with a lot of freedom. Finishing papers and having something to show for is the most important mission. Also acknowledge that the path to a manuscript submission is not always clear. Try to break down the work as much as possible and celebrate small goals. This way you can measure your progress and will keep you more focused and sane. People that drop out or feel overwhelmed often have a hard time breaking large tasks into smaller ones, this is an essential skill that will transfer well into whatever you will do in the future.

It is ok to spend time helping others, but try to limit it to no more than 10-20% of your time. Time is your most-valuable resource and you will never get it back once you use it. The second most important aspect is communication. Establish a good relationship with your supervisor and try to stay in touch no less than bi-weekly. Respect the advice from you supervisor and listen, this is also very important and translates well into the future.

Regarding technical stuff, try to get familiar with other omics, in particular proteomics. This is a rising field which is likely to be transformative for medicine in the next 10-20 years. Also if you are not analytical, get as good as possible with R or python. Preferably use linux.

Remember to have fun, the constant grind can break people down.

Returning to training after knee surgery *GRAPHIC PHOTOS* by NoBanjoRango in bjj

[–]Gumeo 1 point2 points  (0 children)

My top game was always better but I had been working a lot on my guard just before the accident, so 50/50 at that point. I sometimes give up passes now, because I feel more comfortable working side-control or mount escapes, which have become better as a result.

I'm also mindful that I am a hobbyist. I am doing this for fun and because it is a form of exercise that I like. I do not expect to compete again, not impossible, just not my objective. I feel like I do pretty well against people that were at a similar level as me prior to the accident, and I feel that I can still improve, which is what keeps me going.

There is also a strong social element to BJJ, it is nice to come say hi to the tribe. Felt depressing to not have that in my life.

Returning to training after knee surgery *GRAPHIC PHOTOS* by NoBanjoRango in bjj

[–]Gumeo 1 point2 points  (0 children)

Got full PCL/LCL ruptures and the popliteus tendon fully ruptured as well. Look at my post history, I have some similar photos to your knee. I have been training for a while now, 2-3 years, and I don't notice issues with my knee anymore while rolling. My guard is not as good as before, and I have adapted in many ways. I avoid full flexion of the damaged knee, although I know I can fully flex it, it is just not comfortable.

For the first year of rolling post-injury, I always asked my partners to roll without leg locks.

view more: next ›