Skip to main content

Standing desk review: Actiforce

I am too jumping on the standing desk bandwagon. I first gave it a try using a support on the table and once I felt the benefit (I felt more creative and focused) I decided to make the move. After all you can still use a standing desk as a normal desk.

I first tried buying one from the usual, US-based, suspects but it can be hard to figure out the cost of shipping and then I'd also have to manage import which has never been too fun the rare times I had to (fyi: you must send a bloody fax. In 2017!).

So I looked around and found some good looking stuff from Italian manifacturers, but the prices are omg!

So I searched Amazon and of course, there it was. It is from a German vendor who is in fact reselling products from Actiforce. I know people using Actiforce and they are happy with it so I bought it.


Bear in mind that this will only get you the frame. The rest (cable mgmt, monitor arm, casters, mat) you need to figure out yourself. The price is IMHO cheap, on par with Ikea, which I had already discarded because of the bad reviews. I had a chance to try the Bekant desk at an Ikea store and I don't remember it feeling too bad, but ultimately I was scared away by the reviews.
The final result. Cable mgmt? not yet

The frame arrived on the second day in a tight, but heavy, package. Heavy is good, right?

Assembly was easy, it took probably an hour. The manual is only in German with ridiculous pictures that you can't make anything out of, but I managed.
Good quality tools are included.

Once it's assembled you screw in your own top and then start typing away. The motors are maybe a *little* noisy, but I don't care.

Stability is excellent: the darn thing won't move, wobble or give way even when pushing intentionally. When it starts moving rising or lowering it does so gracefully, so it should not spill your coffee :-)

At the moment I am using a cheap 125x60 cm top, but I'm moving to a 75x130 soon as I feel 60 cm is not deep enough.

Absolutely recommended and this is not a sponsered review.
Labels:

Comments

Post a Comment

Popular posts from this blog

Mirth: recover space when mirthdb grows out of control

I was recently asked to recover a mirth instance whose embedded database had grown to fill all available space so this is just a note-to-self kind of post. Btw: the recovery, depending on db size and disk speed, is going to take long. The problem A 1.8 Mirth Connect instance was started, then forgotten (well neglected, actually). The user also forgot to setup pruning so the messages filled the embedded Derby database until it grew to fill all the available space on the disk. The SO is linux. The solution First of all: free some disk space so that the database can be started in embedded mode from the cli. You can also copy the whole mirth install to another server if you cannot free space. Depending on db size you will need a corresponding amount of space: in my case a 5GB db required around 2GB to start, process logs and then store the temp files during shrinking. Then open a shell as the user that mirth runs as (you're not running it as root, are you?) and cd in
Post a Comment
Read more

From 0 to ZFS replication in 5m with syncoid

The ZFS filesystem has many features that once you try them you can never go back. One of the lesser known is probably the support for replicating a zfs filesystem by sending the changes over the network with zfs send/receive. Technically the filesystem changes don't even need to be sent over a network: you could as well dump them on a removable disk, then receive  from the same removable disk.
1 comment
Read more

How to automatically import a ZFS pool built on top of iSCSI devices with systemd

When using ZFS on top of iSCSI devices one needs to deal with the fact that iSCSI devices usually appear late in the boot process. ZFS on the other hand is loaded early and the iSCSI devices are not present at the time ZFS scans available devices for pools to import. This means that not all ZFS pools might be imported after the system has completed boot, even if the underlying devices are present and functional. A quick and dirty solution would be to run  zpool import <poolname> after boot, either manually or from cron. A better, more elegant solution is instead to hook into systemd events and trigger zpool import as soon as the devices are created.
Post a Comment
Read more