The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
Quite a number of my repos aren't pushed to DevOps because the apps are non-productions one-offs, or educational, or laboratories for experimenting with new tools, and I need another way to back them up.
You could look into any of the free Git providers (GitHub, GitLab, Bitbucket). They all have a free tier with quite sizeable private repo offerings.
I don't always want o commit and push at the end of the day. Maybe I should.
Yes, you should. Half ranting here: I know there is kind of a "shame" to push on private branches half finished work and stuff that is still not right. Besides the obvious safety advantage, in the long run, I find that commit history shows more about the development process and difficulties encountered than a single large commit with a short message. And for the shame part: we all make mistakes and there is no shame in finding and fixing our mistakes. It's always a learning process.
We use DevOps as a central Git repository, but quite a number of my repos aren't pushed to DevOps because the apps are non-productions one-offs, or educational, or laboratories for experimenting with new tools, and I need another way to back them up.
And for those that are in DevOps I don't always want to commit and push at the end of the day. Maybe I should.
If you think 'goto' is evil, try writing an Assembly program without JMP.
I'm pretty certain I've had folders / files disappear when there were account / "owner hardware" issues. Might have been a past issue; or I imagined it. In any case, never again.
I first used it for sharing files, and that's all I'll use it for.
"Before entering on an understanding, I have meditated for a long time, and have foreseen what might happen. It is not genius which reveals to me suddenly, secretly, what I have to say or to do in a circumstance unexpected by other people; it is reflection, it is meditation." - Napoleon I
As I've said many times before, if you don't own the hardware on which the data are stored, you don't own the data.
And as it has been shown several times too...
Daniel Pfeffer wrote:
If you absolutely need to access you source version control away from the office, I would suggest setting up a VPN.
If something has a solution... Why do we have to worry about?. If it has no solution... For what reason do we have to worry about?
Help me to understand what I'm saying, and I'll explain it better to you
Rating helpful answers is nice, but saying thanks can be even nicer.
I used my own version of OneDrive:
0: All code/projects live in shares on the h/o server and are accessible to my main system and my laptop through mapped drives.
1: The laptop uses the 'available offline' option on the mapped drives. When the laptop connects, it automatically synchs up any changes. It's a cheap and effortless backup and gives me full access to everything when I take the laptop on the road.
This has worked really well with just one caveat that I haven't been able to work out: debugging/running web apps with visual studio does not work anymore...it will run and start but session objects don't hold values! It's easy enough just to copy those to a local drive when I need to.
"Go forth into the source" - Neal Morse
"Hope is contagious"
Hey no disrespect, my dad when he was alive probably listened to him...
Okay, like I bet some people hear might not have ever heard of Bob Saget, and he just died...
I was just saying that I didn't know who he was, but I wish he hadn't died...
How do you categorize languages? A recent article on a certain mailing list has debunked "compiled" vs "interpreted". I have long stood by my 3-mutually-exclusive-category system:
Type 1) "Hey, look what I can do in only 7 lines!" (Python, C#, most new languages etc.)
Type 2) "Hey, look what I can do in only 7 characters!" (Perl, awk, golf-oriented gibberish)
Type 3) The good ones.
A lack of planning on your part does not constitute an emergency on mine.
I don't think that "debunked" is quite the best term, but yes, there's nothing about a language itself which means that it must or must not fit into only one of those buckets -- for the most part, any language could be in either or both -- it's just the difficulty of implementation.
"Turing-complete" (vs not) and "general purpose" vs "domain specific" are decent attributes though. As well as how rich the set of supported datatypes is.
But that's just an opinion based on seeing the maintenance problems you can avoid with strongly typed languages.
"I have no idea what I did, but I'm taking full credit for it." - ThisOldTony
"Common sense is so rare these days, it should be classified as a super power" - Random T-shirt
AntiTwitter: @DalekDave is now a follower!
Do latently-typed or duck-typed languages count as "strongly typed"? This is always a point of confusion for me with strong vs weak distinctions - there is no line in the sand. Except for the outliers (rigorously-typed vs un-typed) you can make arguments for the majority of type systems being both strong and weak in different regards. I think Typescript is a great example of this since it has a gradual, structural type system.
Typing should be explicitly visible in the program text, and clearly identified as a type.
Polymorphism, through subclasses, is OK. You can force run time type errors through casting, but casting is explicit.
As pointed out: No language is absolutely bound to being interpreted or compiled, but strict typing leans quite strongly towards a complete parsing of the source code before execution starts. When you do that, why not go all the way and generate the code? So strong typing leans towards compilation rather than interpretation, although not by definition.
That's really interesting that you consider readability as an attribute of strong typing. Not that it's wrong in any way; just that most attributes I've seen that people have come up with have been more function-oriented. Since your criteria have to do more with form, what's your opinion on inferred type systems like F# and Haskell?
I have not spent much time with pure functional languages at all - not enough to have any qualified opinion. For one project, 30 years ago, we evaluated Erlang, but rejected it for our use. My main experience with Lisp is from emacs F# and Haskell I know at "Wikipedia level", not from any practical use.
My professional upbringing is from the days when software designers still did data modelling. I know it is not comme il faut to state, in 2022, that Entity Relationship modelling has something to be said in favor of it, but I have seen ER being used very successfully in a number of projects to really get a grasp on the problem domain. And, it is an excellent tool for communicating with a customer: They will easily understand the concepts so that they can participate in development of the ER model, and when that is in place, they can successfully teach you the operations to be done on the data. (And sometimes they also realize that the current state of data collections and handling procedures is a mess ...)
So I have always been on the data model side, rather than the function oriented one. I guess that is an essential reason why I consider strong typing essential.
Last Visit: 31-Dec-99 18:00 Last Update: 23-May-22 6:57