Hm. Might not be standup that’s the problem. Might be a company culture thing. But only you know that for sure. Good luck op! Disassociation can be a life saver.
Web Developer by day, and aspiring Swift developer at night.
Hm. Might not be standup that’s the problem. Might be a company culture thing. But only you know that for sure. Good luck op! Disassociation can be a life saver.
You found an important bug in your short code plugin. Removing the line from .gitkeep
is not actually the solution; it was a symptom of a much bigger and more dangerous problem: you are inadvertently including and parsing a file that is not intended to be a short code.
You, or a crafty hacker, might one day create a file with code in it that should not be parsed as a short code, and not realize that it’s being done. You’re lucky that you’re the one who discovered this and not somebody else.
The solution is the only parse the files that you need to parse. This means ignoring hidden files that begin with a dot. You might also think about creating a default ignore list for any other non-shortcode file that could exist.
Birthed me. Then they had the audacity to celebrate it each year there after.
This post is still not Linux related.
The way I look at it is this: I want credit for the work I do, I should also be able to fork a repo that I work on, and I sure as hell don’t like giving up my rights if I can help it.
But others may feel different.
They are nuts. Their license means that you give up all of your authorship rights to the code you contribute, and on top of that you’re not allowed to distribute modified source, nor can you fork the source for any purpose.
Edit: lol
I’ll admit I’m no c/c++ aficionado, but after a little research I see what you mean. Originally, C++ was a superset of C, but C has since diverged to include things that are not in C++. So we are both correct.
In before the pedants: clang is a c compiler, in that it compiles c code—but it also compiles other languages too. The distinction is that c, c++, rust, etc are compiled directly into byte code , whereas typescript is transpiled into another language (JavaScript) before it is executed. I’ll probably catch heat for this, but you can liken TypeScript to C++ because they both are supersets of another language.
I feel you’ve missed my entire point. My comment was not based on any technical merits of a language. It’s about a persons personal (religious) view of a tool they use to do their job.
I proudly use PHP, JavaScript, Java, Bash, and SQL. They have given me the means to make a long and fruitful 18+ year career. If my boss walked up to me tomorrow and said I needed to learn Python, or Rust, or even brainfuck, I’d learn it and be better for it.
Would it be as easy as my tried and true toolset? Not at first. I still remember the struggles I had when I was first learning my current toolset. It was frustrating. I remember cursing how stupid this or that was (especially PHP and JavaScript). But I learned, and now they’re not as frustrating — because I work with it, and not against it.
Look at JavaScript. Yeah it’s weird sometimes; if you don’t understand how it works. So people slap these transpiled languages or frameworks (like CoffeeScript or TypeScript or whatever) on top, trying to fix the things they think are wrong with JavaScript, and end up making a chaotic mess of the entire community. (And yes we could spend months arguing pros and cons of any merits of transpires and frameworks and why and what not, but then you’re still missing the point).
Anyway, the point is: if it works, then it’s good. Rust does not make Linux worse. If anything, it makes it better because it makes it more accessible to programmers who know Rust but not C. And that’s a good thing. It ensures the Linux kernel will be around longer than whomever ends up being the last C developer.
Those C developers bitching about how they don’t like the idea of rust in their kernel are akin to those old fogies yelling about those damned kids and their loud music or fashion sense.
This quote applies to so many situations and so many languages. It’s beautiful. 🧑🍳 💋
Typescript is always compiled down to JavaScript, so it’s kinda the same thing, but with “nicer” clothes.
People need to chill with the language fanaticism. It’s one thing to make jokes and rip on a language for its quirks, but at the end of the day it’s just a language. If you truly don’t like it, don’t use it. I’m going to take a stab and guess that there is enough Linux kernel source to go around to both the c devs and rust devs. Just be glad they’re not trying to rewrite it in JavaScript. 😉
The problem is that they both are contextual and can mean any position in a list/array. The starting index or starting offset is generally zero, but could be one, depending on the language used.
Amen. Now, where’s that Wine?
Obligatory: this is not medical advice. This is merely my personal experiences. In fact, the only thing I will advise anyone on is that if they feel overwhelmed, they seek advice from a licensed therapist.
So I’ve had a similar problem for the past 9 years. For me, I have to come to the conclusion that I’m in a freeze-state of my dysregulated nervous system.
I’m in weekly talk therapy, and have been working on recognizing the things that have been causing me the most stress, and ways I can deal with or mitigate those things.
And that’s been all fine and good, but I still struggle with getting started on actual activity to help deal with my compounding responsibilities. It’s hard, and some days are better than others.
I used a combination of calendars and reminders to help break down and organize my tasks. I give myself grace if I can’t get them all comply when I initially wanted to finish them, and I try to do at least 2 or 3 things a day ( o matter how small).
What I suggest is not the same as using git rebase
. It’s pretty automatic and easily abortable.
In my experience, this amount of conflicts typically occurs because 1) most people mass commit a bunch of (mostly unrelated) changes at once, which leads to 2) inexperienced/impatient devs to clobber incoming merge conflicts without doing proper merges (mostly because they can’t make heads or tails of the diffs).
This is very easily mitigated if all developers would make small, related commits (with descriptive commit messages and not “committing changes”). This makes everybody’s life easier because 1) diffs are smaller and readable for conflicts, 2) the dev can see the progression of code through commit history, 3) broken code is more easily revertable (and traceable) if something goes wrong, and 4) it’s easier to cherry pick specific changes if the whole changes cannot be published all at once.
Also, git pull --rebase
is your friend and not scary at all. It applies all incoming changes first, then applies your new commits last. 9 out of 10 times it avoids conflicts.
Lastly, use a GUI. There are plenty out there to suit your tastes, and I feel they are a safer and easier alternative than CLI. Some GUIs are very safe and even allow undo operations on most things.
I know this is a joke, but those errors/warnings/messages screenshot is not from git. That looks more like results from a compiler of some sort.
Sometimes it takes a little unintentional embarrassment to drive a point home. It’ll make them think twice next time.
What I mean by that is that as long as you’re not intentionally or maliciously trying to embarrass them, then you shouldn’t feel bad. You cannot always control how somebody receives information; nor should you. The best you can do is to be clear and polite in your communication. If someone’s feelings get hurt, that’s on them to reconcile, not you.
This is genuinely like parenting a child: they need to develop their critical thinking skills, and to gain their own confidence. So they must be left to make their own mistakes to learn from. Your job is to give show them the tools to use, give advice when necessary, and be there to catch them when they fall; because they will fall.
Doing this will help bolster their self-confidence and make them better mid-/senior-developers later in their career. Coddling them and constantly holding their hand will make them reliant on other people and prevent them from learning anything.
Edit: also remember KISS. 😊
When my dad was in hospice, laying in a coma, I poured my heart out to him saying good bye and all that. The next day he died. Might be a coincidence; it might not. I like to think that he got closure from my ramblings the night before.