I could have been more constructive her in fairness! It's not so much the language as the presentation of the options in that specific question - they're kind of presented as a scale but the middle options deals with a different variable to the outer ones - western vs non-western and traditional vs modern. It might be worth breaking these kinds of questions into Likert scaled for more tightly defined variables.
It also seems like because of this pattern a lot of the tools wouldn't actually be that useful in the field. I've played around with a few now that 1. it was almost impossible to test and debug behavior because you can't tell which elements of the prompt cause it to do what and 2. you can rarely get it to do the same thing each time it's triggered with 100% confidence, which make them pretty useless as workflow tools. This definitely feels like bandwagoning rather than actually coming at it from the perspective of what anyone would find useful.
I don't even get the sense the questions/answers have been written by a human? I have no idea how you could land on the three available options for the cultural environment question.
I had some fun trying to get this to work with prompts based on specific brands etc. It felt like it had a pretty good attempt at a Fender Jazz Bass and a Moog Mother, but struggled with a Juno 6. Is that pure coincidence or would the model be able to understand the semantics of specific instruments and things as well as more generic terms?
For arrangements/history/background/variations on folk songs, especially Irish, Scottish, and American ballads, mudcat.org is an incredible resource that's still rocking the early 2000s plain HTML look.
Can't say enough good things about sheldonbrown also. It's the ultimate resource for people who want to bodge a bike build from their parts bucket.
We set out to experiment with whether we can usefully automate low-code development tasks using RPA. While we were able to set it up to ship tools relatively easily, the constraints we encountered make it tricky to see many real-world applications for doing so. This article explores what we learned.
I've tried to create resources like this in the past for internal use in agencies and also mentoring clients and I think the thing that makes it really tough is that for any of this kind of information to be actionable the would-be SEO needs to get a grip on the creative and strategic elements. For example - I always found it tough communicating to colleagues/clients that it's one thing seeing a particular keyword on Semrush/Ahrefs that they'd like to after - it's another having enough experience to work out if it's something that's worth their effort based on things like their domain authority/core web vitals - and then again knowing what to do to go after it in RE search intent and how to out-compete the existing results.
Then there's the extra tricky bit that the kind of people reading these types of articles are often going to be small business owners/entrepreneurs who aren't necessarily going to want to put the time and effort into the above.
I don't mean this is a criticism of the original article to be clear. It's my own experience of trying to create resources like this that readers would be able to pick up and use to drive traffic (and ultimately make money). This article goes after more of a glossary-style approach, which is still going to provide value - knowing the lingo is really important for the kind of people who will want this kind of resource, if nothing else to help them understand what they're talking about if it comes to dealing with external stakeholders or agencies etc without getting ripped off. It's an inherently difficult topic to be comprehensive about in a blog post - if it wasn't, there probably wouldn't be so many people making good money as full-time SEOs.
I love this. I've definitely seen one of those TV chefs go to SE Asia somewhere and be served a broth that claimed to be >150 years old - probably Anthony Bourdain.
Tough one to get past the hygiene inspector I guess though.
This is the exact point in the market I try to look out for when I'm buying any kind of product - not just studio gear. I've heard someone referring to some kinds of products as the 'AK-47 option' - as in reliable, ubiquitous, mendable, versatile and (relatively) inexpensive. I think the other classic examples were telecasters, SM57s and the Toyota Hilux if memory serves.
Anyway, really cool to see a write up like this on an iconic but often unsung-hero of a piece of gear.
I took a course from a local conflict mediation charity based around the Harvard Negotiation Project's framework on Difficult Conversations (So another vote for soft skills, really). It completely changed the way I think about dealing with internal & client side comms - with a big part of the focus being on trying to understand the underlying motivations behind people you're communicating with. Honestly, this feeds into how I try to communicate with people in a non-work context too, so, can't recommend it highly enough.
Not sure how helpful that'll be in terms of finding a course that you can access yourself, but link to the original book outlining the framework below.
The human in the mix is definitely the interesting part here. UI design inevitably has a more subjective element than other tasks, so I suppose it would be tricky to build a solution like this because, even if what it outputs is objectively a good UX, the end user will base their judgements on their own design preferences, so it'd be hard to satisfy everyone enough to get something working that's commercially viable.
I wonder is there also a factor that - since there are so many low/no-code and WYSIWYG UI tools on the market already - the potential time savings are lower compared to back-end tasks that are being targeted by AI tools - ie providing language prompts to get a tool to output UIs and then needing to tweak them to implement your own branding/messaging/design preferences might not be that much faster than building the same UI from scratch with the kinds of solutions already on the market.
Very interesting to see how this space could play out over the coming years anyway.
I've also read a line of thinking that negatively correlates home ownership with entrepreneurship - or sometimes this is operationalised as a high proportion of net worth being accounted for by home ownership rather than other assets.
This paper explores the idea in the UK over time, but I've seen studies out there that examine the idea comparing the UK to other European countries where home ownership is less of an embedded norm:
https://conference.iza.org/conference_files/ESSLE_2012/brack...
Anyhow, very interesting to think that there are human traits at play as in the original article as well as structural/socio-economic factors.
This is my attitude. Doing these kinds of things for your own satisfaction is something that gets majorly overlooked. Reminds me of Kurt Vonnegut talking about writing a poem every day just for the heck of it.
Even if you're not actively trying to progress, writing/coding/working out/cooking/whatever else can be done for its own sake and still be rewarding, and sometimes it's good to resist the urge to compete with others or even monetize hobbies.
Is this always on or can it be opted out of? What if you don't want your data exposed to chatgpt