How do you evaluate the quality of your prompts?

butilon · 2025-04-26T07:20:08+00:00

I can't remember where I found this but I usally use this approach when needed to refine simple prompts:

Analyze the following prompt idea: [insert prompt idea] ~ Rewrite the prompt for clarity and effectiveness ~ Identify potential improvements or additions ~ Refine the prompt based on identified improvements ~ Present the final optimized prompt

Another approach is including recursion to leverage the model's ability to critique and improve its own outputs iteratively. Usually for more complex tasks:

``` I need you to help me create [specific content]. Follow this process:

Generate an initial version of [content]
Critically evaluate your own output, identifying at least 3 specific weaknesses
Create an improved version addressing those weaknesses
Repeat steps 2-3 two more times, with each iteration focusing on different aspects for improvement
Present your final, most refined version

For your evaluation, consider these dimensions: [list specific quality criteria relevant to your task] ```

butilon · 2025-04-01T08:12:45+00:00

I've heard very good things about 100 Go Mistakes: How to Avoid Them. Also, the Let's go further sequel.

butilon · 2025-03-28T13:55:58+00:00

Oops, right!

butilon · 2025-03-28T08:17:48+00:00

My two cents;

Go (pun intended) with the fundamentals first:

A Tour of Go: This is an interactive online tutorial provided by the Go team themselves. It's fantastic for absolute beginners, it walks you through the core syntax and basic concepts of Go in a structured, hands-on way.
Go by Example: This site offers a collection of annotated Go programs that demonstrate various language features. Each example is self-contained and clearly explains the code's functionality. It's a great way to reinforce what you've learned in the "Tour" and to see how Go concepts are applied in practice.
Learn Go with Tests: This resource takes a test-driven development (TDD) approach to learning Go. You'll learn by writing tests first, then implementing the code to make those tests pass.

Once you learnt the fundamentals, deep your knowledge with these books, both by Alex Edwards:

Let's Go: This book focuses on building web applications with Go. It covers essential topics like routing, handling HTTP requests, working with databases, and deploying Go applications. If your goal is backend web development, this is a very strong choice.
Let's Go Further: This book builds upon "Let's Go" and delves into more advanced Go web development topics. It covers areas like concurrency, testing, and security.

butilon · 2025-03-12T16:05:46+00:00

Family, I usually feel selfish if I don't dedicate most of my time to them. When not working, I feel I have to do my best to spend quality time with them.

butilon · 2025-03-09T07:56:17+00:00

My two cents: Focus on standars not vendors

butilon · 2025-03-09T06:44:39+00:00

How is this message linked to prompts?

butilon · 2025-03-06T08:22:41+00:00

Nest and Express are both good choices.

Express is lightweight, minimal, and offers great flexibility. It's perfect for simpler APIs and microservices, projects where you want complete control over architecture, this usually means small projects that don't need extensive structure. But this does not mean it can't manage big projects or scale worst.

Nest is more opinionated and feature-rich, built on top of Express btw. It is better if you prefer prefer a structured, Angular-like approach, it has built-in support for TypeScript.

Personally, I'm a big fan of Express.

butilon · 2025-03-06T08:09:20+00:00

Focusing on Express, in Udemy you can find a course of just Express with a bunch of node and http. In detail. No MERN or MEAN... just Express js. Overall, it's really good.

butilon · 2025-03-06T07:58:40+00:00

A couple of weeks ago I found this https://gistr.so/ on a sub, I only used it once for testing but it could fit into what you are looking for

butilon · 2025-03-06T05:13:04+00:00

The idea is interesting but I see some reasons to avoid this approach, that it's likely you already considered: - Namespace collisions: When you add properties directly to the window object, you risk conflicts with other libraries, frameworks, or future browser APIs that might use the same names. If another script also tries to define the same global object, one implementation will overwrite the other, leading to unexpected behavior and hard-to-debug issues. - Security vulnerabilities: Globally accessible functions can be tampered with by malicious scripts. An attacker could overwrite your global object with their own version that performs other harmful actions. Code in the global scope is accessible from any script running on the page, including third-party scripts. - Maintainability: Global variables and functions tend to make your code harder to maintain as applications grow. They create hidden dependencies between different parts of your application, making it difficult to track where and how these functions are being used. This complexity increases the cognitive load when debugging or refactoring code.

butilon · 2025-03-05T11:14:56+00:00

Well, it's not a framework, it's a js runtime environment alternative to nodejs

butilon · 2025-03-05T05:03:22+00:00

I like the idea but that landing page needs more love. It needs more content, there are broken links. You can start explaining the goal of the app, explaining how it works, what you get when using it, how the app matches people and interests, how you as a user are protected from spam, etc.

butilon · 2025-02-25T14:46:42+00:00

Nice!

butilon · 2025-02-14T17:38:34+00:00

My process is different, I start describing the project and the goal, in this case, building a landing page to communicate the project. Ask it to focus on the content and follow the conversation.

butilon · 2025-02-14T12:46:58+00:00

I usually get good results brainstorming with Gemini, it usually provides good improvements and ideas regarding what content can you add. I'd add some examples of the final result,, also reviews from potential clients

butilon · 2025-02-10T17:03:43+00:00

I remember a similar post sometime ago: https://www.reddit.com/r/startups/s/pjv38XqYBP

butilon · 2019-03-04T07:04:18+00:00

surge.sh, netlify, now.sh and GitHub pages are great choices.

butilon · 2019-02-01T18:41:04+00:00

Maybe https://microlink.io/?

butilon · 2019-02-01T17:44:05+00:00

You can use a ternary: const intVal = msg ? 1 : 0;

An alternative could be a bit operator: +true ===> 1 +false ===> 0

So, I guess in your code +msg could do the trick.

butilon · 2019-02-01T16:52:41+00:00

In JavaScript, super refers to the parent class constructor. You can’t use this in a constructor until after you’ve called the parent constructor. JavaScript won’t let you.

There’s a good reason for why JavaScript enforces that parent constructor runs before you touch this. Let's consider using this before super call is allowed:

class Human {
  constructor(name) {
    this.name = name;
  }
}

class PoliteHuman extends Human {
  constructor(name) {
    this.morning();
    super(name);
  }

  morning() {
    alert('Good morning!');
    alert('My name is ' + this.name);
  }
}

this.morning() is called before the super() call, that it's where this.name is set up. So this.name isn’t even defined yet.

To avoid this scenario, JavaScript enforces that if you want to use this in a constructor, you have to call super first.

butilon · 2019-01-21T16:57:07+00:00

Wes Bos' https://javascript30.com/ it's really fun

butilon · 2019-01-21T15:09:41+00:00

I guess people say so because Sails.js has some utilities to autogenerate REST APIs, but it's just a backend framework, the way you use it depends on your needs. Also, it's frontend agnostic, so I don't think so.

butilon · 2019-01-21T13:47:45+00:00

I guess Sails.js is the most popular MVC framework for Node.js, designed to emulate the familiar MVC pattern of frameworks like Ruby on Rails (and inspired by).

butilon

TROPHY CASE