summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorAndré Fincato <work@andrefincato.info>2022-09-20 11:56:35 +0200
committerAndré Fincato <work@andrefincato.info>2022-09-20 11:56:35 +0200
commitca91cebb1c5351a29d9577f17f36005d86262a56 (patch)
tree99da492e0e0534ad67ca6d0deae23dcac6997d0a
parente3c3aeeec0174b5cdbdbb8520fb5ebb32da30352 (diff)
worklog 2022-W02-W37: sketch out on projects
-rw-r--r--content/worklog/2022-W02-W37.txt42
1 files changed, 41 insertions, 1 deletions
diff --git a/content/worklog/2022-W02-W37.txt b/content/worklog/2022-W02-W37.txt
index 8403781..9cf5648 100644
--- a/content/worklog/2022-W02-W37.txt
+++ b/content/worklog/2022-W02-W37.txt
@@ -11,4 +11,44 @@ smaller things happen in between, primarily some existing projects in maintenace
[^work-org-tools]: curiosly, i went to use a small script i put together to check when i updated the work file of each project, and while i got back some info i also got reminded that during summer i changed how i use those work files (the system has changed) and am not sure how much is accidentally being left out of it.
-writing this entry feels difficult, as many processes have endend. i endeded them. at some point this action began to feel alien to my normal array of operations, as more projects took on a long, streched out, forever trend. this year i put an end time on them, and it's a great feeling. as it is re-discovering the "taste" of this action.
+writing this entry feels difficult, as many processes have endend. i endeded them. at some point this action began to feel alien to my normal array of operations, as more projects took on a long, streched out, forever trend. this year i put an end time on them, and it's a great feeling. as it is re-discovering the "taste" of this action, is this an example of manifesting and experiencing agency?
+
+## dae.wiki
+
+newest final release was planned to be mid february 2022. a mix of problems pushed it further of a few weeks into early March. testing began from the school side and bugs began to be reported. a possible problem (up to that point only a big consideration) at last took shape and while it made me die i already looked into it at the very beginning of the process 3 years ago and i knew how it could be solved. due to this last point, i asked more time (3 weeks) after the agreed upon delivery was finished. the list of bug report grew and began to mix with wishes, last minute disagreement and overall misunderstandings of how things should work on the website. *after 3 years*.
+
+i fixed all the bugs in the list and discussed those point which were new request (see disagreements and misunderstandings). spent the summer to implement many of those new points and integrate everything into a Docker environment. wrote setup scripts and documentation, added more code to make the initial setup smoother.
+
+in mid august i uploaded both the dae.wiki repo as well as the dae-infra Docker code to a new account handled by the school. i told my delivery was finished, ready with all info necessary to run it. sent the last big invoice for the work done in the previous 8 months — as the delivery stretched from March to August.
+
+as of the time of writing (2022-09-20), the same endless cycle of acting completely lost, with no idea of how to run the website, how to manage "the last part", etc from the side of the school has taken place again. i made it clear my time is up at every attemp to flip around the story of whom responsibility is for this and that. not moving from my position.
+
+## job application
+
+in early spring i applied for a job application at a US company. it was for a front-end position at a p2p company building a new computer-stack from scratch. they gave me a bounty to work on, eg a real github issue, for the span of 3 days and got paid for it. did an interview before and after it.
+
+ultimately did not the job because i am not a good fit as i never worked in a medium-big team and have no direct experience with particular code framework. both reasons reminded me why i like freelancing!
+
+## buycloud
+
+this year i finished to work on the urcloud part of buycloud, which is the archive of the project. the main buycloud website lets you buy a cloud in the context of an exhibition. all the bought clouds are displayed in the archive website.
+
+this website also enables the second part of the buying process, which is to put the clouds in a pacman-like game environment and make the bigger cloud eats the smaller ones. while at last this feature is not enabled in the current online website, it's there. besides, clouds roam on the sky and exit-enter the "sky" space as in pacman.
+
+an index list of all bought clouds — with info of whom, when, and cloud features — is available as well.
+
+the project took a longer time due to the initial confusing process of collaborating together with the artist. confusing as in not having a shared language to talk about things and express ideas, as well in part having contrasting ideas. all in all a very project! i would have enjoyed exploring even more the game element of the website, but it was a good intro nonetheless.
+
+on the other side, it was a python-based project after a few years of doing nothing like that, and i learned that python slows down small VPSs with few resources. while using it was a good experience, i began to dislike that it requires a lot of computer resources to not slow down the whole machine. well!
+
+## TWLA
+
+another stretched out project that i completed was TWLA. roughly it was concluded around February-March i believe, and then smaller patches of work were performed in the months following.
+
+i liked i had the chance to look up and use git bundle to share the repo of the project, and uploaded it online at a public URL (on my VPS). this was necessary due to another institution mis-management of departments. originally we agreed i would have uploaded the git repo on a hosting service, but 3 months into the project a new ITC team took over the previous one and all of a sudden "no one knew anything". ah!
+
+## smaller bits
+
+---
+
+