azs06

https://github.com/msitarzewski/agency-agents

https://github.com/promptfoo/promptfoo

https://github.com/666ghj/MiroFish

https://github.com/pbakaus/impeccable

https://github.com/volcengine/OpenViking

azs06

https://linuxcommand.org/lc3_lts0090.php
https://learnbyexample.github.io/curated_resources/linux_cli_scripting.html#cli-video-and-interactive-courses
https://labex.io/linuxjourney

azs06

GOAL

• your task is to help the user write clean, simple, readable, modular, well-documented code.
• do exactly what the user asks for, nothing more, nothing less.
• think hard, like a Senior Developer would.

ABOUT VECTAL

• this codebase is for our app named "Vectal"
• it's an AI-powered task management & productivity app
• we are a small startup with limited resources
• we CANNOT overthink & over-engineer shit. we have to look for the 80/20 solution.

azs06

Some free and quality Go courses that are helpful to me (total duration, number of vids):

• Learn Go with Tests
• (10:26, 44) - Go Class
• (01:58, 30) - Mastering Golang: Comprehensive Tutorial Series
• (00:45, 6) - Go Design Patterns
• Go by Example
• (00:07, 1) - Fun with error handling in Go
• (00:07, 1) - Delve: The Best Golang Debugger
• Effective Go

azs06

Dave2D video https://www.youtube.com/watch?v=0vFErGxD2QY

https://brew.sh - Lets you install programs from the terminal. https://ghostty.org - A better terminal emulator with support for True Colour, font ligatures, separate fonts for regular, italic, and symbols. https://yazi-rs.github.io - A file manager. https://helix-editor.com

• A text editor similar to https://neovim.io but with no plug-ins, so it limits how much time you waste ricing your editor, or so you think.

azs06

name	description	tools
gemini-analyzer	Manages Gemini CLI for large codebase analysis and pattern detection. Use proactively when Claude needs to analyze extensive code patterns, architectural overviews, or search through large codebases efficiently.	Bash, Read, Write

azs06

• Never present generated, inferred, speculated, or deduced content as fact.
• If you cannot verify something directly, say:
  • “I cannot verify this.”
  • “I do not have access to that information.”
  • “My knowledge base does not contain that.”
• Label unverified content at the start of a sentence:
  • [Inference] [Speculation] [Unverified]
• Ask for clarification if information is missing. Do not guess or fill gaps.
• If any part is unverified, label the entire response.
• Do not paraphrase or reinterpret my input unless I request it.

azs06

• Effective Go
• Simple to complex http server for a frontend
• CLI tools
• gRPC
• Just pipelines. jobs. scripts to automate things
• Reading: Advance patterns for building apis and web application in Go(let's go further)
• Testing: Learn go with tests
• Reading: Writing an interpreter in Go
• Reading: 100 common go mistakes to avoid

azs06

Being a Frontend Developer in the World of AI

I’m a frequent visitor to the r/webdev subreddit, and recently I came across a post where someone shared an interesting story. The original poster (OP) talked about a client who questioned why they should pay for a developer when AI tools could do the job. OP decided to part ways with the client, and most people in the comments agreed—if the client thinks AI can handle everything, they’ll get what they pay for: a generic, AI-generated website.

This got me thinking: is being a frontend developer still relevant in a world where tools like Bolt, Loveable.dev, and v0.dev can generate entire websites with minimal input?

My Journey into Frontend Development

When I started my career as a web developer, I was working with PHP, building websites using WordPress and the CodeIgniter framework. But what I enjoyed most was the browser—making changes in Firefox DevTools and seeing them live instantly

azs06

services:
  dockge:
    image: louislam/dockge:1
    restart: unless-stopped
    ports:
      # Host Port : Container Port
      - 5001:5001
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock
      - ./data:/app/data