My perspective is that an opinion from a Christian viewpoint can never be 'inappropriate' anymore than an opinion from an atheist or agnostic viewpoint should be. You may be angling toward that idea that religion, money and politics should not be talked about in polite company, but we are hardly polite and we are already talking about politics, yes. Christians should have a seat at the table just like anyone else, and be as free to dismiss your beliefs as you seem to feel you are to dismiss theirs. Insh'Allah
Wondering if you're a member of the Mensa of atheists, the Freedom From Religion Society
Klaatu nikto barrada.
Coincidentally, I wrote that in a software comment last night.
It seems you often shoot just left if the point we try to make. You seem to just circle this drain of persecution...
[So, are you trying to say I'm jerking my trigger now? ]
Coincidentally, I wrote that in a software comment last night.
I'd love to know what you were writing.
What language, os, purpose?
I deal in C almost exclusively.
I was (and still) writing a program to mangle some files, at the end is a magic signature...
// Now write Klaatu nikto barrada to the file so the device recognizes it as valid.
It was a reverse engineering job because another engineer never bothered to document the formatting or check his source into revision control.
I write a lot of sarcastic and culturally relevant comments (who me?). My philosophy is that comments should explain high level details and explain why you made certain design choices and where potential pitfalls are; they should be multiple paragraph when necessary. My symbols (e.g. variable and function names) are often very long, and rarely do I use abbreviations.
You should see my git commit comments.
Well...everyone says that. But lets get back to the idea that you've come to the conclusions by yourself.
You didn't used to believe in Bible prophecy. But now you do. Your change of mind appears to be caused by your attendance of the "last days" studies where maybe it did not feel like it was being explained to you. Many denominations have such studies--nothing untoward about that--and what's presented to you as "plain scripture" takes on the meanings implied. Again, nothing untoward about that. It's just how we think. For every one of you who think that you arrived at your belief about prophecy on your own, the thing you tend to believe is what the group says it means.
It is indeed ambiguous text. There are many plausible meanings. And that's why there are so many denominations, and interpretations. Attend the prophecy study groups of 20 different denominations and you'll come away thinking they're all wrong, that YOU are right. Well, every one of them will have the same impression as you, that THEY are the ones who are right, and everyone else has it wrong.
I'm not saying you should not believe what you've come to believe. But beware of the kind of confidence that leads to hubris; an assumption that you are right, and that they are wrong. Without any other input, you have 100 different people who have no prior knowledge of eschatology, they'll each have a different take on what it could possibly mean. Generally each denomination will have their own interpretations, and their interpretations will likely come from where their leaders went to seminary.
Having the state tell you what your invention is worth and then take the rights to it IS socialist--unless you decide it's a good deal. If it was an issue of increasing production capacity, other companies could be licensed by the inventors to make it.They can be reimbursed for the value of it, the concept is to spread it to other drug makers to increase the manufacturing capacity.
That isn't socialism.
Do you think the arms manufacturing market is socialist? Because that's more or less exactly what they do with the TDP.
https://thehill.com/opinion/energy-...dens-devotion-to-radical-great-reset-movement Fronkinstein is at it again.
My philosophy is that the code should explain the high level details. Comments explaining WHAT you’re doing should be rare. But sometimes WHY you’re doing it is important enough to comment. But I understand you’re doing imbedded systems so that’s not always feasible.I deal in C almost exclusively.
I was (and still) writing a program to mangle some files, at the end is a magic signature...
// Now write Klaatu nikto barrada to the file so the device recognizes it as valid.
It was a reverse engineering job because another engineer never bothered to document the formatting or check his source into revision control.
I write a lot of sarcastic and culturally relevant comments (who me?). My philosophy is that comments should explain high level details and explain why you made certain design choices and where potential pitfalls are; they should be multiple paragraph when necessary. My symbols (e.g. variable and function names) are often very long, and rarely do I use abbreviations.
You should see my git commit comments.
My philosophy is that the code should explain the high level details. Comments explaining WHAT you’re doing should be rare. But sometimes WHY you’re doing it is important enough to comment. But I understand you’re doing imbedded systems so that’s not always feasible.
Sarcastic comments would definitely not fly where I work. Pull requests and peer review is part of the process. We can’t just change code. I would reject a pull request if the code did not meet what we agreed were the standards.
I kinda liked Subversion before Git came along. It was better than CVS. But git is pretty much it now.Standards?
We're a team of 3.5 total. So the embedded stuff is all me. I do follow the MISRA C standard. 'Round here, I'm considered the process enforcer; I manage the build server and all it's static analysis.
I did work on space project for a major defense contractor, so I was more disciplined there. Actually, I was less disciplined in ways, as they were stuck in the 90's using waterfall development (and Subversion ). Now days I use Test Driven Design - my code is a lot cleaner.