Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Sweep (slow): What should I write about? #5

Open
1 task done
kent opened this issue Aug 30, 2023 · 1 comment · May be fixed by #6
Open
1 task done

Sweep (slow): What should I write about? #5

kent opened this issue Aug 30, 2023 · 1 comment · May be fixed by #6
Labels
sweep Assigns Sweep to an issue or pull request.

Comments

@kent
Copy link
Owner

kent commented Aug 30, 2023

Please read my blog by looking at the posts and the about Kent content and pick a blog post I should write about and draft it for me.

Checklist
  • _posts/2023-08-01-the-future-of-web3.md

• Start with an introduction that hooks the reader and introduces the topic of Web3. Kent has shown interest in this topic in his post "Future Fomo".
• Write the main body of the post, divided into subheadings. Discuss what Web3 is, why it's important, and how it's going to impact the future of technology. Include Kent's personal insights and predictions.
• Conclude the post by summarizing the main points and leaving the readers with something to think about. Kent often ends his posts with a thought-provoking question or statement.
• Maintain Kent's casual and conversational writing style throughout the post. Use first-person narrative as Kent does in his posts.
• Include personal anecdotes and experiences as Kent often does in his posts. This could be related to his experiences with Web3 or his thoughts on its future.

@sweep-ai sweep-ai bot added the sweep Assigns Sweep to an issue or pull request. label Aug 30, 2023
@sweep-ai
Copy link
Contributor

sweep-ai bot commented Aug 30, 2023

Here's the PR! #6.

💎 Sweep Pro: I used GPT-4 to create this ticket. You have unlimited GPT-4 tickets. To retrigger Sweep, edit the issue.


Step 1: 🔍 Code Search

I found the following snippets in your repository. I will now analyze these snippets and come up with a plan.

Some code snippets I looked at (click to expand). If some file is missing from here, you can mention the path in the ticket description.

---
layout: post
title: "Consistency Is Hard"
date: 2022-11-15 18:40:19 -04:00
---
> I will write a book, how hard can it be?
I think back to this article I read [So You Want to be a Writer?](https://hughhowey.com/so-you-want-to-be-a-writer/), that prompted me to publicly commit and write this [writing daily](https://ewakened.com/posts/writing-daily) and back then, in September I committed to write 80 posts by the end of the year. I have written... 7.
Consistency is hard. I have read many books on habits, on kaizen, on daily improvement, all of that and all I have really learned is that consistency is hard. Am I too hard on myself though? I've got a busy day job, a healthy curiosity of side projects to keep my mind sharp, don't forget the kids and my wife, not to mention my parents that are aging and need more help. Still, excuses.
So, what should I do? Give up? Say I was too ambitious? That is always the case, I am always too ambitious and I love that about me, so no, I will not give up, in fact, I will double down and recommit today to the process and idea of one post a day. It is November 15th, that means that we have 47 days until the end of the year. It's a far cry from 80, but 47 would be pretty epic.

---
layout: post
title: "A book in me"
date: 2022-10-03 18:40:19 -04:00
---
I found myself writing this one Sunday evening and it's true. Of all the times I have had something to say, I finally think I have enough words to say what I want, in a way that I haven't seen before. What stops me from taking a step forward isn't that I am too lazy to get started or put in the work, quite the opposite. My problem is the crushing imposter syndrome.
In order to make something worth reading, I feel like that has to say something about me and my life. That somehow my life is worthy of a book and worthy of you caring. The book I have in me is part auto biographical and partially about startup equity. How to value it, how to negotiate it for it, when it matters, when it doesn't. I have had so many good and bad stories about equity it's hard to keep track of them, but as I started sketching it out, I found that I do have something to say, that hasn't been said.
But aren't there hundreds of folks more qualified than me? Hundreds, likely thousands. Why doesn't this book exist yet? I don't know, but am committed to take some steps to find out.
Well, it's been 18 days since my last post. So much for once a day. Let's see if I can get it started... now.

---
layout: post
title: "Future Fomo"
date: 2022-09-17 18:40:19 -04:00
---
How do you judge different great opportunities? How privledged do I need to be where my biggest concern is deciding between great outcomes. Ultimately, how much money is enough? What is important in daily life? Should you shoot for the moon? Aim for the stars?
Looking into the future there are a few things that are clear. Web3 isn't going anywhere and legacy Web2.0 business will slow turn into Web3 businesses. Everything from media, to insurance, to banking, to lending, to commerce will sit on a blockain of sorts. The distributed power of Web3 follows the same trend that there are only two business models. Bundling, and unbundling. Web3 is the unbundling of Web2.
Then there is the metaverse. I am spending at least 15 minutes a day in VR. My favoruite thing to do is fire up [Horizon Workrooms](https://www.oculus.com/workrooms/) and just check my email in VR. Feels weird to say that, but it's true. Something about "working from anywhere" is really cool, and if Meta just doubled down on those environments I think that app, even without others would be a daily use for me.
Then there is the legacy Web2 world that still has enough life in it for disruption. Or maybe there is a way to combine all three together.
Utlimately it comes back to the Framework, I will investigate that in another post. For now, more questions than answers.

---
layout: page
title: About
description: Software engineer and founder living in Toronto. I write about software engineering, parenting, startups, and life.
permalink: /about/
---
Welcome to the world of Kent Fenwick – a creative visionary, technology enthusiast, and innovative problem-solver. With an unwavering passion for all things tech and a keen eye for detail, Kent has spent years honing his skills and mastering the art of creating digital solutions that elevate businesses and simplify everyday life.
## A Bit About Kent
Kent Fenwick was born with a natural curiosity and a love for technology. Ever since he was a child, he was fascinated with how things worked, often taking apart household gadgets and putting them back together. This passion for understanding technology only grew stronger over time, leading him to pursue a degree in Computer Science and Engineering. He has since amassed over a decade of experience in the tech industry, working with a diverse range of clients and projects, from startups to established corporations.
## Kent's Expertise
As a full-stack developer and software engineer, Kent has a vast range of skills at his disposal. He specializes in creating intuitive, user-friendly applications and platforms that seamlessly integrate with existing systems. His technical expertise spans across various programming languages, frameworks, and tools, including Python, JavaScript, React, and Node.js, among others.
Apart from development, Kent also boasts a deep understanding of data analytics, using data-driven insights to optimize processes, improve user experiences, and inform strategic decision-making.
## Collaborations and Projects
Kent's portfolio showcases his versatility and commitment to excellence. Some of his most notable projects include:
An eCommerce platform for a major retail brand, which streamlined the online shopping experience for millions of users.
A custom content management system for a media company, designed to efficiently manage and distribute their digital assets.
A mobile app for a non-profit organization, which helped increase engagement and raise awareness for their cause.
Get in Touch
When Kent isn't immersed in code or dreaming up innovative solutions, he enjoys exploring nature, photography, and expanding his culinary skills. He believes that life is about constantly learning and evolving, both personally and professionally.
If you're interested in collaborating with Kent, discussing a project, or simply want to chat about the latest tech trends, feel free to reach out via the contact form on this website or connect with him on LinkedIn and Twitter.

---
layout: post
title: "Legacy"
date: 2022-11-10 18:40:19 -04:00
---
When I was younger I spent a lot of time thinking about my legacy. Now, I do too but in a very different way. I came up in the age right after the dot com boom and bust. I learned how to program and build web and mobile apps in 2003. In fact, I remember getting a ride home with a friend of mine in Comp Sci in 3rd year who told me he picked up a book about Rails. I had no idea what he was talking about. I worshiped Musk, Thiel, Levchin, Rose, Ferriss and others. These were my tech idols and gods and I would join them in olympus soon.
That idea changed when I had kids as so many things do. I turned down a lucrative offer from Airbnb as it would have meant a move to San Francisco, something my wife and I didn't want for our kids. I started realizing that the thing that a lot of people feel like they need and are chasing, I already had. I had a purpose and it was, these kids. This family.
As we move into the holiday season, I get more reflective. Choices I've made, doors that were open, now closed, new doors about to open. The constant is children, and family and life and legacy. I love the movie a Christmas Carol, I watch it 3-4 times a year around Christmas time. Different avatars, the best being Mickey's Christmas Carol. I also love the movie the Family Man as I resonate with that character. I have a fear right now, that I am living in that life. That I will wake up ten years ago, to that time I almost moved to San Francisco and this path, this family filled life will be a dream that I can't get back to and fades more and more over time. That's why I have to enjoy each day, each moment here, as I could wake up tomorrow and know the choice I need to make.


Step 2: 🧐 Snippet Analysis

From looking through the relevant snippets, I decided to make the following modifications:

File Path Proposed Changes
_posts/2023-08-01-the-future-of-web3.md Create _posts/2023-08-01-the-future-of-web3.md with contents:
• Start with an introduction that hooks the reader and introduces the topic of Web3. Kent has shown interest in this topic in his post "Future Fomo".
• Write the main body of the post, divided into subheadings. Discuss what Web3 is, why it's important, and how it's going to impact the future of technology. Include Kent's personal insights and predictions.
• Conclude the post by summarizing the main points and leaving the readers with something to think about. Kent often ends his posts with a thought-provoking question or statement.
• Maintain Kent's casual and conversational writing style throughout the post. Use first-person narrative as Kent does in his posts.
• Include personal anecdotes and experiences as Kent often does in his posts. This could be related to his experiences with Web3 or his thoughts on its future.

Step 3: 📝 Planning

I have created a plan for writing the pull request. I am now working my plan and coding the required changes to address this issue. Here is the planned pull request:

Add new blog post: The Future of Web3
sweep/add-web3-blog-post

Description

This PR adds a new blog post titled "The Future of Web3" to the ewakened.com blog. The post is based on an analysis of Kent's previous posts and his about page, ensuring that it aligns with his writing style, tone, and interests.

Summary of Changes

  • Analyzed Kent's writing style, tone, and structure from previous posts
  • Brainstormed potential blog post topics based on Kent's professional background and personal interests
  • Chose the topic "The Future of Web3" based on Kent's interest in the topic as shown in his post "Future Fomo"
  • Drafted an outline for the blog post, including an introduction, main body, and conclusion
  • Wrote a draft of the blog post, maintaining Kent's writing style and tone throughout
  • Reviewed and revised the draft to ensure it is engaging, informative, and aligns with Kent's usual content

Please review and provide feedback on the new blog post.


Step 4: ⌨️ Coding

File Instructions Progress Error logs
_posts/2023-08-01-the-future-of-web3.md Create _posts/2023-08-01-the-future-of-web3.md with contents:
• Start with an introduction that hooks the reader and introduces the topic of Web3. Kent has shown interest in this topic in his post "Future Fomo".
• Write the main body of the post, divided into subheadings. Discuss what Web3 is, why it's important, and how it's going to impact the future of technology. Include Kent's personal insights and predictions.
• Conclude the post by summarizing the main points and leaving the readers with something to think about. Kent often ends his posts with a thought-provoking question or statement.
• Maintain Kent's casual and conversational writing style throughout the post. Use first-person narrative as Kent does in his posts.
• Include personal anecdotes and experiences as Kent often does in his posts. This could be related to his experiences with Web3 or his thoughts on its future.
✅ Commit 8420712 No errors.

Step 5: 🔁 Code Review

Here are my self-reviews of my changes at sweep/add-web3-blog-post.

I finished incorporating these changes.


🎉 Latest improvements to Sweep:

  • Use Sweep Map to break large issues into smaller sub-issues, perfect for large tasks like "Sweep (map): migrate from React class components to function components"
  • Getting Sweep to format before committing! Check out Sweep Sandbox Configs to set it up.
  • We released a demo of our chunker, where you can find the corresponding blog and code.

💡 To recreate the pull request edit the issue title or description.
Join Our Discord

@sweep-ai sweep-ai bot linked a pull request Aug 30, 2023 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
sweep Assigns Sweep to an issue or pull request.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant