2,270 karma · joined May 22, 2009
You can find more info about me on my website https://davesnider.com
Can contact me dave.snider [at] gmail.com
The sad reality is the Internet publishing is dead and as a business that business is nearly impossible to operate if you have any moral compass. In its place we have various traffic to ad scams and a creator economy built on the backs of a couple large platforms like Twitch, Reddit and YouTube. While the later option seems freeing for some creators, the reality is that soon those too will become hard to make a living from as those large platforms start slowly squeezing their creator class outside of a couple few who play nice. It's only slightly better than the journalism field because at least some of the personalities can shoot over to Patreon and work directly with their audience (albeit still tied to another large platforms).
I love this space, and it's where I grew up as a kid in the late 90s. I love community websites where I can engage with some experts. With video though, it's extremely hard to run independently. Hosting video for Giant Bomb in 2008-2012 meant home rolling our own streaming service, chat service and edge-based video platform. We had an all-star engineering team. We had one of the largest podcasts in the world and the hosting bills were killing us. Getting an audience with good content was easy. Monetizing it was very difficult. That's only continued over the years as I've seen various companies buy Giant Bomb (CBS, then RV, now Fandom) looking to pick up a premium brand that they could use to mask the giant volume of dead, but trafficked content they had in the background. The shill back then was was to sell Giant Bomb or GameSpot ads, but serve it on GameFaqs or Comic Vine (which had huge traffic at low cost). Various SEO tricks were pulled to hide traffic. For example, Comic Vine moved to a Gamespot subdomain to make this seem more legitimate. I anticipate similar dark patterns every time these sites are resold to cheaper owners. Likely, these brands will be used to promote a mountain of google-driven traffic in other properties.
The question I haven't been able to solve:
How can good content be monetized in a way that allows it to remain independent and not succumb to warping its content to feed that monetization? How can it be audience driven instead? Is such a thing even possible? Right now good monetization strategies beget bad content. There's got to be a better way than cobbling together five platforms under a Patreon account, giving all of them 10-50% along the way.
"There is nothing terribly complex about this algorithm — an understanding of basic trig is all that is required."
"After a 30-year hiatus, back to writing shareware, ha ha."
I LOVE seeing stuff like this. Keep hacking till the lights go out.
Window manager? I3... heh, let's build a bunch of scripts. Vim? Well... man, that's a whole ecosystem of tooling I an hack together and write against.
I do this as a designer. I'm actually not a fantastic programmer, I just like the flexibility of building tools that are specific to me. My entire desktop feels like a love letter to building cool things the way I want.
I'm running an arch setup, and because it's fairly barebones I needed to learn about temp / power control regulators like TLP.
It's one of my favorite pieces of software from the past decade.
Also, they have a nice CLI. I'm sure getting some of these features there is only a matter of time.
What if you walked into a bar and everyone was pre-ranked on your phone?
What if news was replaced with streamers, and every friend group had a person who was streaming non-stop?
What if economy and finance stopped being about making capital and instead became about managing debt, at both the micro and macro level?
What do relationships look like in that world?
[0]: https://www.amazon.com/Super-Sad-True-Love-Story-ebook/dp/B0...
https://github.com/jarun/googler
Screenshot of Googler in action when it's nice and clean
I used to run some popular publishing websites around entertainment: gaming, movies, tech...etc.
I talked to our first users entirely through our message boards, which had PM systems built in. The regulars were there almost every day and I got to know them fairly well. We'd talk daily and I used the message board to show off new designs I was working on. Eventually they started their own fan podcast (this was 2008 or so mind you) and I'd show up as a guest to support their love of the websites. They'd be surprised I'd show up. Me? I was surprised they went to so much trouble to support my site.
Eventually we just hired a bunch of these early users at interns. One we hired permanently, and others we helped get jobs within the gaming industry. I don't see them that often in person anymore (I've since moved) but I'm happy to see them with their own thriving careers and consider a couple of them friends.
I sometimes wonder if the move away from message boards and towards larger communities like Reddit and Twitter would have allowed for this kind of clubhouse atmosphere. It's one of the bits of the old Internet I occasionally miss.
Elastic is looking for someone to lead their docs team. You'd get to work on some of the most viewed technical docs in the world.
https://jobs.elastic.co/jobs/kibana/distributed-amer/kibana-...
Anyways, the way we got our early users was nontraditional. We went in person to car shows, took pictures of the cars, making sure one of them was with a polaroid camera. We then handed the Polaroid to the owner of the car and asked if we could feature their car on our website. If they said yes, we wrote out a email/pass on the back of the polaroid and then went home and set up their account. This seeded our original social graph.
Harder to do these days, but don't forget about your legs. It's a lot easier to convince people in person than over a rote email.
We got on Techcrunch as well, but it didn't help nearly as much. Techcrunch is mostly good for the inner industry[0]
[0]: https://techcrunch.com/2006/06/11/cnet-veterans-launch-boomp...
First, I was already a vim user for 8 years, so I was used to config files and the terminal. I moved primarily after watching some videos about I3 / awesome WM and browsing the /r/unixporn subreddit. Primarily I liked the idea of designing my own OS from scratch, and the idea of being able to change ANYTHING was really intriguing to me.
I guess it's important to note that as a designer this wouldn't have been possible without tools like Figma and Framer being web based. Put bluntly, Linux native design tooling isn't up to par with what I had on a mac, and without Figma I wouldn't have been able to move over full-time. It's also important to mention that while I classify myself as a designer, I design 90% of the time in code, writing React + CSS. I realize I'm a little different and this likely sways some of my feelings towards linux.
In short, I've really enjoyed the switch. The window management alone has been reason enough. Being able to navigate my windows with key commands, and generally lay things out the way I see fit between polybar + i3 has been fantastic. Don't like a certain shadow? Change it with picom. Don't like seeing title bars on your windows? Change a config. I'm also a designer that believes in heavy focus (think tab focus in a browser) so every window gets a thick focus border. Everything is matched to a color-scheme that I like, and I mean everything. I don't feel like I'm using Linux so much as I've used Linux to build Dave OS.
I was able to migrate nearly $500 of annual tooling to home-made scripts and services that I run through GCP. For example. I used to use cloud app for screenshot / movie snippets. Any designer will tell you something like that is their bread and butter... "hey what do you think of this?". I moved it to Peek / Flameshot + a 40-line bash script that watches a folder and uploads it to a gcp bucket. It took me a half day of learning. At the end of it I had a funny realization... why have I been paying for these simple services for years and complaining about features they didn't have? Now I just add the features.
Performance is hit and miss. Everything I used to do in the terminal (which is where I spend most of my time) feels faster. In general, I had to drop apps and move command line. This was fun! I moved to buku for bookmarks, taskwarrior for todo lists...etc. What I loved about this was it forced me to engage more in the OSS community. I already do mostly OSS stuff for work, but I was in my bubble. Linux forced me out, and I found myself talking a bit more on Github, asking questions and the like. This was the thing that I've ended up loving. In general I've been amazed at the amount of support I've gotten from maintainers by just saying "Hey, I'm a designer, I'm not so knowledgeable about the guts of this code, can you help me out"?
Slack and zoom are slow. They are pretty resource intensive apps and weren't exactly speed kings on my mac, but they do feel noticibly worse on Linux. I'm hoping this is due to my hardware, but I suspect the apps just aren't as considered in Linux. I've really enjoyed AUR / pacman for package management and it feels like brew, but for everything. The one thing I think Linux is missing is a good calendar application that syncs with gcal. The terminal based ones are a little overweight and underdesigned, and I can't find a GUI one I like.
Anyways, I'll probably do a formal blog writeup at some point, and more importantly make some videos of my setup, since it's probably interesting for folks to see how a designer uses Linux, but I thought it'd be worth a quick post to let others know its possible.
Hardware wise I had no trouble with my mac, mostly because I already had my own custom keyboards and the like, but I'm excited about the new Thinkpad on the way more for it's power-to-price.
For the deep history I'm a pinboard user and bookmark at least a dozen things daily with tags.
1. The omnibar completion isn't as good. Chrome figures out where I go pretty regularly, and autocompletes extremely well based upon habits. 2. The dev tools aren't as good. I mostly work in the frontend, and simple things like how you write css overwrites with tab completion is just not as good in Firefox. 3. I often run with lots of tabs. Although firefox lets you make tabs smaller, it's default method of "scrolling" tabs isn't as nice as chrome infinite method.
It doesn't help that I pair this yearly experiment with DDG as my search. With that pairing I often run into autocompletion / omnibar issues and find myself just banging !g to get myself out of it.
I really would like to switch, but the gap is too much for my daily tooling. I say this as someone who recently switched to Linux from OSX and really ran into no issues outside of having to spend a week setting thing up how I liked.
Some of my favs
The untold story of Astroneer's development https://www.youtube.com/watch?v=tfUjl4owxTQ
Doom: To hell and back https://www.youtube.com/watch?v=PS6SBnccxMA
For palette generation, we do a lot of our work with tools like chroma.js[1] which can help with some colorblind math.
[0]: https://github.com/elastic/eui/blob/master/src/global_stylin...
[1]: https://gka.github.io/palettes/#/9|s|00429d,96ffea,ffffe0|ff...
- We make sure tab order and keyboard control is a equal level citizen.
- All our colors and palettes are backed by math, both for contrast and for color blind qualitative comparison.
- We build using semantic HTML and try to to avoid abstracting things like input controls and labels with too much magic.
- We test and build for screen reader support at the component level and then provide helpers for navigation. Usually, given the complexity, this means a decent mix of native html, aria, and hidden text to make things read correctly.
We do have some automated axe testing, but in all honesty, axes only gets the surface level spec and might cover 30% of what you need. The rest is really hand touched, backed by pretty strict review.
In general the bigger frameworks like ours are getting better at this stuff, but it's still fairly poorly considered in the industry overall. The specs are pretty verbose and poorly standardized against browsers. This make it very much like building a traditional visual frontend during the browser wars of the 2000s (I was there!).
Third party audits are normally done on the products themselves (in our case Kibana), not the framework itself. This ends up being an indirect method of auditing the framework though.
All our work is open source and documented. If you have any questions, please ask away. I love this stuff and web UI has been a 20-year passion for me.
This is by far the best way to get recognized at those companies that are hiring. I will admit it's a long sell, but it has fairly predictable results if you're steady with your contributions.
As a former college drop-out that made it into the industry this is the route I would have taken were I joining the workforce today when I was younger. Great way to learn on something real and get your foot in the door.
Note too this is possible for designers as well. There are lots of design libs floating around and contributions to those repos is so rare it's very easy to get stand out.