It’s obviously an advertisement but it made me think about how much we actually work in our lives. I looked up the average lifespan of a male in the USA and got this:

That’s depressing. We work most of our lives. I know that wasn’t their intent but yeah.

Fuck.

References

• https://www.cdc.gov/nchs/fastats/life-expectancy.htm

I’d rather do a hackathon outside of work with friends or colleagues, even if there is no financial gain.

You might ask, “if you don’t care about money, why not just do a hackathon for your company?”.

If I join a hackathon outside of work I can do it to potentially create a side hustle or simply for the joy of creating software.

If I volunteer to work on a hackathon for my employer, my ideas and creations are taken from me even if I enjoy working on these projects. It feels like someone is taking advantage of me, especially if hackathons are not part of my job description and I receive no additional compensation for participating. If there is compensation, it’s usually something like a $100 Amazon gift card.

Maybe it’s just me that can’t get motivated or excited about a company hackathon.

I can summarize company hackathons like this: you come up with a million dollar idea for your employer and (maybe) get $100 in return.

To resolve this warning, I added a Cache-Control header with the value max-age=31536000 to the HTTP responses of my domain (31536000 is the number of seconds in a year).

I host nelson.cloud on Amazon CloudFront. I added this header to the CloudFront Distribution that the nelson.cloud domain points to. This can be done by adding a “Response headers policy” in the Behavior of the Distribution. I wrote a post demonstrating how to do this in detail: How to Add a Custom Response Header to an Amazon CloudFront Distribution.

After the header was configured, I checked PageSpeed Insights again and the warning had gone away for the assets under my domain nelson.cloud:

(The remaining asset is not under my control so I can’t fix that one.)

Note:

You may be able to use a different value smaller than 31536000 for your header. I chose a year in seconds to be on the safe side for PageSpeed Insights.

References

• https://developer.chrome.com/docs/lighthouse/performance/uses-long-cache-ttl/
• https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cache-Control
• https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/Expiration.html

Go to the AWS Console and click into your CloudFront Distribution. Then click on the “Behaviors” tab. If you already have a behavior, you can edit the existing one. Otherwise, create a behavior.

I won’t cover the other Behavior settings as that is out of the scope of this post, but to add a custom response header look for the “Response headers policy - optional” field which is under “Cache key and origin requests”.

Click on the “Create response headers policy” link. On the next page fill in the “Name” field at the very top. Then, scroll a bit down and you should see the “Custom headers - optional” field.

Click on the “Add header” button and add the custom header you’d like. In my case, I added the Cache-Control header with a value of max-age=31536000. I also checked the Origin override box because I want this header to take precedence over other headers that may be set in the origin.

Then click the “Create” button on the bottom right. You’ll be redirected to CloudFront > Policies. You can see your newly created response header under the “Response headers” tab. In my case it’s called cache-control-header.

Now that this custom header policy is created, browse back to your Distribution and click on the “Behaviors” tab. Edit an existing Behavior or create one. Scroll down to the “Response headers policy - optional” field again. Then, select your new response header policy.

Then save your changes.

Wait a few minutes and your distribution will be updated with the new header. There is no need to create an Invalidation.

You can test this out by running curl -IX GET <your-distribution-domain-name>. Your output should look something like this. Look for your custom header in the output. In my case, cache-control shows up at the very bottom.

$ curl -IX GET https://abcdefghijklmn.cloudfront.net

HTTP/2 301
content-length: 0
location: https://nelson.cloud/index.html
date: Wed, 01 Jan 2025 08:12:11 GMT
server: AmazonS3
x-cache: Hit from cloudfront
via: 1.1 98167d64569fd17ca63a5b7db2edfe28.cloudfront.net (CloudFront)
x-amz-cf-pop: LAX54-P1
x-amz-cf-id: l5n0bciPQfswC27jGnhcrkuldHWFDgZx0JdYo406qkoKKKP87i_dsA==
age: 2292
cache-control: max-age=31536000

Done!

References

• https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers
• https://stackoverflow.com/questions/56187791/how-to-set-cache-control-header-in-amazon-cloudfront
• https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/modifying-response-headers.html

You can copy and paste these into HTML templates. If you want to use these within your posts/articles (Markdown files) you’ll need to create a shortcode first. Scroll down to the Using Shortcodes section for more details.

I’m running Hugo v0.140.0+extended.

For all examples, I will assume the time is 2024-12-22 2:30PM PT.

Date Only

1

{{ now | dateFormat "2006-01-02" }}

2024-12-22

1

{{ now | dateFormat "2006-01-02 3:04" }}

2024-12-22 2:30

1

{{ now | dateFormat "2006-01-02 3:04PM" }}

2024-12-22 2:30PM

2024-12-22 2:30AM

1

{{ now | dateFormat "2006-01-02 15:04" }}

2024-12-22 14:30

1

{{ now | dateFormat "2006-01-02 15:04 PST" }}

2024-12-22 14:30 PST

1

{{ now | dateFormat "2006-01-02 15:04 test" }}

2024-12-22 14:30 test

1

{{ now | dateFormat "2006-01-02 15:04 PST -0700" }}

2024-12-22 14:30 PST -0800

1

{{ now | dateFormat "2006-01-02 15:04 PST UTC-0700" }}

2024-12-22 14:30 PST UTC-0800

1

{{ now | dateFormat "2006-01-02" }}

1

{{< generate_date >}}

1
2
3
4
5

# A Header in Markdown

Some text in markdown

*The current date is*: {{< generate_date >}}

1
2
3

<noscript>
    <blockquote>This message only shows up when JavaScript is disabled!</blockquote>
</noscript>

1
2
3
4
5
6
7
8
9

<noscript>
    <style>
        blockquote#example {
            font-style: italic;
        }
    </style>
</noscript>

<blockquote id="example">The text within this blockquote element is italicized when JavaScript is disabled!</blockquote>

1
2
3

button:active {
  transform: translateY(4px);
}

1
2
3
4
5
6

@media (prefers-reduced-motion) {
    /* anything in here will apply on devices with reduced motion enabled */
    button:active {
        transform: none;
    }
}

1
2
3
4
5
6
7
8
9

body {
  background-color: red;
}

@media (prefers-reduced-motion) {
    body {
        background-color: blue;
    }
}

1
2
3
4
5
6
7

class Category < ApplicationRecord
  has_many :transactions, dependent: :nullify
end

class Transaction < ApplicationRecord
  belongs_to :category
end

1

defaults write com.apple.screencapture "disable-shadow" -bool "true"

1

defaults delete com.apple.screencapture "disable-shadow"

resume.pdf filetype:pdf site:github.io

resume.pdf filetype:pdf site:github.com

resume filetype:pdf site:pages.dev

resume filetype:pdf site:netlify.app

resume filetype:pdf site:*.me

resume.pdf filetype:pdf site:*.dev

boston resume filetype:pdf site:*.dev

University of California Los Angeles resume filetype:pdf site:*.dev

"Apple, Inc" resume filetype:pdf site:*.dev

"resume.pdf" "Raytheon" filetype:pdf

1
2
3
4
5
6
7
8
9

package main

import "fmt"

func main() {
	for i, v := range "testing" {
		fmt.Printf("index: %d, char: %c\n", i, v)
	}
}

index: 0, char: t
index: 1, char: e
index: 2, char: s
index: 3, char: t
index: 4, char: i
index: 5, char: n
index: 6, char: g

1
2
3
4
5
6
7
8
9

package main

import "fmt"

func main() {
	for _, v := range "testing" {
		fmt.Println(v)
	}
}

116
101
115
116
105
110
103

 1
 2
 3
 4
 5
 6
 7
 8
 9
10
11

package main

import "fmt"

func main() {
	str := "testing"

	for i := 0; i < len(str); i++ {
		fmt.Printf("index: %d, char: %c\n", i, str[i])
	}
}