Skip to content

Commit

Permalink
chore: update cpast links
Browse files Browse the repository at this point in the history
  • Loading branch information
rootCircle committed Oct 28, 2024
1 parent 15435c4 commit de6f5d0
Show file tree
Hide file tree
Showing 3 changed files with 3 additions and 3 deletions.
2 changes: 1 addition & 1 deletion docs/archives/misc/buggy_code.md
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,7 @@ Upon coming to college, I was introduced to CS50x, an introductory course by Har

Later, a few of my college seniors introduced me to Rust. Initially, I couldn’t fully appreciate the beauty of what seemed like such a complex masterpiece. Rust was difficult, I admit, but it was equally rewarding. The beauty of this language lies not just in its syntax or its features but in the community and processes that shape it. The development of Rust involves a lot of discussion, resolution, documentation, and RFCs (Requests for Comments) to refine the language into something so well-designed.

As a beginner developer, I used to code first and think about architecture later. However, interacting with the Rust community taught me to approach coding differently. I began to think more critically before diving into writing code. This shift in mindset helped me immensely in designing systems that truly matched my vision. For example, I once rewrote the lexer and parser for a domain-specific language (DSL) _three times_ just because I hadn't defined the grammar properly beforehand. (Fun fact: you can check out that project [here](https://github.com/rootCircle/cpast)). This experience taught me the importance of planning and design in software development—an invaluable lesson that has shaped how I approach projects ever since.
As a beginner developer, I used to code first and think about architecture later. However, interacting with the Rust community taught me to approach coding differently. I began to think more critically before diving into writing code. This shift in mindset helped me immensely in designing systems that truly matched my vision. For example, I once rewrote the lexer and parser for a domain-specific language (DSL) _three times_ just because I hadn't defined the grammar properly beforehand. (Fun fact: you can check out that project [here](https://github.com/rootCircle/cpast_mono)). This experience taught me the importance of planning and design in software development—an invaluable lesson that has shaped how I approach projects ever since.

These beautifully crafted software tools, like Rust, involve a lot of discussion, resolution, documentation, and RFCs to be so refined. As beginner developers, we often code first and think about architecture later. But this interaction with Rust's development process taught me to think first and code later. This approach helped me in designing systems that truly fulfilled my vision.

Expand Down
2 changes: 1 addition & 1 deletion docs/archives/misc/cost_of_not_initializing_variables.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,7 +24,7 @@ head:

## Introduction

Last week, I was benchmarking one of my tools named [cpast](https://github.com/rootCircle/cpast) with [hyperfine](https://github.com/sharkdp/hyperfine), and I observed something strange! With the completion of every other odd benchmark, my PC started to hang after a few seconds! The memory usage was spiking a lot ***after*** the benchmark was complete. I was pretty sure, it was not a memory leak, as I was not [leaking any memory intentionally](https://stackoverflow.com/questions/55553048/is-it-possible-to-cause-a-memory-leak-in-rust) and cpast was written in Rust as well, with all memory safety features built-in!
Last week, I was benchmarking one of my tools named [cpast](https://github.com/rootCircle/cpast_mono) with [hyperfine](https://github.com/sharkdp/hyperfine), and I observed something strange! With the completion of every other odd benchmark, my PC started to hang after a few seconds! The memory usage was spiking a lot ***after*** the benchmark was complete. I was pretty sure, it was not a memory leak, as I was not [leaking any memory intentionally](https://stackoverflow.com/questions/55553048/is-it-possible-to-cause-a-memory-leak-in-rust) and cpast was written in Rust as well, with all memory safety features built-in!

![Memory usage of orphan process after few seconds](./data/orphan_memusage.png)

Expand Down
2 changes: 1 addition & 1 deletion docs/project/cpast.md
Original file line number Diff line number Diff line change
Expand Up @@ -179,7 +179,7 @@ As **cpast** stands as a valuable tool for code testing and analysis, the journe
Ready to elevate your CP experience? Dive into the world of cpast and let it handle the heavy lifting while you focus on crafting winning code!
[Check out cpast on GitHub](https://github.com/rootCircle/cpast)
[Check out cpast on GitHub](https://github.com/rootCircle/cpast_mono)
[cpast on crates.io](https://crates.io/crates/cpast)
Expand Down

0 comments on commit de6f5d0

Please sign in to comment.