trm42

KDE’s terminal app Konsole is great and really ITerm-like at least with my usage patterns.

This is actually quite important. After supporting my family and relatives with Linux and Windows for 15 years, I decided that I’ll only support them if they buy Macs. My time has become more precious to myself than it was without family and work. Some bought Macs and basically I may need to install some updates when visiting and point them to some software, nothing annoying or time consuming and no late-night helpdesk support calls.

Of course some relatives like my mom were cheapskates and did not buy Macs but then their problems are now somebody else’ problems. My personal life quality improved a lot after drawing the clear line.

And no, Macs are not completely problem-free but anecdatally a lot easier :)

Agreed, my take on the same subject although from 2 years old, but I would make the same decisions still (though maybe switch to AMD Ryzen mobo and CPU;-)

The Fractal Design Node 304 box is awesome. It's quiet, can host 6-7 disks although it doesn't have hotswap design. In practice opening the box and switching disks is not that common problem and the design makes the HDDs quieter than hotswap bays.

https://medium.com/@trm42/building-backup-server-for-photogr...

One of the things I’ve personally learned and been touting it ever since, is that it’s ok not to make perfect code in a hurry or when the real target is somewhere else, if the crude method solves the problem for long enough and is capsulated well enough and the intent of the crude solution is documented and it has tests. Documenting the intent is useful for the next programmer to understand, why the solution has been enough for the needs then and to quiet the DailyWtFs for the next guy poking the code.

By crude solution I mean half-hardcoded or not well generalized methods as the other cases are coming in a year or so. This is also a way to limit the scope and to achieve deadlines. What this means though, is that when new needs arise we need to go ba k and make them better later. Kind of managed techincal debt.

I can kind of relate to you. Not sure about the 10x but on the previous job I ended up working as team lead, pm, janitor, process developer, architecture guy, partially managing the infra, teaching the stuff to others etc. We had quite good team spirit and the people were generally awesome but there were management issues which broke our focus into pieces and we didn't get any real progress on the important stuff. In the end I didn't even realise how burnt-out I was (just trying to help and fix all the things for other devs so somebody could get something meaningful done) until some headhunter tried to recruit me and I started going through pros and cons. Switching to a job with a real focus has helped a lot and I learned a lot from that experience but happy to be somewhere else.

That company kind of imploded as there was about ten working when I left and now there's three guys left trying to get the work done. Luckily their focus has finally changed and tightened and there may be some good stuff brewing up so I'm cheering for them. Still missing working with those guys, though.

Good compilation! I’ve been shooting digital-only for the last 12 years and tried 35mm film last year. Now my medium format itch became so bad that I ended up buying a Hassy with the 80mm lens to learn new (or old?) things. The mechanical feel of a Hassy is awesome compared to new DSLRs and mirrorless. Everything is mechanically coupled and there’s nothing unnecessary. Just the focus, aperture and shutter speed settings on the lens, mirror lockup button and the actual shutter button and that’s it. This forces me to think about more and planning more before pressing the button.

Also, people have been talking here about developing the negatives itself to minimise the cost. Ended up making a kind of compromise: bought Epson v850 flatbed scanner and taking the film-rolls for development company to get the negatives. The scanners pays for itself really quickly as here one 120 film roll scanning costs 16 euros :D

In my experience this all boils to the fact that usually it's not the actual chosen technology stack but the missing craftmanship when making the stuff first time.

Then you either end up refactoring the whole setup for years (which usually is expensive, slows down the business development velocity) or rewriting it from scratch (or as a new implementation next to the old one).

If the original implementation would've been sanely made. Then making new features on top of it (or partial replacements or micro-services etc) wouldn't be that big issue. But usually these beasts are more like godzilla-level monoliths with bad architecture etc so it's probably easier to rewrite the whole thing.

Have you checked whether Vuescan or Silverfast supports your scanner model? They are quite amazing with supporting old hardware.

I really like white-on-black dark modes. They are somehow more pleasing than the other way round. There's a problem with all dark modes, though. If one is using laptop running on battery juice and needs to prolong the battery time, then conserving battery with low screen brightness makes reading the dark modes really hard. Hence I've ended up using multiple crucial apps like IDEs with black-on-white themes as they are more readable on dim laptop display. Annoying but better compromise than writing code without laptop, haha.

Now you’re comparing different sensor/negative sizes against each other. Usually ”full frame” (aka 135mm) diffraction starts to affect on smaller f-values (larger aperture) but on larger negative sizes the diffraction starts to be a problem on bigger F-numbers (smaller apertures). On 4x5 format something like f/22 and on 8x10 f/45.

It's quite different to work for your own company as much as possible as you (hopefully) gain really something big in return. If you're doing mandatory constant crunch for somebody else without extraordinary recompensation, then it's not a blessing but quite close to slavery.

Of course that kind of slavery can be a blessing in a country like China where the other options may be even worse...

This happens even in the best families. Yesterday Outlook365 informed me that there's a suspicious and blocked message coming from Github. And yep, that was the email confirmation I should've received from the real Github. I would assume that whitelisting bought services could be a thing within Microsoft...

I did use the new 2017 MBP for few months as my trusty, old type 2016 MBPr developed keyboard/trackpad connector issue after 2 years of constant use. The company I work for had to pay for changing the upper part of MBPr just because of that connector issue which rendered keyboard and trackpad completely broken.

After I got back to the old type keyboard, it feels a lot more mushy, has longer traveling distances, feels bulkier but is quieter.

The 2017 MBP has issues with dust and bread crumbs but otherwise it felt better after getting used to it and getting back to the old felt awkward. A little bit same the same with the Magic Touchbar and getting back to normal function key row.

Also the old MBPr feels heavy and awkward (but more robust built) compared to the new one, which is a lot more easier to carry aroung and pick up from a bag, but the robustness doesn't protect from stupid connector issues which may render the keyboard and trackpad useless...

I feel divided about the connector issue now that I got USB-C to USB-C and USB-C to USB-A cables + the mandatory USB-C hub with ethernet, memory card reader, HDMI and USB A ports. It's cool to be able to plug USB-A cables directly but then I miss the versatility of USB-C and the ease of having bunch of same connectors around the laptop and without minding what port to use with charger. On the other hand I miss the Magsafe 2 charging port which is a lot more robust as a connector compared to USB-C. The connector issue will fade away when the external devices you're using are getting USB-C ports as well. The connector issue is kind of "iMac supports only USB and Firewire instead of SCSI, LocalTalk, ADB etc) but these transition periods are annoying and frustrating.

Actually, that would be really, really awesome once you get used to Jetbrains' way of working. It's so unusual to be able to search for all the configuration, functionality, code and files in the same place.

The idea of your shell script and Makefile are the same. For me it doesn't matter which one is used but source code should have some kind of easily usable list of common development tasks. Otherwise developers are doing this and that and the easier ways of doing repeatable stuff are not getting propagated to everybody.

Although Laravel promotes ways of coding that keeps the code readable and more fun that the traditional Symfony/Java way (Like really long class namespaces and names that have redundant strings in them etc).

Laravel uses Symfony components but the APIs are a lot more fluent and more natural to use.

Been using first Text Wrangler for the last ~ten years. At some point as my main coding editor and later on as generic txt/md/csv editor. When they sunsetted Text Wrangler, ended up switching to BBEdit. Its trial version's free features are enough but recentely ended up buying the license just to show my support and appreciation. Awesome applications which can handle big files.

Actually, I'm kind of surprised Tumbler is trying to get rid of the all content instead of moving it to some separate "Porn Tumbler" instance. Sounds like there could be additional revenue stream coming out of that kind of stuff...

Funny, I was thinking the same. Although at the same the article put into words what I've been thinking about my photography hobby that has gotten too serious.

35. This has been going for a few years already but now I start to see some results: posing people for photography.

I know people which are quite good at it naturally, but at least for me it's a lot harder than learning a new programming language.

Learning something in which you're completely out of your comfort zone is even more rewarding.

Sounds kind of familiar. We started a mvp/prototype that was handed to one guy without that much of a planning. That guy is really good coder but not a product owner/manager, documentor or planner. You see where this is going? This was about empowering team members with responsibility.

Without a concrete plan it was really hard for the rest of us to help or say what's really important. And so began the feature creep for something that was suppose to be a quick prototype ended up being whole implementation which took half a year to get first somewhat working version.

The problems for us was we didn't know status of anything as it was always promised to be ready in 1-2 weeks but feature creep made it bigger and bigger. We tried to help with planning sessions etc but that wasn't enough to get the prototype back to track.

As everybody got a bit too rosy picture of its status, our salesguy started selling the idea forward. The timing seemed to be right etc but we didn't have even proper deml version as the one guy chugged on with his waterfall ad hoc dev style...

After our sales guy confirmed there's lot of demand for this proto and we got the first somewhat working version out and when the next steps were not really sane, we made an intervention which we felt we should've done four months earlier.

First we had a team discussion and decision what should we do together for the situation and then we created concrete plan for the next steps we felt we needed to get first sane version out. Then we made this public to everybody.

The funny thing with this intervention was that the guy who made the feature creep proto felt relieved after this. The biggrst reason why we were so reluctant to intervene was that this guy would get badly demotivated but he had chugged on so long he did get really stressed and frustrated with the situation but didn't know how to get help in the hole he had dug in.

So my advice is to talk out loud and make things visible. Timelines, features bot yet implemented etc. Maybe a gant timeline etc. These helped us to get the project to a sane point shere to continue.

Haven't had to use Zend but at least Symfony DI is really heavy to use with all the services.yamls and the javaisms it introduces.

DI can be heavy or it can be something mostly automagical like in Laravel. That's something I've enjoyed quite a bit. Basically it doesn't that much exist until you start needing special cases.

Quite a big part of the PHP community is gravitating towards Laravel and the new steam it introduced with OOB best practices and "let's try hard to avoid the Java-heaviness". Laravel seems to have quite nice balance between easy for new devs and bunch of powerful concepts when needed. Lots of basic problems solved OOB as well.

Sure, ZFS has lots of awesome features, but the point of loopback device lets you to attach and mount basically any disk image that has kernel or fuse drivers.

The reason why Apple's iOS App Store is so successful, is it's the only store accessible/allowed. On Mac Apple is also competing with Steam, which probably taxes quite a lot App Store game sales.

Read both of them + Unfinished Tales of Númenor and Middle-earth and few of the books in the History of Middle-Earth series compiled by Christopher.

I have to say I was disappointed in the Children of Hurin as it was once again repeating the same story with slight variations. After that I skipped the Beren and Luthien and will skip the new one as well. But my view may be distorted by the HoME series as they were full of different versions of the same stories.

Tried first The Old Reader but at some point of time switched to Inoreader for a reason I can't remember anymore but Inoreader has been really awesome all the way <3

About everybody else but Canon uses Sony sensors and fab. Canon still designs their own sensors and ATM they seem to be losing the sensor tech race to Sony.

Care to elaborate for people who are not familiar with it?

I would say Westerners are quite intrigued about what life was in Soviet Union in good and in bad as that world feels so different from us and the information has been limited and more propaganda than anything else. Been talking about it with my Estonian and Hungarian colleagues and wouldn't mind understanding more about it.

I have fond memories of the first PPC gen 8100/80. They really did amazing perf feats with the PPC CPUs. Apple managed to get lots of "faster than Pentium" ads out of those CPUs.

Also m68k IIci was really durable and upgradeable computer. They also lasted a lot longer than they were really needed <3

Been thinking of buys 6100/60 with PC Compatibility Card so I could have a retro gaming station with two different architectures.

Apple had bunch DOS/PC compatibility cards for handling best of the both worlds. The recent ones run even Windows 98...

At least Fuji and Olympus have realised the new model cycle is getting longer so they are releasing new firmware features until the replacing model is launched.

Canikon aren't doing new features in firmwares, seems more like bug fixes and Sony is somewhere inbetween at least with the A7-series...

Sony A7 series have also some kind of small apps you can buy and download from their store to your camera. Haven't seen that many apps there =(