Wilson Silva

Today I learned: 26 May 2024

2024-05-26T16:45:00.000Z

TL;DR

Using Unify neural router to optimize LLM apps’ speed, latency and cost
Configuring Charles Web Debugging Proxy to inspect HTTPS/SSL traffic
Leveraging truststore to mitigate self-signed certificate errors in Python

Introduction

Unify is a neural router for LLM endpoints. It automatically selects and routes prompts to the best LLM endpoint to get the best output while optimizing for speed, latency, and cost to supercharge LLM applications.

It provides a Python SDK, but not a Ruby one. Integrating it into the project was an opportunity to practice Python. But this process was not smooth.

Unify UI

Using Unify neural router to optimize LLM apps’ speed, latency and cost

I followed their Making Your First Request tutorial to learn how to use the platform. These were the steps:

Sign up on the Unify website
Copy the default API key from the Unify console
Add the API key to an .env file
Create a Python script with code to initialize the Unify client and generate a response

from unify import Unify, list_models, list_providers
from dotenv import load_dotenv

load_dotenv()

unify = Unify("mistral-7b-instruct-v0.2@fireworks-ai")

response = unify.generate("Does discipline equal freedom?")

I ran the Python script but didn’t see any output or errors. I wasn’t sure if the API was responding correctly.

Configuring Charles Web Debugging Proxy to inspect HTTPS/SSL traffic

Then I launched Charles Web Debugging Proxy to debug the Unify API requests. This tool lets developers inspect HTTP and HTTPS traffic between a client and server.

I enabled the macOS proxy in Charles (Proxy > macOS Proxy) and re-ran the Python script. However, the request was encrypted with SSL.

SSL encrypted Unify request in Charles

Charles has SSL debugging, allowing decryption of encrypted data to review/troubleshoot the transmitted content. So I configured it:

Add api.unify.ai:443 to the SSL proxy settings Proxy > SSL Proxying Settings...
Install the Charles root certificate: Help > SSL Proxying > Install Charles Root Certificate
Trust the certificate in Keychain Access
Enable SSL Proxying: Proxy > Start SSL Proxying

I had SSL proxying set up, but I still couldn’t see the traffic. Running the Python script now threw an SSL certificate verification error:

[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed:
self-signed certificate in certificate chain (_ssl.c:1000)

Leveraging `truststore` to mitigate self-signed certificate errors in Python

To resolve the self-signed certificate error, I tried many approaches and all led to frustration. Here’s what worked:

First, I installed the truststore package:

pip install truststore

Then, at the top of my Python script, I added:

import truststore
truststore.inject_into_ssl()

After this, I could see the decrypted request in Charles:

Decrypted Unify request in Charles

But why didn’t I see them in the terminal? I forgot to print the response 😂:

from unify import Unify, list_models, list_providers
from dotenv import load_dotenv

load_dotenv()

unify = Unify("mistral-7b-instruct-v0.2@fireworks-ai")

response = unify.generate("Does discipline equal freedom?")

print(response) # <- Catalyst for learning

Conclusion

Who knew forgetting a print statement could be so educational? 😅 Turns out, tiny mistakes can lead to big learnings, like mastering debugging tools and sharing knowledge through blog posts.

Mistral Ruby gem

2024-05-05T15:20:00.000Z

Why I ported Mistral’s client to Ruby

Python is everywhere

I am taking several AI courses to become proficient in AI development techniques like Retrieval Augmented Generation (RAG), DSPy, and agentic workflows. Most AI libraries, courses, and tutorials use Python as the primary language.

I finished a course recently called Getting Started With Mistral. It taught me effective prompting techniques, function calling, JSON mode, and RAG.

To reinforce my learning, I began transcribing the course. I wrote all code samples in the same language they were taught: Python.

What if developers could learn AI using Python and then easily apply their knowledge to their language of choice?

For this to happen in the Ruby ecosystem, we need libraries that match those in Python, with similar features and APIs. That’s why I created a Mistral gem that closely mirrors the official Python client. It was also a great exercise to practice Python.

Take a look at the code samples below to see how easy it is to translate between the two libraries thanks to their similar APIs.

client = MistralClient(api_key=os.environ["MISTRAL_API_KEY"])

response = client.chat_stream(
  model="mistral-small",
  messages=[ChatMessage(role="user", content="Hi")],
)

for chunk in response:
  print(chunk.choices[0].delta.content)

client = Mistral::Client.new(api_key: ENV["MISTRAL_API_KEY"])

response = client.chat_stream(
  model: "mistral-small",
  messages: [Mistral::ChatMessage.new(role: "user", content: "Hi")]
)

for chunk in response do
  print(chunk.choices[0].delta.content)
end

Other gems

When this was written, only two mistral gems existed: mistral_rb and mistral-ai. Here’s how they compare to each other and my gem.

Feature	`mistral-ai`	`mistral_rb`	`mistral`
Completion without streaming	✅	✅	✅
Completion with streaming	✅	✅	✅
Embeddings	✅	✅	✅
Response formats	❌	❌	✅
List models	✅	✅	✅
Function calling	❌	❌	✅
Type safety	❌	❌	✅
Familiar interface	❌	❌	✅
Automatic retries	❌	❌	✅
Configurable timeouts	✅	❌	✅
Code examples	✅	❌	✅
Runtime dependencies	3	11	2

Key takeaways

Python’s built-in dependency management is brittle. But tools like Poetry offer a more robust solution, similar to Bundler in the Ruby ecosystem.
Gained experience with Pydantic for data validation and pytest for testing in Python
Experimented with minitest as a lightweight alternative to RSpec for testing Ruby code
Deepened my understanding of implementing enumerators effectively in Ruby
Compared to Ruby, Python is ugly 😂

Nostr 0.7.0 - Logging

2024-04-13T13:22:00.000Z

I’m excited to announce the release of version 0.7.0 of the nostr gem, which introduces logging and debugging capabilities to help you monitor and troubleshoot your Nostr client’s interactions with relays.

As an open-source maintainer, I appreciate community engagement. On March 13th, a developer asked for my help to debug an issue with integrating the nostr gem into his application:

Hello Wilson,

I’m Matej Lukášik a RoR developer. Recently I became interested in nostr and found your client. It looks pretty neat and I really appreciate the care you took around documentation and examples.

I would like to help. However, I can’t make it work :-D This are of websockets and event machine are quite new to me and I don’t even know how to debug things properly.

Would you ever have some time to show me around and make it work on my computer so that I can tinker with it later? I would pay you your normal hourly rate if you like.

What do you think? Would you find time to give me a paid introduction to the gem for an hour or so?

I was happy to assist for free. We jumped on a call a few hours later.

While debugging, I realized that the nostr gem needed default logging to provide developers with visibility into their application’s relay interactions. This realization led to prioritizing logging in this release.

I also realized Matej’s code was immediately exiting, potentially before the client could handle all asynchronous operations.

You see, the Nostr client relies on EventMachine, which uses a reactor pattern. For the client to process all the events and messages properly, the main thread needs to be kept alive while the EventMachine reactor runs in the background. By adding gets, we pause the main thread, waiting for user input, and giving the background thread the time it needs to do its job.

This small addition to the example code ensures that the client can connect to relays, send messages, and receive responses as expected. It’s a tiny but important detail, especially for newcomers who might be wondering why their client disconnects unexpectedly.

To make sure developers have a smooth experience with the nostr gem, I’ve updated the README with this helpful tidbit.

Built-in Logging Functionality

The Nostr::Client class now comes with built-in logging functionality. By default, it uses the ColorLogger, which logs events in color. Here’s an example of how to use the default logger:

client = Nostr::Client.new

Logging with colors

If you prefer plain text logging without colors, you can use the PlainLogger:

require 'nostr/client/plain_logger'

client = Nostr::Client.new(logger: Nostr::Client::PlainLogger.new)

Logging without colors

To disable logging entirely, simply pass logger: nil when creating the client instance:

client = Nostr::Client.new(logger: nil)

Customizable Loggers

In addition to the default loggers, you can create your own custom logger by subclassing Nostr::Client::Logger and overriding its methods to tailor the logging format to your needs:

class CustomLogger < Nostr::Client::Logger
  def on_connect(relay)
    puts "Connected to relay: #{relay.url}"
  end
  
  def on_message(message)
    puts "Received message: #{message}"
  end
  
  def on_send(message)
    puts "Sent message: #{message}"
  end
  
  def on_error(message)
    puts "Error: #{message}"
  end
  
  def on_close(code, reason)
    puts "Connection closed: #{reason} (Code: #{code})"
  end
end

client = Nostr::Client.new(logger: CustomLogger.new)

More Changes in 0.7.0

This release includes several other improvements and updates. For a full list of changes, please refer to the CHANGELOG.

I would like to express my sincere gratitude to Matej Lukášik for reaching out, providing valuable feedback. His input directly influenced the implementation of logging in this release.

I encourage all users to continue sharing their experiences, suggestions, and feature requests. Your feedback is invaluable in shaping the future of the nostr gem. Together, we can make it an even more powerful and developer-friendly tool for building Nostr applications in Ruby.

Nostr 0.6.0 - Signatures

2024-03-19T13:49:00.000Z

I’m excited to share the release of version 0.6.0 of the nostr gem. Marking a significant update with a focus on enhancing cryptographic functionalities and introducing a systematic approach to documenting architectural decisions.

What’s new in `0.6.0`?

Architecture Decision Records (ADRs)
Message signing and verification
Event signature verification
KeyPair destructuring

Detailed Overview

Architecture Decision Records (ADRs)

I’ve begun documenting architectural decisions using Architecture Decision Records (ADRs). This structured approach aids in recording architectural changes and their rationale.

An ADR typically includes the following sections:

Title: A short, descriptive name for the architectural decision.
Status: The current status (proposed, accepted, deprecated, etc.) of the decision.
Context: The circumstances that led to the decision being considered.
Decision: A detailed explanation of the decision.
Consequences: The expected impact of the decision, both positive and negative.

Here’s an abbreviated example of an ADR for introducing the Signature class:

# ADR 0001: Introduction of Signature Class

## Status

Accepted

## Context

Before the introduction of the `Signature` class, signatures were
handled as simple strings throughout the nostr gem, leading to
repeated validation logic and the potential for errors.

## Decision

To encapsulate signature handling and validation in a single,
cohesive unit, we introduced the `Signature` class. This class
enforces the necessary validations at the point of creation,
providing a more robust and error-resistant approach.

## Consequences

Positive:
- Centralized signature validation logic, reducing repetition and potential errors.
- Improved code readability and maintainability.

Negative:
- Requires updates to existing codebases to utilize the new class.
- Adds a slight learning curve for new developers.

Message signing and verification

Introducing a Signature class addresses primitive obsession with string signatures by providing a dedicated class for signature handling, including validation and error handling.

signature = Nostr::Signature.new('your_signature_here')

This may raise InvalidSignatureTypeError, InvalidSignatureLengthError, or InvalidSignatureFormatError if the signature is invalid.

Furthermore, new functionalities for signing messages and verifying the authenticity of messages and events have been added, ensuring data integrity within the nostr ecosystem.

key_pair = Nostr::KeyPair.new(
  private_key: Nostr::PrivateKey.new('7d1e4219a5e7d8342654c675085bfbdee143f0eb0f0921f5541ef1705a2b407d'),
  public_key: Nostr::PublicKey.new('15678d8fbc126fa326fac536acd5a6dcb5ef64b3d939abe31d6830cba6cd26d6'),
)

crypto = Nostr::Crypto.new
message = 'Hello, nostr!'
signature = crypto.sign_message(message, key_pair.private_key)
crypto.valid_sig?(message, key_pair.public_key, signature) # => true

The valid_sig? method checks if a signature is valid, whereas check_sig! raises an error if the signature is invalid.

Event signature verification

Signing an event ensures its authenticity. Verification confirms the event was not tampered with.

event.sign(private_key)
event.verify_signature # true or false

`KeyPair` destructuring

Enhancing usability, the KeyPair class now supports destructuring, making it easier to work with private and public keys.

key_pair = Nostr::KeyPair.new(
  private_key: Nostr::PrivateKey.new('7d1e4219a5e7d8342654c675085bfbdee143f0eb0f0921f5541ef1705a2b407d'),
  public_key: Nostr::PublicKey.new('15678d8fbc126fa326fac536acd5a6dcb5ef64b3d939abe31d6830cba6cd26d6'),
)
private_key, public_key = key_pair

Coming next

The next release will focus on enhancing error messages and debugging capabilities. Feedback is welcome as development continues. Feel free to start a discussion on the GitHub repository.

Today I learned: 8 Sep 2023

2023-09-08T05:00:00.000Z

TL;DR

Plunk has a generous free plan, ideal for low-budget indie hackers
Plausible Analytics is dead simple and privacy-friendly
Deploying with Cloudflare pages is simple and fast
Open Graph tags are useful to make links look good on social media
Compiling Sass in the CLI
Replacing env variables in HTML files with Vite
Gandi.net domains cost 2 to 3 times more than other registrars

Introduction

From today onwards, I will blog about my learning journeys and other things I find interesting. I’m not sure how often I’ll do it, but I’ll try to do it as often as possible. This is the first post of this kind.

Today I developed a basic landing page for my social accountability platform, duty.camp, with a mission statement and a form to capture email addresses of people interested in the project.

It is ~~a modified copy of once.com source code~~ inspired by 37signals once.com landing page.

Duty Camp landing page

While doing that, I learned some useful things that I want to share with you.

Plunk

As part of my enrolment in buildspace’s nights & weekends season 4, I created a landing page for classes.pt using ConvertKit. I was happy with the result but:

It took me too long to deliver a simple landing page
The paid plan was too expensive, considering that I only captured 3 emails
The 2-week trial period was too short

I was looking for a cheaper alternative. As always, I even considered developing my own! Fortunately, I found Plunk, which has a generous free plan, allowing me to capture as much as 3000 emails per month! Plunk is

“the affordable, developer-friendly email platform that brings together marketing, transactional and broadcast emails into one single, complete solution”

I hope that one day I have enough revenue to repay the creator for his generosity.

Plausible Analytics

I also added Plausible Analytics to the site. It’s a privacy-friendly alternative to Google Analytics. It’s simple, fast and the 30 day trial period is more than enough to evaluate its limited features. I’m happy with it and I’ll probably upgrade to the paid plan in the future. I got a visitor from Belgium. I’m sure it was from the creator of Plunk, Dries Augustyns!

Plausible Analytics visitors by country

All visits from Thailand are mine. I have no idea how I got visitors from the United States. Perhaps it was a bot or Cloudflare.

Deploying with Cloudflare Pages

Cloudflare Pages is a new service that allows you to deploy static sites for free. It allows deployments via folder uploads as well as automated builds via git. I chose the latter. I was surprised how easy it was to set up.

On top of that, it is great to use a single platform to manage the needs of a static site: domain registration, DNS, CDN, SSL, deployment and much more.

Open Graph Tags

The Open Graph protocol enables any web page to become a rich object in a social graph. For instance, this is used on Facebook to allow any web page to have the same functionality as any other object on Facebook.

I knew that this could be achieved via meta tags, but never had the need to do it. By reading once’s source code, I was surprised how easy it was to do it.

Compiling Sass in the CLI

I have used sass/scss in the past and I briefly remember the syntax. But I had no idea how to compile it directly and what the underscore files were for. I assumed they were private files but I was wrong. They are partials and they are used to split the sass code into multiple files. This is useful to keep the code organised and to avoid having a single file with thousands of lines of code.

Finally, to compile and retain the source map of a directory with this structure:

assets/_sass
├── base
│    ├── _fonts.scss
│    ├── _reset.scss
│    └── _root.scss
└── styles.scss

Into assets/css/styles.css, I just had to run the command sass --watch assets/_sass:assets/css.

Replacing env variables in HTML files with Vite

Eventually, I found myself in need of a simple way to serve the page in development mode and production mode. In development mode it should use localhost. In production mode it should use the domain name.

Vite also supports replacing env variables in HTML files. Any properties in import.meta.env can be used in HTML files with a special %ENV_NAME% syntax:

<h1>Vite is running in %MODE%</h1>
<p>Using data from %VITE_API_URL%</p>

If the env doesn’t exist in import.meta.env, e.g. %NON_EXISTENT%, it will be ignored and not replaced, unlike import.meta.env.NON_EXISTENT in JS where it’s replaced as undefined.

Gandi.net high fees

Gandi.net has been overcharging me for all domains and offering me little to no value in return. I’m moving all my domains 5 to Cloudflare. Here’s an example of how much I’m saving. Renewing duty.camp would cost me 95€, worth 102 USD at the time of writing. In Cloudflare it costs 35 USD. That’s a 3x difference!

In defense of ‘boring’ tech: Pieter Levels’ SaaS success stories

2023-06-16T04:15:00.000Z

As we continually chase the latest tech trends, let’s not forget the value in embracing ‘boring’ but reliable technology. I personally aspire to emulate the likes of Pieter Levels, a well-known Indie Hacker. Utilizing tried-and-true tools like PHP and jQuery, he’s built a consistent monthly SaaS revenue stream of $250,000. His success is a testament to the fact that stable technology, mastered and applied effectively, often outweighs the allure of the newest trends. It’s a reminder that mastery of the fundamentals can lead to substantial success.

The strategies effective for a solopreneur without any stakeholders, deadlines or code-sharing responsibilities may not translate as efficiently to the context of a medium to large-scale enterprise. There are no silver bullets, but Levels does seem to be Blade!

Pieter Levels SaaS MRR stats

The perils of a hyperactive mind

2023-04-18T04:15:00.000Z

Ten years ago, I came across one of my favorite adages - if you commit to nothing, you’ll be distracted by everything. Back then, I was hyper-focused, hyper-committed, hyper-disciplined, and hyper-productive.

Fast forward to April 2023, things have changed. Although I’m interested in starting everything, I lack the commitment to finish anything. Here’s an example of what happened today:

I had scheduled 30 minutes for studying Thai and gathered my study materials - two boxes of flashcards for vowels and consonants. The consonant card box had instructions on memorablethai.com, while the vowel box had a video memory system on howtolearnthai.com.

Learn Thai flashcards

Unfortunately, howtolearnthai.com was no longer available, and memorablethai.com redirected to lannainnovation.com.

After some searching, I found the Innovative Video Memory System on YouTube in the form of playlists. However, this was the second time the support materials were unavailable to me. So, I decided to download the YouTube videos to my laptop.

While attempting to download the 34 videos, I faced several issues with different websites. Some could only download a video at a time, while others downloaded the video at ridiculously slow speeds. Eventually, I found the Pytube Python library, which helped me accomplish my goal.

I considered creating a Ruby equivalent. This led me to read about the YouTube API, but before I knew it, I was writing this blog post about my experience. My mind had hopped from one interest to another, and I never got around to learning Thai.

I worked on this blog post for an hour, and although I didn’t learn Thai, I made progress towards my blogging goal.

Getting a motorcycle driver’s license in Phuket

2023-04-07T04:30:00.000Z

I recently obtained my motorcycle driver’s license at Honda Safety Riding Park Phuket. The online booking process proved to be a bit challenging since the website was not entirely in English. However, I sought assistance from the staff by contacting them and also visited the park in person to get my questions answered.

Securing a spot for the Pre-Riding course required booking about 3 months in advance due to high demand. The cost was 2000 THB, and the practical lessons spanned 2 days. On the first day, I went through a physical aptitude test, received a brief introduction to the motorcycle’s basic functions, and then spent the rest of the day riding it through an obstacle course.

The second day involved more riding practice, an easy practical riding test, and a relatively quick theoretical lesson with a few mock exams on a computer. To pass the real exam, I needed to get 45 questions correct out of 50. The questions and answers were automatically translated from Thai to English, making the test a bit harder than expected.

Thankfully, I passed the exam on my first attempt. After passing the exam, I received a certificate. The next step was to visit a medical clinic to get a medical test done, which cost around 100 THB.

To proceed with obtaining the license, I needed a proof of address document, and I followed these steps:

Gathered the required documents, including passport-sized pictures, passport copies, copy of my visa, TM30, and 300 baht for processing fees.
Visited the local Immigration Office in Phuket to submit all the required documents and processing fee for the proof of address document.
The Immigration Office processed my application and provided me with the proof of address document. I made sure to obtain at least two copies since they might be needed for other purposes, like buying a motorcycle.

Once I had the medical check document, driving school certificate, passport, and proof of address document, I went to the Phuket Provincial Transport Office to book an appointment. At the appointment, they repeated the physical reflexes tests, took my pictures, I paid a few more hundred baht, and they printed my driver’s license. It’s important to have extra proof of address documents for other purposes, as obtaining them from immigration can be time-consuming.

Finally, I purchased a new motorcycle from a local dealer and rode it home with my new license.

Honda Click 160 Motorcycle

For a guide on how to choose a motorcycle, a helmet and other Phuket questions, see this collaborative document by Colin Dunn.

Documenting dry-structs

2018-09-16T00:00:00.000Z

Documenting attributes using YARD for Plain Old Ruby Objects is fairly straightforward:

class Location
  # Geographic coordinate that specifies the north–south position
  # of a point on the Earth's surface
  # 
  # @return [Float]
  attr_reader :latitude
  
  # Geographic coordinate that specifies the east-west position
  # of a point on the Earth's surface.
  # 
  # @return [Float] 
  attr_reader :longitude
  
  def initialize(latitude:, longitude:)
    @latitude  = latitude
    @longitude = longitude
  end
end

But sometimes the attributes are created using metaprogramming. One such example is dry-struct, a gem built on top of dry-types which provides a virtus-like DSL for defining typed struct classes:

class Location < Dry::Struct
  # Geographic coordinate that specifies the north–south position
  # of a point on the Earth's surface
  # 
  # @return [Float]
  attribute :latitude, Types::Strict::Float
  
  # Geographic coordinate that specifies the east-west position
  # of a point on the Earth's surface.
  # 
  # @return [Float] 
  attribute :longitude, Types::Strict::Float
end

The shortcoming of this approach is that YARD does not know how to generate documentation from the attribute declarations. This is where the directive @!attribute comes in.

It defines an attribute with a given name, using indented block data as the attribute’s docstring. If the type specifier is supplied with "r", "w", or "rw", the attribute is made readonly, writeonly or readwrite respectively. A readwrite attribute is the default, if no type is specified. The comment containing this directive does not need to be attached to any source, but if it is, that source code will be used as the method’s source.

class Location < Dry::Struct
  # Geographic coordinate that specifies the north–south position
  # of a point on the Earth's surface
  # 
  # @!attribute [r] latitude
  #   @return [Float]
  attribute :latitude, Types::Strict::Float
  
  # Geographic coordinate that specifies the east-west position
  # of a point on the Earth's surface.
  # 
  # @!attribute [r] longitude
  #   @return [Float]
  attribute :longitude, Types::Strict::Float
end

Improving my expressiveness

2017-04-05T00:00:00.000Z

Prologue

A few years ago, I assembled a mastermind group - a collective higher conscience to enforce discipline, support and accountability. Amongst other things, we were required to give weekly speeches.

Then I taught troublesome children from vulnerable socioeconomic backgrounds the rightful path to peaceful coexistence, through public speaking. Children have a short attention span, so I had to be succinct.

At work, I coached my colleagues on diverse software engineering subjects, such as architecture, defining boundaries, API and OO design, functional programming, best practices, and agile methodologies.

While they always got my message, and usually agreed with it, I always felt that the delivery could be greatly improved. My heart shouldn’t race and my throat shouldn’t close. But they did, too many times.

The last incident

Two days ago I attended a presentation on how to become an epic freelancer, in Chiang Mai, Thailand. The presentation was delivered by Josh Hoffman, a young and charismatic individual, just like me. Except that I’m not that charismatic. Yet.

Somewhere along his speech, he said:

I'm gonna ask a question, and I appreciate some audience participation. As a freelancer, what is your most important asset?

Josh Hoffman

I raised my hand and, when I was given permission to speak, I answered with confidence: “time”. Happiness flowed through his face as he exalted “bingo!”. He asked why, after a short pause to let the audience absorb his message.

Then I elaborated:

Time can only be spent. It cannot be saved. You cannot have a jar of time. And time is life. You work for money, and you spend life getting money.

Me being smart

He was very pleased with my answer, and gave me a high five. As he continued with his presentation, I noticed that I was very nervous and jittery, just because I said a few sentences in front of a small crowd. If the audience looked at me, they could see waves on my shirt, produced by my fast heartbeat.

The turning point

Out of that frustration, I decided to be truly gifted with words, written or spoken. In content and in delivery.

Words enable us to interpret and to express. If we have a limited vocabulary, we will also have a limited vision and a limited future. And I envision a better future.

Conclusion

I will write more often on my blog. Mostly to practice, but to share some strong opinions, loosely held, that I have about software engineering and how to make it more productive and enjoyable.

Repeating mistakes

2014-08-18T00:00:00.000Z

I believe there’s absolutely no problem in making mistakes. It happens. The Japanese have an interesting philosophy about it: “Shou ga nai”. Shou ga nai means “it can’t be helped” or “nothing can be done”. They accept reality and move on, just like Buddhists do.

Now, what I don’t believe in is the acceptance of making the same mistake over and over again. You shouldn’t make the same mistake twice, much less making a habit of it.

Some people say the best way to learn is by trial and error. I disagree with all my heart. While trial and error presents an opportunity for learning and improvement, in my opinion, learning how to do something right without making mistakes is way more satisfying.

My philosophy about mistakes is best explained with the last verse of one of my favorite rap lyrics:

I hate losing, I refuse to make the same mistake.

Black Thought

My first gem

2014-08-05T00:00:00.000Z

Oh, happy day! I feel good because of this. I’ve done some gems, but none ever got to see the light. My gem helps Ruby developers to know if a process exists.

require 'process_exists'

pid = 12
pid_exists = Process.exists?(pid)

I can’t sleep

2014-08-03T00:00:00.000Z

At 10 pm I turned my computer off and went to bed. I grabbed one of my favourite books by Jim Rohn - “The Seasons of Life”

and read it to make sure I was going to sleep with something positive on my mind. It had the opposite effect. Don’t get me wrong, the book is great, but it made me go through my memories about life and work and that got me stressed.

Eric Thomas said in one of his speeches:

Some of you love sleep more than you love success. If you're going to be successful, you got to be willing to give up sleep!

Eric Thomas

That speech just crossed my mind and I’m taking this opportunity (the lack of sleepiness) to be productive. I’m going to work on my projects.

Staying lean

2014-03-04T00:00:00.000Z

It took me 40 minutes to write this post. I wanted to explain how perfectionism was affecting the development of this website, then I threw the draft away. I was being a perfectionist again! I’m staying lean and agile. That’s my new way of life.

Wilson Silva

Today I learned: 26 May 2024

TL;DR

Introduction

Using Unify neural router to optimize LLM apps’ speed, latency and cost

Configuring Charles Web Debugging Proxy to inspect HTTPS/SSL traffic

Leveraging truststore to mitigate self-signed certificate errors in Python

Conclusion

Mistral Ruby gem

Why I ported Mistral’s client to Ruby

Python is everywhere

Sharing a common language

Other gems

Key takeaways

Nostr 0.7.0 - Logging

Built-in Logging Functionality

Customizable Loggers

More Changes in 0.7.0

Nostr 0.6.0 - Signatures

What’s new in 0.6.0?

Detailed Overview

Architecture Decision Records (ADRs)

Message signing and verification

Event signature verification

KeyPair destructuring

Coming next

Today I learned: 8 Sep 2023

TL;DR

Introduction

Plunk

Plausible Analytics

Deploying with Cloudflare Pages

Open Graph Tags

Compiling Sass in the CLI

Replacing env variables in HTML files with Vite

Gandi.net high fees

In defense of ‘boring’ tech: Pieter Levels’ SaaS success stories

The perils of a hyperactive mind

Getting a motorcycle driver’s license in Phuket

Documenting dry-structs

Improving my expressiveness

Prologue

The last incident

The turning point

Conclusion

Repeating mistakes

My first gem

I can’t sleep

Staying lean

Leveraging `truststore` to mitigate self-signed certificate errors in Python

What’s new in `0.6.0`?

`KeyPair` destructuring