ShakyJake
<Donor>
- 7,921
- 19,997
The language itself or the concepts? I know it took me a while before object oriented concepts became instinctive.
IT/Software career thread: Invert binary trees for dollars.
- Thread starter Traak
- Start date
-
Guest, it's time once again for the massively important and exciting FoH Asshat Tournament!
Go here and give us your nominations!Who's been the biggest Asshat in the last year? Give us your worst ones!
Conefed
Blackwing Lair Raider
- 2,850
- 1,702
I'm at the level where I don't know the difference. Currently I'm copying stuff without understanding what I'm doing.
Siliconemelons
Naxxramas 1.0 Raider
- 11,926
- 17,900
Okay super pals...
2 or more ISPs load balanced into "one" for speed and failover purposes.
Solution needs to be as close to plug and play as it can be - aka system admin dumb, not network admin easy.
looking at this ...
2 or more ISPs load balanced into "one" for speed and failover purposes.
Solution needs to be as close to plug and play as it can be - aka system admin dumb, not network admin easy.
looking at this ...
Rude
Potato del Grande
- 3,824
- 12,052
Have you ever asked him why he refuses to move up or is your opinion naive and arrogant? I take it you've never played in the lead / management arena?
- 1
Noodleface
A Mod Real Quick
- 38,287
- 15,129
He just doesn't want to manage people or lead. Some people are like that, I get it. My opinion is also pretty naive.
Denamian
Night Janitor
- 7,494
- 20,745
Being in charge of others can be a pain in the ass that you don't want even if you're capable enough to do it. I prefer to just be another cog in the machine even though that means I have little authority over what I do. It does help that I lack any kind of ambition.
- 1
- 1
alavaz
Trakanon Raider
- 2,003
- 714
Okay super pals...
2 or more ISPs load balanced into "one" for speed and failover purposes.
Solution needs to be as close to plug and play as it can be - aka system admin dumb, not network admin easy.
looking at this ...
Never heard of Peplink. The absolute simplest that fits your use case would probably be a Linksys LRT224 or a Ubiquiti Edge router.
- 1
- 7,879
- 507
Yeah, I made the leap from "do-er" to "manage-er" and regret it about 51% of the time. I've also inherited some team members that are "ok", and made a bad call in hiring another one.
Wanted to get some input on my companies current practices of how to properly permission folders on a network share. Maybe I'm just being daft, but I think how we currently do things is archaic and a bit of a mess.
The gist is that each division has a folder on a dfs share. Basically, heres a folder, dump what you want in there, create other foldes/subfolders/etc. Occasionally we'll ask the heads of each division to work with thier team to get rid of any unnecessary files. Each divisions folders is locked down via SGs (read/write, read, etc, though oddly the naming convention for the SGs isnt standardized or properly documented) and they can only see folders they're permissioned for. Over 30 divisions, each division has probably at least a 1000 folders within their shares, plus the files (several hundreds of thousands).
On occasion, divisions will work together, which means an employee(s) may need access to files/folders in another divisions share, but only the requested files/folders. This most likely means we create a new SG(or SGs) to restrict access to the requested files/folders. This can be somewhat time intensive.
This isn't a process I created or am obligated to fix but I am interested to see what some of you guys do instead of doing whats described above (because its shit). We do use sharepoint/teams for some things, but its not even close to fully integrated. I think standardization, user education, and properly documenting things could go a long way, but I have to think theres a better solution/practice to the cross sharing of folders/files that we aren't currently using.
The gist is that each division has a folder on a dfs share. Basically, heres a folder, dump what you want in there, create other foldes/subfolders/etc. Occasionally we'll ask the heads of each division to work with thier team to get rid of any unnecessary files. Each divisions folders is locked down via SGs (read/write, read, etc, though oddly the naming convention for the SGs isnt standardized or properly documented) and they can only see folders they're permissioned for. Over 30 divisions, each division has probably at least a 1000 folders within their shares, plus the files (several hundreds of thousands).
On occasion, divisions will work together, which means an employee(s) may need access to files/folders in another divisions share, but only the requested files/folders. This most likely means we create a new SG(or SGs) to restrict access to the requested files/folders. This can be somewhat time intensive.
This isn't a process I created or am obligated to fix but I am interested to see what some of you guys do instead of doing whats described above (because its shit). We do use sharepoint/teams for some things, but its not even close to fully integrated. I think standardization, user education, and properly documenting things could go a long way, but I have to think theres a better solution/practice to the cross sharing of folders/files that we aren't currently using.
Asshat wormie
2023 Asshat Award Winner
- 16,820
- 30,968
Mist
REEEEeyore
- 31,252
- 23,494
Wellm our security is awful and we have VPNs into our customer environments using unsecure passwords easily searched up in our Sharepoint that hundreds of third party contractors in other counties also have access to, so that covers the stupidity part...
Noodleface
A Mod Real Quick
- 38,287
- 15,129
The younger guy on our team is making massive commits constantly, so much so that it's disruptive reviewing his code. But he's ambitious so whatever. What's annoying Is I think in his head he thinks that he with the most story points completed wins, not realizing that story points are relative to the engineer. What bothers me the most is I'll comment on his code reviews and immediately he shoots down my criticism.
I don't nitpick shit, but I do look for things that stick out or are useless. For instance he defined two vars and did
Just to initialize them. He then never used other_id, so I commented that it isn't used. He then references that it was used on that line I listed above and it's ok. I mean technically sure, but why have an extra byte hanging around? Plus it looks stupid and unprofessional. You could argue that's nitpicking but it stood out to me.
Another was we changed the labelling on hardware but his code was printing old labels. I pointed it out and he argued users are used to the old labeling so we should use that. Boss backed me up on that.
Just senseless. I don't mind someone defending their code but for obvious things, come on?
I try to mentor junior engineers as much as I can, but you can tell this guy is hearing nothing you're saying sometimes.
I don't nitpick shit, but I do look for things that stick out or are useless. For instance he defined two vars and did
C:
id = other_id = 1;Just to initialize them. He then never used other_id, so I commented that it isn't used. He then references that it was used on that line I listed above and it's ok. I mean technically sure, but why have an extra byte hanging around? Plus it looks stupid and unprofessional. You could argue that's nitpicking but it stood out to me.
Another was we changed the labelling on hardware but his code was printing old labels. I pointed it out and he argued users are used to the old labeling so we should use that. Boss backed me up on that.
Just senseless. I don't mind someone defending their code but for obvious things, come on?
I try to mentor junior engineers as much as I can, but you can tell this guy is hearing nothing you're saying sometimes.
- 1
Vinen
God is dead
- 2,790
- 495
Ouch. Hopefully you can work with his Manager to get him nick'd on his review for not accepting feedback from more Senior Engineers. It will help teach listening.
I'd have had a long conversation with the Engineer on the side by now.
Large Code reviews & no taking Feedback are two bad characteristics.
Noodleface
A Mod Real Quick
- 38,287
- 15,129
Vinen
God is dead
- 2,790
- 495
Lendarios
Trump's Staff
- 19,360
- -17,424
He created a variable, initialized and never used it.
And he is complaining about you pointing that out.
Tell him he is flat out wrong about that one. That is not nitpicking. Tell him he writes code so other people can read it, and having extra unused variables reduces that.
If he still doesn't get it as him if this is fine.
and see his reaction.
Also you don't have to explain to him. Reject the code review if he keeps doing this.
And he is complaining about you pointing that out.
Tell him he is flat out wrong about that one. That is not nitpicking. Tell him he writes code so other people can read it, and having extra unused variables reduces that.
If he still doesn't get it as him if this is fine.
C:
id = other_id = other_id1 = other_id2 = other_id3 = v other_id4 =other_id6 =other_id5 =other_id =other_id = v other_id = other_id = other_id = other_id = other_id = other_id = other_id = other_id =other_id1 = other_id21 = other_id5 =other_id8 =other_id =other_id7 =other_id = 1;and see his reaction.
Also you don't have to explain to him. Reject the code review if he keeps doing this.