Skip to content

Commit fdc3ed7

Browse files
committed
Improve post and add references in others
1 parent e61d946 commit fdc3ed7

4 files changed

Lines changed: 82 additions & 29 deletions

File tree

_posts/2025-08-18-blog-posts-in-2025.md

Lines changed: 16 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -131,3 +131,19 @@ The conclusion after writing blogpost number one was: After almost a full day of
131131
I wish I knew how much time I actually saved by using Gemini, and if I would have found my mistake more easily had I not been in "LLM" mode with my brain. But it for sure felt like a pleasant and productive day, and I did learn a ton, not only about optimization but also about interacting with Gemini.
132132

133133
The conclusion after writing blogpost number two is: for evolutions of the original blogpost and notebook, Gemini definitely saved me so much time. The reason is that most of the thinking and reiterating was already done with the first blogpost, and that blogpost was super useful to provide context to the second blogpost.
134+
135+
## Addendum: Using LLM as a reviewer
136+
137+
In some follow-up blogposts, such as [this one](/research/2025/10/27/subspaces.html), I did not use the same pipeline but used LLMs mostly to type up my (this time, more complete) handwritten notes. However, I found it super useful to use the following prompt, which I also added to my "library of prompts" to review the post before publishing it. As attachment I simply uploaded my finalized post.
138+
139+
```
140+
I have written a blog post; see the attachment. Please provide a critique of this blog post, structured as follows:
141+
1. General comments
142+
– Is this blog post standalone understandable by a non-expert? My target audience is graduate students and beyond with good literacy in linear algebra and optimization. If not, suggest a few concrete, concise additions that would make the blog post more understandable, in Jekyll Markdown format.
143+
2. List of typos
144+
– Provide a concise list of obvious typos and English mistakes
145+
3. English improvements
146+
– Suggest any edits in terms of language, keeping the same tone as the original blog post, but making it easier to read.
147+
```
148+
149+
I didn't integrate most of what was suggested under point 3, since I found it unnecessary (maybe this is due to my own ignorance, but I prefer to keep my tone unless I am convinced the proposed solution is better). But under points 1 and 2 it suggested valuable additions and spotted non-trivial mistakes!

_posts/2025-08-18-kernel-image-primal-dual.md

Lines changed: 3 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -5,7 +5,9 @@ date: 2025-08-18
55
categories: [research]
66
---
77

8-
_I finally got around to writing my first blogpost, thanks to LLMs. This blogpost is not just AI-generated, but thanks to the latest and greatest LLM magic, the time to go from handwritten notes to a polished blogpost was greatly reduced. For full transparency, and maybe because others might find this interesting, I am writing [another blogpost](/misc/2025/08/18/blog-posts-in-2025.html) about my process to generated this blogpost (and hopefully a few more in the future) using Gemini.
8+
_Note from November 3rd 2025: The concepts of this blogpost are better described in the [more recent post](/research/2025/10/27/subspaces.html)_
9+
10+
_I finally got around to writing my first blogpost, and it was partly thanks to LLMs. This blogpost is not just AI-generated, but thanks to the latest and greatest LLM magic, the time to go from handwritten notes to a polished blogpost was greatly reduced. For full transparency, and because others might find this interesting, I am writing [another blogpost](/misc/2025/08/18/blog-posts-in-2025.html) about my process to generated this blogpost (and hopefully a few more in the future) using Gemini.
911
If you are interested in the follow-up question: tackling minimization rather than feasibility problems with SOS, you might want to look at [this follow-up post](/research/2025/08/24/kipd-minimization.html)_
1012

1113
Checking if a polynomial is non-negative is a fundamental problem that appears in many areas of engineering and mathematics. While checking for non-negativity is computationally hard in general, a powerful sufficient condition is to check if the polynomial can be written as a sum of squares (SOS) of other polynomials. This condition is not only tractable—it can be checked by solving a semidefinite program (SDP)—but it is also a key component in a wide range of optimization methods for polynomial systems.

_posts/2025-08-24-kipd-minimization.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -5,6 +5,8 @@ date: 2025-08-24
55
categories: [research]
66
---
77

8+
_Note from November 3rd 2025: The concepts of this blogpost are better described in the [more recent post](/research/2025/10/27/subspaces.html)_
9+
810
_This is a follow-up to my [previous post](/research/2025/08/18/kernel-image-primal-dual.html) on different formulations (Kernel, Image, Primal, Dual) of Sum-of-Squares (SOS) feasibility problems. This post took significantly less time to write because it is really an evolution of the previous post, which Gemini is amazingly good at. I added a paragraph about this in [other post](/misc/2025/08/18/blog-posts-in-2025.html) about writing blog-posts with the helpf of Gemini_
911

1012

0 commit comments

Comments
 (0)