How can I help you?

Ehh, Probably not... Though I could single-handedly design/engineer, build and maintain one.

Yes I'm serious, and don't call me Shirley.
Every single facet, from the literal ground; up to custom software. Even hosting the VPS for remote VPN connection and control/monitoring of smart home automation systems. :)

Of course I'm not likely to do all that, because it's alot of work for one person over a very long time. Even on a tiny home project; Speaking from experience, as I was actually crazy enough to do such a thing once upon a time.

That's a general summary of my knowledge/experience.

Basically anything in IT, and the construction field I have either done or am more than capable of doing. That's right, I have a fairly extensive background in both IT (computers) and residential/commercial construction (Fun facts not found on my resume: In the late 80's, I often worked with my Dad who was a general contractor at the time, I also interned with an Architect in the early 90's). Even have a bit of background in the industrial construction field (chemical processing, oil/water tanks), at least on the design/engineering/CAD side.
Some other fun facts: I've also done a fair share of shadetree mechanic work, been a DJ, karaoke host, run live sound, and been in a couple bands.
I'm a veritable wealth of practical knowledge and experience.

So a better question might be; What can't I do?

Windows.

Well, actually I can do that. The building kind or the software. Prefer not to though.

Mostly interested in Linux based projects, Open Source Marine electronics (OpenPlotter hardware/software), ESP32/IoT firmware and related Home Automation systems.
I'd rather be sailing though and since my sailboat is home, remote projects are preferred. Onsite availability is generally limited unless convenient to dock/anchor; preferably in the southeast coastal US or Caribbean. Travel costs can be found on the Rates Page.
On that note... Need a Delivery Captain or any other marine services?

I invested a lot of time and money in order to minimize expenses and manage surviving on very little revenue. Alas, it still costs money to live. However, the result of such investment is that at my standard rates I should only have to work a day or two a week, or about one week per month. Of course, after overhead that only works out to about poverty level income, but it's at least enough to not starve.
Not offering a six digit salary remote position, or equivalent contract gig (at the typical going rate for my qualifications)? Then consider a donation to support open-source product development. Or if it makes you feel better, make it a consulting engagement...send an email, ask some questions, get some answers/advice/recommendations/etc., and receive an invoice. BTW, I currently have a consulting special on "How to NOT live paycheck to paycheck on $100k+/yr".

TLDR; Here's the single page corporate rat-race highlights resume.

All the juicy IT keywords that HR bots and NPC's like to see can be found below. Keyword lists of software/technologies are generally irrelevant for those of us able to work with practically any software and system across the vast majority of the IT field. For professional construction related experience refer to my resume.

Slackware Linux has been my OS of choice since the 90's when everyone was compiling kernels for their Xwindows desktop...had NetWare and Redhat servers running at home... ran their own Quake servers across dialup connections and occasionally lugged their gaming tower to the office after hours for use of the T1 connection to play deathmatches...

What's that you say? It wasn't everyone that did that? hmm.. well that's interesting...

Since the late 80's I've used/worked on Dos, Amiga, Unix, Vax, Aix, HPUX, BSD, Netware, Linux (Slackware, RedHat, Mandrake, Suse, Debian, Ubuntu, Dd-wrt, OpenWRT, and quite a few others including LinuxFromScratch), Cisco and other routing/switching/'black box' devices, some Mac's and even Windows systems which I hear people still actually use for some odd reason. Personally, I couldn't find a reason to use any Microsoft products since a certain contract that stupidly required it (to support hardware which ran on Linux-based firmware no less) in the early 2000's. Appears that it hasn't changed much - still a maintenance headache and security nightmare that requires more resources to keep running than it's worth. Maybe more people use AutoCad (or some other proprietary product stuck in that dev cycle) now then back when I did throughout the 90's, IDK.
Still running Slackware as my desktop, though running Debian and derivatives on more devices (servers, SBC's, phone, etc.); and running more services in docker stacks/containers over the past few years.

I started programming in BASIC on a Tandy 1000 IIRC, or was it a Sinclair ZX81? Learned AutoLISP and C/C++ around 1990. At some point, to some degree or another (incidental to job/contract, specific programming projects, personal interests), have also worked on code in VB (the classic variety), perl(and miniperl), python, java, php and probably a few others I can't recall now. I guess batch files, bash scripting, awk/sed/regex, et. al. would fall under the programming category as well. I have a couple, now old, docker projects on github. Github isn't what it used to be, could have something to do with Microsoft buying it. Maybe at some point I'll make my gitea server public. Til then [if/when I bother to] I clone repos to Codeberg. The bms2sk project can be found there. It's a C program that reads data from a JBD BMS (a common LifePo4 Battery Management System) via bluetooth and sends the json Delta to SignalK.

In the 90's I worked with data in FilemakerPro, Access, Oracle, Informix, Delphi, mysql, crystal reports... More recently, mariadb and postgres. Have run redis, solr, etc. as services in docker fwiw. I guess Grafana would fall into the db category for commonly being integrated with InfluxDB and Telegraf.
How about some message queuing/protocol stuff that I run at home/boat - Mqtt, signalk, 1wire, nmea... or we could just move on to network protocols. Token ring, ethernet, IPX, IP... Like an onion, there's layers...Well nevermind, I forgot how to rattle off the OSI model a long time ago and there's a website or two somewhere for reference when it actually matters... Got the hurricane electric ipv6 certification when ip6 started rollout. I've setup/admin'ed my own and numerous others' servers for file, print, app, web, mail, ftp, ssh, DNS, DHCP, etc. etc., again since the 90's.

And then there's the security of all this stuff - user permissions, firewall, vpn, ids, WAF, proxies... there may exist stories of questionable hacking activity in the heyday of AOL, keystroke loggers, recording and analyzing packet captures, elevating privileges and creating hidden backdoor admin accounts in Netware... first generation hacker stuff [*- page lost, The Jargon File is an interesting (or mind-numbingly boring) read to refer to as a substitute] ... On that note, I'm getting bored with this, though before I forget, and since I'm on the subject... penetration testing services are also available. And in closing: kudos to you if you actually read all of this.

* - Some links may be missing. Many webpages, a couple databases and all Hubzilla posts were lost when the previous web/VPS provider's entire infrastructure just disappeared from the internet without warning. A harsh reminder that online backup options are no good if those servers suddenly go away. Offline backups are important. If you need a data backup plan, get in touch for a custom solution.