It's open-source if you're curious about anything! Though it's quite messy. https://github.com/joshwcomeau/blog
2,790 karma · joined February 14, 2016
It's open-source if you're curious about anything! Though it's quite messy. https://github.com/joshwcomeau/blog
A few of them are OneDrop, including a Kuntosh near the front, and a Summit a bit further back :D
Unsolicited collection shot: https://i.imgur.com/H1x5k9Y.jpg
(Also it’s pretty harsh to say that it takes “little talent” to become an SEO expert. Like all industries, there are charlatans selling snake oil, but there are experts who have invested a lot of time in developing their skill sets, and it’s not nice to be so dismissive.)
As for “not really open-source”, you’re right. I’m clearer in the FAQ on tinkersynth.com; it’s not “OSS” in the conventional sense. I just didn’t know how else to phrase it in the limited HN title.
The thing I don’t want is people inverting the colors, or cropping it, and calling it a unique work. I’ve already had people trying to sell Tinkersynth works they hadn’t paid for in the old model, and I’ve heard some horror stories from other creative coders.
As to whether it’s possible to copyright the output of a tool... that’s a good question! I’m not actually sure either. I don’t expect any real issues to emerge. The licence change is largely around guarding the most obvious cases, I won’t even try to make a fuss in any other cases.
Something about HN gives people license to air all of their nitpick grievances, and make it seem like SUcH A bIg DEaL OmG WorST LiBRarY EVArR!11
To the authors, maintainers, and contributors: Thank you for making the ecosystem better. It makes our work easier.
This project was actually meant to be for plotter drawings originally, and the SVGs it produces are plotter-friendly (all the occlusion is done mathematically, not using fills or masks).
The reason is that the experience really only works when you can see the art while you're tweaking a parameter, and there was no way to fit both the art and the controls on a phone screen at once. I had them stacked, and scrolling up to see what a control did was a miserable experience.
I don't really have many plans to keep working on this machine, but I do hope to add new machines (with different controls, and different possible outputs), so I'll definitely keep that in mind :)
I've been thinking of it a different way, though. The option exists for people who want to manage the printing themselves, and it's a much more economical version.
The fine-art prints on my project start at $99, and while the profit on that varies by where it's shipping to, it's always more than 20 bucks. It doesn't cost $80 to produce and ship a 12" x 18" print.
Put another way, you're not paying for an image download, you're paying for the creative energy (not to mention time) that went into producing this tool.
That said, you're not the first person to bring this up, so clearly the messaging could use some work. I've lowered the price to $5 while I figure that out.
Fun fact: While any combination is possible from the "randomize" button, it uses weighting to try and come up with pleasant/interesting combos more often than not. I'm quite pleased with the results.
> Medium, if you ever read this: I don't appreciate being lied to.
> To top it off, they simply ignored the two (very polite) follow-up emails I sent them.
My guess is that Medium has an admin tool for customer-service agents to use, and that tool was likely updated and no longer allows for canonical link updating. As companies mature, the freedom of CS staff tends to diminish, as mistakes are made or privileges are abused.
The email reads "there is no way for you (or us) to set it to something else". I'm guessing "us" refers to the customer-service team, and not Medium as an organization.
In other words, I don't believe the author was lied to.
As for not getting replies, I'm shocked to learn Medium even has an open support email! I'd have to see the author's followups to know if they warranted a reply, but given that the author adamantly believes that deception is at play, it's possible that the emails aren't as polite as the author believes.
I think someone without experience training a model to high-accuracy might struggle at a startup where they're the first hire in the department, but at a larger company, presumably there are senior folks to help newcomers along. I think having motivation is a much better signal, and you need to be motivated to develop a side-project of significant magnitude.
Easy - spend the 45 minutes that you had allotted for whiteboard challenges.
> how can I be sure that you're the one who wrote that code?
You can't be, if the Github account has a single repo with a single commit. But impressive OSS has a history of commits, maybe even a community working with the applicant.
As a random example, do you really think it would be possible for someone to fake an account like this? https://github.com/pedronauck
Even if someone went through the trouble to clone someone else's repo, modify all the commit messages to re-attribute them, and modify the code and commit messages enough to make it not obvious plagiarism, do you really think they could bullshit their way through a quick conversation about the code? Spend 20 minutes digging into it, and then ask pertinent questions about decisions made in the architecture. It'll become clear if this person is the author.
It's theoretically possible that someone could put in all the work to pull off a convincing fraud, but do you really think that's likely?
> How do I know that your previous employers and clients weren't all bozos or that you didn't slack off and let your teammates do all the work?
It's true that there is no perfect signal here, but the odds of this being true are not 50/50. It's not 100% accurate, but having references and employment history is better than nothing.
---
To be clear, I don't think OSS inspection is perfect as a hiring tool - it biases towards folks with the privilege to spend their free time working on passion projects - and I'd object to it being the sole determining factor. But I think the signal is far stronger than it is from whiteboarding, where the false negative rate is super high (I doubt most competent programmers would accurately showcase their skill in this environment).
There is no perfect hiring practice, but to immediately disregard anything that has even a negligible potential for fraud feels a bit silly to me.
My local market (Montreal, Quebec, Canada) _severely_ underpays. It's common for people with 5+ years' experience to be making under 60k CAD (50k USD), if not way less. Because of that, many of the city's best devs either work remotely, or they move to Toronto, or New York, or the Bay Area.
When you base your salary calculations on local market rates, in very-low-market-rate areas, you're looking at an artificially lowered pool. I'm not surprised people balk when they find out how low you pay, because in their mind they aren't competing with local onsite developers. That isn't their market.
Also, there are many benefits to working onsite that don't appear to be factored into your calculations. Not all remote workers can work comfortably out of the home, and so there are office rental costs. Many onsite jobs provide things like free lunches, as well. It's possible these things are factored in; if so, it might be worth mentioning them here: https://about.gitlab.com/handbook/benefits/
EDIT: Removed a complaint about #3, as I saw from another comment that I misunderstood it. I still disagree with the premise - if I was unhappy at my current job, there are plenty of other remote companies that pay well, and even if there weren't, I'd gladly take a pay cut to do more fulfilling work - but it doesn't strike me as condescending anymore. Just ill-informed.
The Dow Jones is higher today than it was last Tuesday. It went up for a few days, and now it's going down by a bit.
It's still 1300 points higher than it was 2 weeks ago. and 500 points higher than it was a year ago.
A few stocks are doing poorly, others are doing well. Same thing as any other day, seems like?
Disclaimer: I'm not a stocks person, I'm just reading the graphs. So maybe there is something significant that a layperson doesn't understand... but it certainly seems disingenuous to make it seem like there's a huge problem with the Dow.
Also, I am cisgendered, and it's important to me. So it's more than 1% of the population. Or do you believe that you have to be a member of a group to be bothered by things that affect them?
Also, I haven't seen a lot of companies saying "Well, Angular is working great for us, but React is hot and trendy so let's rewrite the current UI in it". Rather, I think UI framework switches happen for two reasons:
- They've accumulated so much technical debt with their existing solution that progress has slowed to a crawl, developer morale is really low, etc. A migration strategy can be found that doesn't have such an upfront cost, and will dramatically improve velocity as features are converted.
- The design is totally changing, or the product is being rethought, and so it's not an invisible code rewrite, it's essentially building a new product.
I think in both of these cases, it's a good use of developer time.
Really touching story, great character development, and some interesting questions about AI and sentience.
https://www.goodreads.com/book/show/22733729-the-long-way-to...