- 1,920
- 4,546
Please say no, please say no, please say no.Not develop this way. Holllly shit does this sound like terrible practice.
Do you both go off and work on changes to the same origin at the same time? Then merge back months later?
Please say no, please say no, please say no.Not develop this way. Holllly shit does this sound like terrible practice.
Do you both go off and work on changes to the same origin at the same time? Then merge back months later?
Figured that was the case.I can't break any Ndas here but we purchase the source from them. They sell a one size fits all bios for every customer they have and customers modify it themselves. We have to pull in their updates for critical bug fixes by them and Intel.
It sounds dumb, and it is.
I put all our code changes between ifdefs just so I know what we modify.
Emc did the exact same thing.
Anyways, I just wanted to know if there was a better way.
I just do a beyondcompare on the two folders and then all the differing files I have to manually check. Thankfully not all the code changes, but a lot does.
Massive merges are a mess. This is the reason many products are moving to feature-switches and avoiding feature-branches.Well fml then. At Emc we had one dude always do it
TJT is dumb.I have a degree in Computer Science... I was just saying that the theory portions of the curriculum are fucking dumb. Data Structures? Interesting class but since all of that shit is handled by libraries you can get. Its just not worth the time to focus on. Practical application of coding to build things is just way more useful, in the terms of CompSci.
You can't break it up so their code doesn't intermix with your own stuff? LikeI can't break any Ndas here but we purchase the source from them. They sell a one size fits all bios for every customer they have and customers modify it themselves. We have to pull in their updates for critical bug fixes by them and Intel.
It sounds dumb, and it is.
I put all our code changes between ifdefs just so I know what we modify.
Emc did the exact same thing.
Anyways, I just wanted to know if there was a better way.
I just do a beyondcompare on the two folders and then all the differing files I have to manually check. Thankfully not all the code changes, but a lot does.
I'm saying the Data structures class taught me when to use a list, a hashset, a linked list, an array list, Taught me how make a flood algorithm, how to find the path out of a maze, how to make a tick tack toe program. It taught me about O time of data structures, how to compute O times.Are you telling me that you, in all of your code, handle data structures with code that you write?
As opposed to just using any of the infinite amount of pre-existing frameworks that do it all for you?
Choosing the proper data structures to use, knowing when they aren't working, and recognizing why is like one of those critical jobs software developers have. Yes everyone uses libraries, but if you couldn't write those libraries from scratch you're just a monkey.Are you telling me that you, in all of your code, handle data structures with code that you write?
As opposed to just using any of the infinite amount of pre-existing frameworks that do it all for you?
You wouldn't, but you should know what they do well enough to be able to.Why would you need to write them from scratch if they already exist?
This makes no sense to me. Are you saying that you have to have the source code and know exactly how everything works to use any third party libraries?Choosing the proper data structures to use, knowing when they aren't working, and recognizing why is like one of those critical jobs software developers have. Yes everyone uses libraries, but if you couldn't write those libraries from scratch you're just a monkey.
Yeah that's just way too oversimplified.You can't break it up so their code doesn't intermix with your own stuff? Like
I'm sure I'm just oversimplifying the problem since I have no knowledge space about how the bios work
Oh god, having to change core functionality at even an if/else level? No thanks. I was under the impression they just provided a suite of functionality that you had to add a variable or parameter to here and there. Sounds like you guys are completely changing the entirety of the functionality if you're even changing logic within. Why even use third party software at that point? Ugh.Yeah that's just way too oversimplified.
It's more like:
multiply that by 7,000,000
We have to overwrite what they're doing in a lot of places to make sure stuff is initialized properly. Also BIOS runs in phases (PEI, DXE, SMM) and everything is dependent on a million other things.
When you add a brand new feature you can usually make your own files and libraries, but for the most of it you're directly editing their code.