I seem to be the only person (along with 3 others who were my cow-orkers) who ever used or heard of Teknicad , running on Tektronix Unix workstations and terminals :)
I seem to be the only person (along with 3 others who were my cow-orkers) who ever used or heard of Teknicad , running on Tektronix Unix workstations and terminals :)
What's more, you'll need an AC to play pc games. My home office room is ~6m2, and even the current 500w machine I have there can noticeably bump the temperatures under load.
For example, I'm in Scotland, and apart from one or two days, we've basically had a "year without a summer", with cooler than normal temps. ;)
XRDPConfigurator : https://github.com/scarygliders/XRDPConfigurator
- This is a GUI application I wrote 10 years ago. It even has a full WYSIWYG emulation of the xrdp login screen, which you can use to customize the look of it! All written in Python and PySide. It was originally meant to be a commercial product that I'd sell. Turns out there was no market for it and no one seems interested in it. Oh well!
X11RDP-o-Matic : https://github.com/scarygliders/X11RDP-o-Matic
- This was a shell script which automatically built and installed the Xrdp server on Debian based systems. Was quite popular back in the day but became kinda obsolete, which was good.
Polkit Explorer : https://github.com/scarygliders/Polkit-Explorer
- reads in a Policykit .policy file, parses its XML contents, and presents the information it contains, on a more human-readable GUI window. This seems to be useful to folks and someone even created an Arch Linux AUR for it, which was nice. I perhaps should try to update it so that it works with more modern versions of Python and PySide.
That last one. Hmmm. It's been a hot minute since I even thought about it, but someone recently created an issue to do with getting it running with python 3.12, so maybe I should have a peek at it once again...
The author of the article, I agree with. It's OK to abandon things. XRDPConfigurator is what I used to learn Python and Qt (with a naive goal of making income from it). That application took a year and bit of my time. I'm particularly proud of the Xrdp emulation, and the WYSIWYG editing of the Xrdp login screen layout! But spending any more time on it was wasted time. I open-sourced it after taking out all the nasty - and self-designed - registration (DRM) stuff I'd also had (which spoke to a central registration server and was Very Clever[tm] With No Chance Of Being Bypassed! ( /s ), and promptly just left it stewing in stasis. And no one was really interested in it, either. I guess Xrdp just isn't sexy enough for folks ;)
Users are not guinea pigs. They deserve better.
> Write it. Run it. It either does what it's supposed to or not. If it doesn't, find out why and fix it
That's called functional testing and that's actually testing. You are one step removed from actually formalising what you do and getting non regression testing for free. At that point, I think you are either arguing fot the sake of it and do actually realise that testing is important or somehow confuse testing with unit testing which is only a narrow subset of it.
And that’s why I never want to have to work with you on anything shipping to a user ever.
Don’t get me wrong, the field is riddled with people who think testing is beside them and wash their hand with the quality of what they ship and what they put their users through. That’s an issue to fix not a situation we should tolerate.
See, this is my point. It's not that testing is beside me, it's that my stuff gets tested anyway.
Here's the test: Does it fucking work or not?
You do that by running the thing. If it explodes, find out why and fix it. Job done. No thought or line of code was wasted in writing tests, all brain power was used to initially write a piece of code - which initially had a bug of course - and then said bug was fixed.
My code gets tested. By people using it. Or by me testing it as I write it ("does it fucking work").
There is really only one test.
You can choose to expend your brainpower and time on this planet writing code that will never actually be run by an end-user, or you can just write the fucking code that the end-user will run. That's how I work. Write it and run it. That's the test.
Test code written to test Useful Working Code is time wasted. It's like putting stabiliser wheels on bicycles - you're either gonna be stuck forever riding a bike with stabilisers, or you grow up and rip them off and have a few falls on the bike then become confident and competent enough to ride that bike without them. And have more freedom and time to experiment and go places you couldn't when they were put on.
So yeah. I definitely wouldn't work with people who like wasting my and their time on this Earth.
Write it. Run it. It either does what it's supposed to or not. If it doesn't, find out why and fix it. Or discover that your function/code abstraction/thought was shit in the first place then write it differently - oh and that's the worst part about writing code that tests the Code That Does The Work; say you discover that the function you're writing was a load of bollocks and needs to be highlighted and simply erased - there goes all that test code you spent brainpower and time, with it, too. And now you have to spend even more time writing new test code to test the Code That Actually Does Useful Work.
No thanks. And goodbye.
Same thing for the kernel, plus some versions are fully certified for various contexts so you can be sure fully formalised tests suites exists. And that’s on top of all the testing tools which are provided (Kunit, tests from user spaces, an array of dynamic and static testing tools).
But I would like to thank all the people here who think testing is useless for their attitude. You make my job easier while hiring.
That's fine.
I've never written a test in my life. Have my programs ever had bugs? Sure. But I sleep very well at night knowing that I spent all my brain power and time writing actual code that Does Useful Work rather than have wasted significant lengths of my time on this planet on writing test code to test the code that does the Useful Work.
You speak of attitude and smugly "thank" those who don't write tests as that acts as your hire-or-not filter. With an attitude like that, I'd 100% not work for anyone with that attitude anyway.
Their one Achilles Heel.
I think I still even have a book on Z80 assembly somewhere. Had a bright orange cover.
Deleted Comment
Am I the only one doubting that 30% of kids didn't see any porn by age 18? They're probably just uncomfortable admitting it, right?