curious to see if AI can decipher? Certainly! bonus that we get so see potentially beneficial shell
I'm having a lot of fun taking these inscrutable lines of shell and asking AI to decipher it. Check it out:
spoiler
The ZDOTDIR variable in Zsh specifies the directory where the configuration files (.zshrc, .zshenv, .zshlogin, .zshlogout, .zprofile, and .zlogin) are located. By default, this directory is the home directory of the current user. If ZDOTDIR is set, Zsh will use the configuration files from that directory instead of the home directory.
The script you've posted appears to be setting the ZDOTDIR variable in a complex way, using Zsh parameter expansion and modifiers. Here's the breakdown:
${(%):-%x}: This is using Zsh's %(x,y,z) prompt sequence expansion. This construct is used to insert conditional strings in the prompt. However, in this case, the construct is being abused to get the full path of the currently running script (%x), since the else branch (- modifier) of a prompt sequence expansion is always executed.
:P: This is a Zsh parameter expansion modifier that makes the resulting path absolute by resolving symbolic links. It effectively "canonicalizes" the path.
:h: Another Zsh parameter expansion modifier, which removes the trailing component from a path, effectively getting the directory portion of a file path. This is equivalent to dirname in a POSIX shell.
In summary, this script sets ZDOTDIR to the directory of the currently running script, resolving any symbolic links to get the absolute path. This would make Zsh look in that directory for its configuration files, instead of the home directory. It seems to be useful for a script that's bundled with its own Zsh configuration files, and wants to use those instead of the user's configuration
You're welcome. But don't let this, or any other advice comfort you up to the point where it'll dilute the feeling of urengcy you have now. It is a good motivator; act on it. We all risk becoming obsolete if we get too cozy. Tech moves on; in this field you need to always be learning. I have no advice on how to juggle that and avoid burnout - still figuring that one out :D
I've met many people (myself included) in the tech industry that have experienced similar feelings of stagnation and uncertainty about their career path. You're not alone and there are definitely ways to get where you want to be. From experience, FUD can really eat you alive if you dwell on it.
Having a background in many technologies is actually a strength, not a weakness. It does nothing to hold you back from specializing. You have the ability to understand the broader tech landscape, and that's a valuable trait. While it's true that specialization is important, a wider knowledge base can help you see how different technologies work together, which can make you a more effective problem solver and innovator when you eventually specialize.
Whatever you do, continue to learn and upskill. It seems like you're already doing this, but keep it up.
Some advice? Leverage your current position. It's paying the bills and then some. Keep it around while you learn. You say your current job is not as technically challenging as you would like, this comes with 2 advantages.
-
You can do the bare minimum to stay employed. Since you're not trying to advance in the current field you don't have to stress yourself. Do what you gotta do, no more no less. Use the extra time and energy to put into learning. You don't have to worry about the bureaucracy or "doing the role you want to be promoted to" - often a pre-req to promotion.
-
You can get "selfish" in the way you problem solve by pushing solutions that you want to work on. Look at this this way, you have the solution (something you want to work on) now find a problem in your org you can apply it to. It doesnt have to be optimal, as long as it solves something If you gey noticed, you will become that guy that can do X. This is how I've managed to shift my career in the same department. If you don't get noticed, at least you have real experience applied solutions you want to work on.
See if your company can pay for some classes or trainings. Formal education is definitely not critical but depending on what field you want to break into, they might require either degree or YOE equivalent. So you can work toward a degree while working.
As for the experience question, it can be tough when job postings ask for a certain number of years of experience. Remember that these are usually more like guidelines than hard rules. If you can demonstrate your ability through your projects and show enthusiasm for the role, many employers are willing to overlook a lack of formal experience.
Do lots of LeetCode so you can ace the technical/programming part of the interview. For the rest, honestly just bullshit and be able to talk about how you applied the skill your interviewer is looking for in the domain you're in now. One advantage to that is, since you have a broad view, you have many avenues to talk about.
It's not too late for you. I had a friend that became a math teacher, no formal programming experience. After 10 years he wanted to program. He spent 1 year doing Leetcode and learning how to ace programming interviews and toy problems and now works at Google. SOB went from 60k to 300k, second job ever. What he works on? Google classroom. Can't guarantee the same results, but you can do it!
Let's see what AI has to say about that :D copy-pasting OP's post with some context and letting an AI bot answer it.
@ChatGPT@lemmings.world programming.dev is an instance that his home to online communities that attracts programmers and other tech enthusiasts.
There are no platform's rules, guidelines and policies regarding the use of AI-generated content and we would like to weigh the pros and cons.
I wanted to start a discussion about the use of AI-generated solutions on Programming.dev. Personally, I've found that AI-powered tools have been incredibly helpful in solving programming questions. I won't name any specific commercial software, but I use one that combines GPT-4 and web search to get more factual information. I write some answers I think I might revisit to the ShareGPT community, but I would prefer posting programming solutions to this instance. However, I'm not sure if AI-generated solutions are welcomed on programming.dev. I'd love to hear your thoughts on this. If AI-generated responses are accepted, how should we format the answers, should we just copy paste without quoting, should we quote the model, just mention that it's AI-generated,...?
if the intent of the community is to share things that are considered ridiculous, bold, outlandish, and often for the sake of entertainment, I would suggest "Go big or go home" since it is an established meaning of what to expect, especially in the context of a programming.dev instance. Or maybe "Go big or go void" idk.
Personally i like "Not why why not" because I've never heard of it and if it established itself that would be awesome.
Whatever you land on, make the URL short but descriptive like "gobig" or "whynot" so it's self explanatory when referring to the community whynot@programming.Dev. As clever as nyyn is, my smooth brain can't keep up with all communities that abbreviate.
But have my upvote, I'd love to see more stuff like the videos you shared, them shits rocked!
edit: just saw your edit. URL notyynot is awesome! I vote for that. descriptive and concise
what surprised me here is how much traffic bing gets 😅 integrating with AI was a real pro move, it seems.
Any insight into how much the reduction in traffic is just restricting API usage and actual user interaction? Surely there is a correlation in more API usage (if not just scraping) would drive more engagement?
I'm not a manager but sometimes get roped into interviewing candidates, I really like when they ask the following because it opens up a discussion about "pace" of the team and organization of the department. It also sets the expectations.
What are your expectations of me after 1 month, 3 months, 6 months, and 12 months of bringing me onboard?
In fact, I like this question so much that I'll answer it at the end of the interview even if not asked, I just feel more awkward doing so inorganically. Sometimes we are back-filling a position and the new hire needs to own features by 6 months. Other times we are hiring to expand, in which case there is more runway. Bottom line is, we can discuss if both parties are comfortable with expectations because we want our candidates to succeed. And I as a candidate want to draw boundaries if I am not comfortable.
hey, thanks! Yes, I definitely want Lifestyle and Leisure to be in the context of the programming.dev instance. There is certainly an unspoken comradery we share. And while we are all individuals, I'd say we are more or less in a union to how we approach or see things; and sometimes not! But we won't know until we share :)
.... wow. amazing.
next time you post something as cool as this, write some body for the post. I saw it earlier when you posted but it had no body or other indication of what it is. I'm just hesitant to click on links but this is well worth it!
got a link?