Skip to main content

Planning

There are so much things that I want to write down but can't find out a time to do it. Lately my time management seem to be the worst ever. So I'll try to jot down first what in my head and hopefully I can write about it soon.

  • Understanding Django Content Type framework - I've been working on application that require me to use Django's Content Type framework (at least I decided to use contenttype to accomplish the task). Along the way I started to understand how Django implemented it. Content type concept not really unfamiliar to me since Drupal also using the concept for their Information Archictecture (IA). Django Content Type however seem much more flexible (compared to pre Drupal 7) and simpler to understand (compared to Drupal 7 similar concept).
  • Using Django's haystack app for search in your website/application - I decided to use haystack to provide search in another application I've developing and quite excited to see how simpler and fast I can get search working through haystack. I used whoosh for the search backend since the application not that big and will be used by just a number of users so performance not that important.
  • Look into buildbot or jenkins - I need to pick up a topic for our next company meetup in Pycon Sg next week. It can be any topic of my interest so long as it can still benefited the whole team in the presentation. I'm still not decided but topic on automated testing/continuous integration maybe what I'm heading up to.
  • Sqlalchemy - I used sqlalchemy in of my migration script and need to jot down how to get started quick plus some of the concept such as the Session that I started to understand. As everybody know, sqlalchemy is a very huge library and documentation span over few hundred pages I guess. Always lost in the documentation whenever I need to use it.

On another note, would be going to Pycon Sg next week. This would be my first experience with Pycon, hopefully can learn lot of things along the way.
Labels:

Comments

Post a Comment

Popular posts from this blog

PHP with docker

A friend asking about a PHP library and I decided to test whether that library is working. But I don't have PHP environment setup (we're Python shop btw). But thanks to docker, that's easy these days. docker run -it --tty --rm --volume $PWD:/app --user $(id -u):$(id -g) composer require google/apiclient:^2.0 Then we just need to create the script to run, still in the same directory:- include_once __DIR__ . '/vendor/autoload.php'; $GCSE_API_KEY = "nqwkoigrhe893utnih_gibberish_q2ihrgu9qjnr"; $GCSE_SEARCH_ENGINE_ID = "937592689593725455:msi299dkne4de"; $client = new Google_Client(); $client->setApplicationName("My_App"); $client->setDeveloperKey($GCSE_API_KEY); $service = new Google_Service_Customsearch($client); $optParams = array("cx"=>self::GCSE_SEARCH_ENGINE_ID); $results = $service->cse->listCse("lol cats", $optParams); And we can run that script again using docker:- docker run -it --...
1 comment
Read more

The first step in learning new programming language

Is to prepare the basic environment where you can freely try and experiment with the new language features and tools. Maybe because I'm not programmer type person, but more as tinkerer/builder, I hate learning the language syntax and stuff. For years after I started "learning" Python, I can't barely write any Python code. But I have manage to try lot of Python cool apps because I have that environment for me to experiment with all Python based applications. All these cool apps that get me hooked to the language, not the syntax or whatever language features. And in my experiences, this is one reason why people failed to get hooked on the new language they want to learn. They started learning with some of the language syntax and eventually get bored, because not so much interesting stuff there. In whatever programming language, it's the ecosystem that made it lively, and where the real work happened. Early this year, I made it a point to learn Go programmin...
Post a Comment
Read more

AI coding tools fragmentation

Executive Summary The discussion centers on a tweet by DHH (David Heinemeier Hansson) from January 10, 2026 , arguing against the fragmentation of AI coding tools. DHH contends that developers do not want a separate CLI for every model provider (e.g., Anthropic’s Claude Code, OpenAI’s tools). Instead, he advocates for a unified interface —specifically citing OpenCode —that allows developers to swap models within a single environment. The thread reveals a three-way tension in the developer community between convenience (unified tools), corporate control (walled gardens), and sovereignty (running local models). Key Discussion Themes 1. The Fatigue of Fragmentation The Problem: Developers are exhausted by "model choice fatigue" and the need to manage multiple CLIs. As Rob Zolkos noted, the fragmentation is absurd, leading some to write scripts just to manage their AI CLIs. The Desire: There is a strong consensus (DHH, Will McGugan, Mustafa Ergisi) that a "universal s...
Post a Comment
Read more