|
|
Judging by the amount of POO (programmation orientée objet) I see these days. 
|
|
|
|
|
One of the reasons I'm such a prolific contributor here is I'm using the good people of codeproject.com
This site is an archive of my stuff, a portfolio, and documentation. I wonder if Chris feels used yet? 
To that end, I refer to my stuff when I'm mentoring other people on some reddit and discord spots I haunt.
It seems like I always have an article for the occasion that I can link to. "Oh here's how you do this." "You want to wrap that with *what* now? Okay. Here you go."
It's very convenient, but hard to keep up further inspiration for future contributions. I feel like a bit like The Simpsons - they already did it.
Check out my IoT graphics library here:
https://honeythecodewitch.com/gfx
And my IoT UI/User Experience library here:
https://honeythecodewitch.com/uix
|
|
|
|
|
Or just hope for the best or just re-write everything from scratch with the 2 versions on different screens for reference ?
I added a new feature in my developement branch as part of some bigger changes (database) , I needed to backport it to main branch, and I improved it on the main branch.
Now I have to merge it back to the development branch.
lolz... 
I just hope it compiles at this point and start fixing it !!
CI/CD = Continuous Impediment/Continuous Despair
|
|
|
|
|
I usually type the lines of code on Hollerith cards, then shuffle the deck like a tarot reader and hope for the best.
Will Rogers never met me.
|
|
|
|
|
Manually or auto: I can feel with you, I have always a bad feeling while merging branches 
|
|
|
|
|
Step 1. Take chicken.
Step 2. Sacrifice chicken.
Step 3. Attempt merge.
Step 4. Cook chicken. At least that might work because step 3 sure as hell won't have and, at least you'll have a good meal.
|
|
|
|
|
Pete O'Hanlon wrote: Step 2. Sacrifice chicken to Bubastis.
FTFY 
Freedom is the freedom to say that two plus two make four. If that is granted, all else follows.
-- 6079 Smith W.
|
|
|
|
|
An ounce of prevention is worth a pound of cure. You'll get less merge conflicts (it won't be perfect, just less) with strict formatting rules for the project. But, if it's already out of whack and the mergyness needs to happen...
(Speaking git lingo but it should be transferable)
Assuming it's a large merge....
- If it's not hundreds of commits and the devs actually made smaller commits, use rebase. It'll take a bit to go through all the commits but you can take it in bite sized chunks which may be mentally easier.
- If it's hundreds of commits then, first make sure you diff tool can ignore whitespace. Something like Beyond Compare will do that. Second, run all your linters and code formatters on both the target and the destination branches before attempting the merge. And lastly, for the love of all things pure do a 3-way merge to help give you context.
Jeremy Falcon
|
|
|
|
|
If you are comparing code - I strongly STRONGLY recommend Beyond Compare. My coworker, mentor, boss sent me in this direction, and I never looked back.
As far as the general process - full disclaimer I use SVN and Tortoise, so I cannot speak to what GIT does - doing a large merge should be off in a branch. Once you are done and happy, you can migrate it to the trunk. Using this approach, you have a retreat path. Feel free to do as many commits as you want on the branch to show your merge work. Better yet, have developer 1 and 2 commit their work on separate branches and merge those. Protect the trunk.
Charlie Gilley
“They who can give up essential liberty to obtain a little temporary safety deserve neither liberty nor safety.” BF, 1759
Has never been more appropriate.
|
|
|
|
|
I use WinMerge for single files. Used to be much better before someone got the idea that when a directory on one side was empty that one should (must) show all the files on the other side.
So now I also use BeyondCompare. Just need to figure out all of the rules to add every time I must install it fresh.
And then I make sure I am very, very focused on figuring out the updates.
|
|
|
|
|
I saw a low-flying helicopter over a local strip mall and captured this video.
Low-flying Helicopter Over Strip Mall - YouTube[^]
That's the big excitement this week, folks. 
NOTE: Turn on sounds for chopper sounds and commentary.
The chopper really was quite close.
|
|
|
|
|
Helicopters? I did not know Ohio had such technology. 
|
|
|
|
|
Looks like a Robinson (R44?) descending to land. Is there an open space where it was headed, sports field, etc?
As well as sometimes working with firefighting helis, I see and hear enough of them to be able to identify most by sound alone.
Yesterday, from memory, a couple of military Blackhawks, an AW-139, a Huey (or Bell 2xx derivative, didn't get a visual) and an AS-350 Squirrel.
Software rusts. Simon Stephenson, ca 1994. So does this signature. me, 2012
|
|
|
|
|
I wonder if they actually had all of the permissions for that landing.
|
|
|
|
|
I am thinking about using a static code analysis to identify security vulnerabilities as I and my team write code. (Like Sonar lint but for security).
I have come across some extentions like
Security code scan[^] or Synk Security[^].
Do you have any experience with such extensions?
If yes do you think they are useful?
Do you have other recommendations?
|
|
|
|
|
You do know that Sonar can help identify security vulnerabilities don't you? If you're using Visual Studio, you can also use security analyzers to help detect OWASP errors. To be honest, and I speak with a lot of experience in this area, SAST can be more dangerous because it gives you a false sense of safety. All SAST tells you is that the code you checked in doesn't have a vulnerability. It's not that great at determining that a dependency of a dependency of a dependency has a known vulnerability, or that you have an unpatched container or OS vulnerability. You need to consider security as a top to bottom thing, so you would be looking to leverage SAST, DAST (the dynamic version of SAST), IAST (the infrastructure version), and so on.
|
|
|
|
|
|
We forced to use Checkmarx One - the most annoying thing is that 90% of the 'findings' are BS... For the first time - after that it is 100% BS (if you fix the real problems)
"If builders built buildings the way programmers wrote programs, then the first woodpecker that came along would destroy civilization." ― Gerald Weinberg
|
|
|
|
|
I can recommend the free OWASP Dependency-Check.
I found Snyk disappointing, for .NET it only scans NuGet packages and ASP.NET applications are automatically marked as "high security risk".
|
|
|
|
|
GKP1992 wrote: static code analysis...If yes do you think they are useful?
No.
At best it might help junior developers.
At worst it makes senior developers think that is all or even most of what is needed. Or even significant.
|
|
|
|
|
Wordle 1,067 4/6
⬜⬜⬜⬜⬜
⬜⬜🟨⬜🟨
🟩🟨🟩⬜⬜
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 1,067 3/6*
⬜⬜🟨⬜⬜
⬜🟨🟩🟨⬜
🟩🟩🟩🟩🟩
"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!
|
|
|
|
|
Wordle 1,067 4/6
⬜⬜⬜⬜⬜
🟨⬜🟨🟨🟨
⬜🟩🟩🟩🟩
🟩🟩🟩🟩🟩
|
|
|
|
|
Wordle 1,067 4/6*
⬜⬜⬜⬜⬜
⬜⬜🟨🟨🟨
⬜🟩🟩🟩🟩
🟩🟩🟩🟩🟩
Happiness will never come to those who fail to appreciate what they already have. -Anon
And those who were seen dancing were thought to be insane by those who could not hear the music. -Frederick Nietzsche
|
|
|
|
General 
News 
Suggestion 
Question 
Bug 
Answer 
Joke 
Praise 
Rant 
Admin 
Submit an article or tip
