> Maybe having a loud profile is a positive to some sorts of recruiters but posting anything beside resume information on that site just seems like a guaranteed malus on future prospects.
At one of my past companies, I recall a recruiter disqualifying a candidate for a SWE role solely for having a "weird" headline banner image on their LinkedIn profile.
The "weird" image was a benign screenshot of a landscape backdrop of some Miyazaki film. No characters, no action sequences -- literally just trees, mountains, shit like that.
I think GP assumes that Myazaki's films have transcended the "anime" label. They certainly have with me, and with most mainstream film critics. But based on the LinkedIn reaction, and your comment, maybe not? That's interesting.
I think Miyazaki films are cool, but I seriously doubt most people who aren’t film buffs will really recognise them.
I think many if not most people will have negative associations when they think of adult anime enthusiasts, therefore most people with good social skills would not put anime on their LinkedIn.
I also probably wouldn’t want to hire someone who’s holding a gun in their LinkedIn photos (unless it was related to their work), even though I’m a hobbyist shooter myself. I think shooting is a cool hobby, but I understand that for many people it’s a weird enough hobby that it would be downright stupid to advertise it in an unrelated professional context.
The problem isn’t anime (or guns), it’s the poor judgement demonstrated by adding pointless question marks on what might otherwise be a good profile.
I think we agree with each other, but also that you missed my point: the "mistake", as it were, wasn't to do with social skills as much as assuming Miyazaki / Studio Ghibli had crossed into the mainstream, which... It seems isn't accurate.
Though, I don't know: would putting any film background on a LinkedIn profile read as "unprofessional"? (I don't know; I've never used LinkedIn in any capacity.)
Maybe, but as someone who's done a 4-month backpacking stint, I was over it after 1 month, so I think even just that amount of time is enough to make an impact psychologically. By month 3, I was acclimated to it, but still eager to be done with it.
(As an aside, the experience actually made me less enthusiastic about nature and gave me a deeper appreciation of civilization. Never in my life did I have such deep gratitude for having a flat paved sidewalk to walk on.)
After several weeks I got to a campsite that had a picnic table. It was such a pleasure to have a place to sit upright and prepare my dinner. I'll never take one for granted again. After getting used to doing everything on the ground a table and a bench are a luxury experience.
We're in a mode where we're 'camping' with a 5th wheel trailer. It has COMPLETELY altered my travelling experience in ways I never expected. Being in Nature, with a clean bathroom and warm shower and cold beer makes the experience amazing.
More in line with this thread: Our house is full of stuff. It's a long story that ends up being: four adults living in the space that holds two comfortably.
Having the trailer lets us spend time in a relatively uncluttered environment. IT's a reset that lets me not get quite so worked up about the time I spend not-camping.
The ease of creating visually titillating media, coupled with the difficultly of consistency works against the creation of narrative media. I sure hope we don't get a generation of non-narrative beautiful slop.
Not inviting the man in your life is an important lesson. Not the way I'd teach it, but they may have saved him a lot of jailtime or other issues teaching it to him early.
Guess it boils down to personality, but I personally love it. I got into coding later in life, and coming from a career that involved reading and writing voluminous amounts of text in English. I got into programming because I wanted to build web applications, not out of any love for the process of programming in and of itself. The less I have to think and write in code, the better. Much happier to be reading it and reviewing it than writing it myself.
No ones like programming that much. That's like saying someone love speaking English. You have an idea and you express it. Sometimes there's additional complexity that got in the way (initializing the library, memory cleanup,...), but I put those at the same level as proper greetings in a formal letter.
It also helps starting small, get something useful done and iterate by adding more features overtime (or keeping it small).
> No ones like programming that much. That's like saying someone love speaking English. You have an idea and you express it.
I can assure you both kinds of people exist. Expressing ideas as words or code is not a one-way flow if you care enough to slow down and look closely. Words/clauses and data structures/algorithms exert their own pull on ideas and can make you think about associated and analogous ideas, alternative ways you could express your solution, whether it is even worth solving explicitly and independently of a more general problem, etc.
IMO, that’s a sign of overthinking (and one thing I try hard to not get caught in). My process is usually:
- What am I trying to do?
- What data do I have available?
- Where do they come from?
- What operations can I use?
- What’s the final state/output?
Then it’s a matter of shifting into the formal space, building and linking stuff.
What I did observe is a lot of people hate formalizing their thoughts. Instead they prefer tweaking stuff until something kinda works and they can go on to the next ticket/todo item. There’s no holistic view about the system. And they hate the 5 why’s. Something like:
- Why is the app displaying “something went wrong” when I submit the form?
- Why is the response is an error when the request is valid?
- Why is the data is persisted when the handler is failing and giving a stack trace in the log?
- Why is it complaining about missing configuration for Firebase?
- …
Ignorance is te default state of programming effort. But a lot of people have great difficulty to say I don’t know AND to go find the answer they lack.
None of this is excluded by my statement. And arguably someone else can draw a line in the sand and say most of this is overthinking somehow and you should let the machine worry about it.
I would love to let the computer do the investigative work for me, but I have to double check it, and there's not much mental energy and time saved (if you care about work quality). When I use `pgrep` to check if a process is running, I don't have to inspect the kernel memory to see if it's really there.
It's very much faster, cognitively, to just understand the project and master the tooling. Then it just becomes routine, like playing a short piano piece for the 100th time.
Or just hire adults who know how to proactively communicate issues and concerns without a group babysitting session?