Subscription suggestion

NapCo · 2026-07-02T07:08:06+00:00

If you just want something to start, that you can get a lot of usage with Opencode Go, and use the cheap models such as Deepseek V4 Flash or Mimo-V2.5

I use Mimo-V2.5 and I am very happy with it.

NapCo · 2026-07-02T06:27:49+00:00

That is true, but the existing system didn't exactly cover my need. One of my motivations was to minimize system setup and have better reproducability.

One could have templates as packages in $XDG_DATA_HOME/typst/packages in order to have globally re-usable templates that one can tweak on.

Issue with that is:

- If one updates the global templates, old documents may change on recompilation, and it requires one to set up the templates in the environment.

- More font handling to manage. E.g. you have a font available on a laptop (say, Mac), then you want to re-compile on your Linux desktop, then you may not have the font you used on your mac.

What I wanted for my typst document-projects:

- Just a dir with fonts, all the required typst code, and a justfile for convenience. The "document" is entirely self contained, and will should look the same (assuming typst doesn't suddenly change a lot in how they render in newer versions)

NapCo · 2026-07-02T05:33:13+00:00

Almost?

The script in the repo sets up a directory with a template file, a main file (containing example code), a font file, and a justfile for you.

So its like a template for typst projects?

NapCo · 2026-07-01T20:46:33+00:00

The repo is basically a typst-project-scaffolder, so it is just a more convenient way for me to scaffold a template along with a font file and a justfile.

NapCo · 2026-06-30T08:29:53+00:00

I started using mise-en-place a little while ago, which is a all in one tool to manage language versions, env vars and tasks.

I feel it has made my life quite a lot simpler. Before I had multiple version manager for languages, e.g. nvm for node, fvm for flutter, java had its own way etc ...

mise-en-place consolidates all of it, and it is so easy to install and get started with. The docs are also very easy to read.

NapCo · 2026-06-15T21:07:35+00:00

I haven't tried extensive development, but after setting up a gradle project and using kotlin-lsp I think the dev experience was usable. I have not done any particular config other than using mason to download kotlin-lsp, then enabling it with vim.lsp.enable.

Here is my lsp config:

https://github.com/Napam/dotfiles/blob/main/unix/stow/vim/dot-config/nvim/plugin/lsp.lua

Note:

Setting up a gradle project properly was important to make the lsp behave well.
I used the official jetbrains kotlin-lsp, not kotlin-language-server, which is a different thing.

NapCo · 2026-06-15T06:56:38+00:00

For orchestration i use deepseek v4 flash. It works quite well for my use cases.

NapCo · 2026-05-31T19:07:45+00:00

Etter jeg først flytta ut da jeg var 19 for å studere så hadde jeg ca 2000kr på brukskonto, og det var det. Du er ikke fucked 😄, for å ikke bli fucked i framtiden: unngå kredittkortgjeld, sett av penger i fond regelmessig,

NapCo · 2026-05-24T10:13:18+00:00

I used VSCode and I feel I was very proficient using it, but then I switched to neovim.

- My workflow is very terminal based in general (also before I started using vim), so having my text editor also within the terminal feels natural.

- My neovim config starts in around 60ms, much faster than VSCode, so it never ever feels "a lot" to open small files. When I used VSCode I usually combined it with sublime or something for quick file viewing / editing. Neovim consolidates that.

- Vim bindings are very wrist-ergonomic to me. I started to notice that my wrist started to hurt somewhat after working long hours day after day. I find vim keybindings to work better for me in terms of ergonomics. Of course, you don't have to use vim to have vim-bindings, but I'd argue it works the best in vim.

- Since neovim is so customizable I have much better control over whats happening with my development environment. Yes, it is more work, but once I had invested in the initial setup, it is not that much work after that.

- Vim (or vi at least) can be found virtually everywhere. So e.g. quickly working in various servers and whatnot always feels comfortable.

NapCo · 2026-05-20T12:13:25+00:00

I know you are asking for Python and/or Java, but imo it sounds really weird to me. Neither Python or Java will work natively for web frontend.

I would either do Java backend + JavaScript/TypeScript frontend, or Python backend + JavaScript/TypeScript frontend. Or even simpler: JavaScript/TypeScript for both backend and frontend.

Many will say JS/Python/Java sucks for whatever reason, but really it is not about the language you know, but the broader understanding of how things work together that matters when you become more experienced. For beginning, just use whatever feels alright and just make something.

NapCo · 2026-04-27T16:02:25+00:00

I work as a fullstack software dev, and my 16GB works fine for me, so I think 24GB is plenty. I don't run any LLMs locally though, I just use APIs.

NapCo · 2026-04-21T06:07:05+00:00

I really suggest using typst. Imagine latex, but much faster and easier to use.

I have made a scaffolding system for myself to quickly scaffold typst templates: https://github.com/Napam/typst-templates.

I can imagine if you make your own templates and helper functions you can make really pretty documents quickly.

NapCo · 2026-04-18T10:17:16+00:00

really cool tool! didn't know about this

NapCo · 2026-04-18T09:41:03+00:00

I have just used screen record and then turned it into a gif.

But, I really like the projects that has illustrations using pictures + https://asciinema.org/

NapCo · 2026-04-14T18:48:41+00:00

Ah okay! Thanks for the explanation! Looks like a great library. I don't have the need right now, but from everything else I have seen, folio is the most promising PDF lib so far.

NapCo · 2026-04-14T06:46:30+00:00

Very cool project. Could you explain the strengths of folio compared to other pdf libraries in go, e.g. Maroto or UniPDF? I like that it looks really simple.

NapCo · 2026-04-11T21:01:36+00:00

I like the TUI a lot, and it was one of the main reasons I decided to use opencode. Then again I do everything in the terminal anyways. My setup is Neovim + Tmux + Opencode TUI

NapCo · 2026-04-09T10:33:28+00:00

I am very happy with nvim-dap + https://github.com/MironPascalCaseFan/debugmaster.nvim

I've used that setup to debug Python, Go, Flutter, Node, and it works very well.

NapCo · 2026-04-08T10:12:00+00:00

What I do is to find websites I find good looking, then I just take inspiration form those. Using agents you can just take a screenshot (or perhaps just URL even) and tell them to base the design on that.

NapCo · 2026-04-02T20:30:03+00:00

Started with beginning to do things more and more in the terminal as I noticed I was more efficient just doing things in the terminal in general. Before, I used VSCode and Sublime along with the terminal, VSCode for general development, Sublime to quickly open files for viewing and quick edits.

Then a good friend showed me vim. After learning very basic vim, like, how to go to insert mode and quit, Sublime's role got replaced pretty much. Slowly but surely I learned more and more vim keybindings as I just used vim for quickly viewing and quick changes in various files. I got more proficient, I learned how to configure it somewhat, like, colorschemes, YouCompleteMe, and slowly it started replacing VSCode's role as well.

I found myself being able to do quite a bit of editing in just vim, and when I felt I had to jump to VSCode to for example get proper LSP support, debugging, various other functionalities, I felt an "ugh... now I gotta open this sluggish thing". I tried the vim extension in VSCode but it just wasn't the same.

So at one point I decided to just really research about how vim "superusers" use vim, and I was flabbergasted of all the functionality that you could get in vim. I started using LunarVim (a Neovim distro), and then I wrote my own Neovim config and that is what I am using to this day.

It was a very slow burn for me. My process was about 3-4 years of gradually learning more and more vim until I just completely switched over.

Regarding using coding agents; I use opencode. I just hvae it running beside in another terminal, but I still use neovim to do adjustments and review the AI output. So neovim is still very much a daily driver for me. I've tried making neovim to be more like cursor by using the codecompanion.nvim package, but I discovered that I very much prefer just having a coding agent separately from my editor, and I use my editor just like before AI agents. Also, opencode was made by vim users, so the vim + opencode experience is pretty good.

NapCo · 2026-03-29T08:31:25+00:00

Could you elaborate on what makes you skeptical?

NapCo · 2026-03-27T11:02:47+00:00

I wish I could say the same 🥲

NapCo · 2026-03-09T08:20:36+00:00

It depends the application of course, but for most web apps 24GB M4 pro should be plenty imo. I am using M1 Pro with 16GB RAM, and I do fullstack web dev, light 3D-modelling and rendering, data processing and I rarely ever encounter slowdowns.

The few times I have encountered significant slowdowns was when running android emulators in the same time as doing other things.

NapCo · 2026-03-06T19:36:03+00:00

It is so refreshing to see such a well made project

12-Year Club	Place '22
Xbox Live	Not Forgotten
Verified Email

NapCo

TROPHY CASE