lindner
Joined 15 years ago
Karma
237
Submissions
38
Member since
Apr 6
Recent submissions
Comment · 1 year ago
Location: Burbank, California USA (Los Angeles Metro)
Remote: Open to hybrid, in-office, remote
Willing to relocate: High bar
Technologies: See https://www.linkedin.com/in/plindner/details/skills/ for full list. Golang, Typescript, Node, Java, Python, Pandas, Cloud, Databases, PostgreSQL, MySQL, Technical Leadership, Strategy, System Dynamics, Software Development Lifecycle, Agile/SCRUM/XP, Open Source, Roadmaps, Protocols, API Design, System Architecture, Decentralization, Blockchain (non crypto), Privacy Engineering, Mentoring, and much much more.
Résumé/CV: https://linkedin.com/in/plindner
Email: [email protected]
Github: https://github.com/lindner
Some highlights:
- Hands-on software engineering leader with a deep understanding of systems, from high-level architecture to low-level implementation.
- Proven ability to design and deliver elegant solutions to complex problems.
- Skilled in building and shipping high-volume services, pipelines, mobile apps, and ML models.
- Collaborative leader with experience in mentoring engineers and fostering strong teams.
- Dedicated and passionate about cultivating thriving developer communities and open-source projects.Comment · 2 years ago
Confirmed! I was a big metalhead \m/ and was responsible for all the Unix-y things and spent a lot of time maintaining the community.
Other hostnames we had from bands and SciFi
huskerdu / nirvana / supernova / arcwelder
hafnhaf (big bonus points if you can figure this one out, lol!)
ashpool / tessier / joeboy / countzero
Comment · 2 years ago
It's interesting that this article didn't mention Gopher, which was developed at the University of Minnesota. Jean Amour Polly would have definitely known about it, as back then the Gopher Team was all about creating Digital Libraries.
And Mark McCahill was a ardent Windsurfer, which resulted in this shirt, designed by his partner Wendy Jedeckila, way back in 1991!
https://www.computerhistory.org/collections/catalog/10274778...
Comment · 4 years ago
And here I am just waiting for the revival of Hyper-G :-D
https://www.researchgate.net/publication/220349551_The_Hyper...
Comment · 4 years ago
Also read about the saga of creating the Keyboardio 01:
https://www.kickstarter.com/projects/keyboardio/the-model-01...
They went through hell to get it manufactured. Shady companies, the whole nine yards!
Comment · 5 years ago
Wrong answer.. This effort does not scale. You want to make it such that facts added by anyone can be easily imported with a simple opt-in.
GDPR data portability could be expanded to include defined formats for export so that import can be done in an automated fashion.
Comment · 5 years ago
One thing that someone might consider is working with Data Portability laws to allow for export of user contributed data to corporate map platforms.
I'd like to add my Google Maps contributions to OSM
I'm a Level 7 local guide there and was an active user of MapMaker back in the day..
Comment · 5 years ago
hi5 (RIP) was originally a dating site and Pivoted to a Social Network.
Most profiles fake? I can say for sure that's not true. I maintained Postgres/Memcache/Graph DBs and the write load was real.
That said hi5 did engage in address book scraping and other dark patterns that you'd rather not see these days.
Fun fact: hi5 had a featured photos/profiles section based on popularity. Folks that ended up there deleted their account by 5x or more due to the unwanted attention their 'popular' photos garnered....
Comment · 5 years ago
So many thoughts about OpenSocial and the reference implementation, Shindig. I have it thank for my time at hi5, LinkedIn and then Google.
Some little known facts about OpenSocial
- Hangouts Apps (remember those?) were based on OpenSocial containers.
- OpenSocial powered the LinkedIn Apps Platform and Labs for a number of years. The team built Rails and Node apps and deployed on Joyent.
- Eric Schmidt gave a pep talk to the working group pre-launch and mentioned about how open always wins in the end...
- MySpace was concerned about the attack surface of 3p apps running in iframes. They toyed with the idea of requiring a webkit browser plugin to run apps (!). It did lead to Caja* as a project. https://en.wikipedia.org/wiki/Caja_project
- The work on OpenSocial led in small part to the Activity Streams spec which led to ActivityPub and thus the latest Fediverse protocols. I like to think of OpenSocial as dead, but a good organ donor.
Fun times...
Comment · 7 years ago
This is a lot of history crammed into an hour. Goes from the early code-breaking work and the development of Drum Memory at Engineering Research Associates.
ERA merged with Sperry/Univac/Remington and then begat Control Data, Cray, Unisys and many others.
Also tune in for some history of the Oregon Trail by Minnesota Educational Computing Consortium (MECC) and how that ties into the rise of Internet Gopher.
Oh and disclaimer: former Gopher Dude here.
Comment · 8 years ago
Still early days -- only 2300 artists on 296 labels so far; but growing. It fits somewhere between Soundcloud, Bandcamp and Spotify.
More at https://1500wordmtu.com/
- machine readable stuff below -
[ my public key: https://keybase.io/lindner; my proof: https://keybase.io/lindner/sigs/Syik9hOQR46EQ_k-5VBBTi0yvilo_HNcwenNfd2PyHE ]