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.
Its nonsense to say he cant test. Your project needs to create a test database to test against, and the Lone Ranger needs to be testing his new functionality against that. You could create a script to create an empty version of your live db and load test data into it.
He needs to amend his connection string to test the app against that, or at the very least if its SQL paste his changes in SSMS (or whatever your RDBMS client tool is) and run it against the test db.
In the long term you could aim to create a suite of automated unit tests which are run before a deployment to reduce risk further.
If its government work, here in the UK we have to conform to certain standards part of which is having a test strategy and evidence testing has taken place (and not against live data). We are audited on compliance to this. If you have similar in your locale,you could be at risk of failing an audit and losing business.
Having read the Habits of high performing teams post last week, maybe High Psychological Safety comes in here.
Unclear of the organisation structure of this team, and maybe this will lean more toward a manager person to sort, but here goes:
From their perspective they might be in a defensive position (dont have time to test) and they maybe worried that you lot will criticise how bad his code is.
So, the first step is to have them understand that all of you are their to work. Yes your code is going to be different to what we might expect, but the reason we have been assigned to work with you is because what you have made so far is good for the company. You have done good, it needs to expand, yes somethings will change, but we are not here to murder you (i am a sarcastic person, remove the last part if this sarcasm doesn't work for you)
Address all concerns as a team, do a meeting - I worry X will be Y. Others either agree or disagree, gets rid of the mental thoughts. Figure out what needs to be setup and what does not need for a team. Source control is always needed.
If the management have basically ignored the project for "a couple of years now" then they have only themselves to blame, and should be thinking in terms of a recovery plan from their lack of support.
It's not possible for a single person to be truly their own QA (etc), while still inside a big system (the management!).
Someone needs to be the proper "support" person that helps the 'LR' victim identify and resolve the (administrative / management) technical debt, so as to back out those years of problems. Victim blaming, just because you / I / someone else would have had different problems, isn't a productive way out of this double blind.
If the LR walks, will the project be cancelled, or will it be a death march? Is it better to 'promote' the LR to being lead advisor to relieve them from some of the historical hidden pressure?
It's still a problem, in many ways, with your (company's) management. Did they know they'd let the project stall, why did the take on the new project without a review?
It's not what's under the rock that's the problem, it's the rock on top!
Do you not have a team/group meeting where you discuss:
1) Massive Backlog
2) Continuous Improvements (where this would fall)
3) Code Reviews
4) Branches and the main branch stability?
Without clarity of purpose and buy in, I assume it isn't happening.
And as professional developers we spend 10% of our time doing continuous improvement. An analogy to painting is cleaning up when you are done. If I hire a painter, I expect him to leave a finished product free of masking tape, and if he used my brushes, they are cleaned, but if he used his, I think I still paid him to clean them... I am 100% okay if he does that on the jobsite as long as he cleans up before he leaves...
So, we allocate it. Otherwise the code just starts cracking under it's own weight. With multiple developers we assign one person to be responsible to make breakthroughs (like parsing all the SQL and bind variables, getting that added to the build process, and either refactoring the code, or the "fixed when touched" approach and verified in code review).
I had a similar problem. My solution was to not come back to the office and find another job instead. A better solution would of course be to first talk to him about the subject, the same way you did in this forum post. If this doesn't help, ask your boss to mediate, that's his job. If this doesn't help either... leave the company.
Show him a benefit to being in a team.
My current role is more implement and support, with a little business analysis.
Moving into a team where others could answer the call was great. They were tech competent and even if I wrote the code using Hungarian notation, they could walk thru it. If a spec was there in full geek, they could translate.
Each of us has our alignment and strengths, and are available to the others.
As we don't dev, we do not do builds and tests. But communication tools of some kind.
Does he have domain knowledge that is useful to all? Does he know (and share) the dark corners that need work?
Lead, help, or go away.
".45 ACP - because shooting twice is just silly" - JSOP, 2010 ----- You can never have too much ammo - unless you're swimming, or on fire. - JSOP, 2010 ----- When you pry the gun from my cold dead hands, be careful - the barrel will be very hot. - JSOP, 2013
Ask yourself a question: why is he "unable to test code before pushing it"?
Is he so stupid or is he so overworked (all these years without a help) and now has even less time to do what he is ordered to do (by manager) because he has to cope with endless questions and complains by you and others on top of his already busy schedule?
And how about you - did you even try to see his situation or are you all under such stress that you do not even have the time to stop and think clearly? Did anybody actually asked him what he needs? ...or you just came in like a flood with "it is our code now and this is how it is gonna be .... you stupid little...."
Start by writing tests and think how to divide the task in such a way that you do not need each others perfect and up-to-date code. Do you really need him to first implement/fix something for you to do your job or you could actually create some independent test-layer or fix it yourself but are lazy and complaining, all blaming the one and only that managed to keep it all running that long with bus factor of 1? Are you really helping?
The basic victimage will really be linked primarily to usage of these phone - and that is simply a Darwinian culling process.
Option 2: the IP's are worried that, with such high speed available via broadcast they'll have to compete instead of maintain their local monopolies (and trusts). Source of the conspiracy theory may be as simple as 'follow the money'.
the IP's are worried that, with such high speed available via broadcast they'll have to compete instead of maintain their local monopolies
I think you're onto something. In my country 40% of population have access to less than 2 Mb/s connections - my parents can't even get a landline and a 56k connections because telephone box is at full capacity and monopolists don't want to install a new one just for a customer.
GCS d--(d+) s-/++ a C++++ U+++ P- L+@ E-- W++ N+ o+ K- w+++ O? M-- V? PS+ PE- Y+ PGP t+ 5? X R+++ tv-- b+(+++) DI+++ D++ G e++ h--- r+++ y+++* Weapons extension: ma- k++ F+2 X
It's not that bad, here, compared to what you describe.
They 'sort of' compete with good introductory pricing - poaching one anothers customers. One of the two (and only two) local suppliers, Altice (a Euro company) is trying to get cell phone customers on its network (fighting back?).
Speed's usually not a problem for most people - living in sensible places. They keep pushing me up from 15->25->100->200Mbs. Everything was fine at 15Mbs, including live streaming via a Roku device. Less expensive plans keep disappearing.
So what's the problem? Both Altice and Verizon know one another's prices and won't really give you any sort of deal. One has contracts, one does not. Here's the real sleazy part:
They may give you a great-sounding deal and lock the price in for one or two years, the deal including some combination of internet, cable TV and a phone line. What they omit is that although the price is fixed for the services, they're free to increase the surcharges all they want. So they charge rental for the internet Modem, Cable TV box if you have one, you must pay a "Sports Surcharge" - now $5/$6 month, even if you don't watch sports. Party, because the big sports networks insist they include their stations in all packages (everyone pays, like it or not). Don't like it? Too bad. That's why I started streaming: them. And their children. Also, there's an accessibility charge - I have to pay extra into a fund so some rural a**hole get his internet cheaper. Phone systems do that, too.
This now borders on soapbox, but those rural sponges have been on federally supplied welfare forever. There are a number of states, all so anti-government anti-taxes that get back more money from the federal government than their citizens pay in taxes.
my parents can't even get a landline and a 56k connections because telephone box is at full capacity
This reminds me of an age-old story, i.e. from the 1970s when phone lines were analog and multiplexing was expensive:
Bodø is a north Norway town with an airport that is essential to the entire region. When a runway was built, many years earlier, a single phone line was laid down below its surface, for communication between the tower and the main building. As traffic grew, the need for a second phone line grew. So they had two alternatives: Either dig a new ditch across the runway for a new physical cable, or use the old line and install multiplexers at each side. The cost of the alternatives were comparable(!), so they ran a project to evaluate the consequences of either. The multiplexer alternative won: They expanded from 1 to 30 phone connections (i.e. a 2 Mbps E1 digital mux, with A/D and D/A converters to adapt to the pre-WW2 standard analog phones) without digging up the runway.
Around here, any old analog copper "sewing thread" wire was capable of carrying an ADSL stream of at least 4-5 Mbps (in the best case 10 Mbps) on top of the analog phone channel. The achieveable bit rate depends a lot on the distance to the local switch, but 2 Mbps E1 will work fine even at quite long distances. Today, 2 Mbps multiplexers are commodity items, the cost is magnitudes below the cost of digging up an airport runway . If the phone company really wanted to offer 30 times as high capacity, they could have done so - either by putting a mux on one line, like they did on the Bodø airstrip. Or they could install ADSL modems for those subscribers who wanted that, like we did here in Norway for something between half a million and one million customers.
Nowadays, about 80% of Norwegian households have fiberoptic connections, so I guess that at least half a million ADSL modems were made available on the secondhand market. In any case: The years I had an ADSL connection, I didn't pay anything extra for the modem itself, so it couldn't be that expensive!
Btw: In Europe, digital lines were never 56 kbps but 64 kbps. 56 kbps is a US artifact due to the "bit stealing" of the LSB every 6 byte to be used for signaling between switches. In Europe, signaling always were on a separate channel, leaving all 8 bits per byte untouched on the user channel. For use on analog and non-multiplexed phone lines, you could buy US style 56 kbps modems, but as soon as that analog modulation hit an A/D converter for a digital 64 kbps channel, it would be completly wrecked (unless the interconect provided an analog US standard modem - which you couldn't expect in Europe - feeding the decoded digital 56 kbps bitstream into a European 64 kbps digital pipe).
If your typical analog "sewing thread" copper lines are ten or twenty kilometers long, then I guess that neither ADSL nor E1 multipelexers are viable alternatives. That's a pity. Make sure that when they upgrade the lines, they do it properly! As early as in the 1980s, I read a news story about an optical fiber cable being pulled between the two cities Oslo and Drammen, of 96 optical fibers. That's the way to do it! Ever since the early 1990s, the major telco around here, Telenor, has been using "hybrid" cables for all new installations: Even though the copper pair was used for quite a few years, when the demand for optical capcities grew, the fiber was already in the ground.
Maye we have been above-average forward looking. Maybe the situation is not as bright in other countries. That's a pity.
Or, better yet, try not to form a viewpoint before evaluating all the evidence. Reminds me of an old saying (paraphrasing): "Sometimes a person's view of the world narrows and narrows until it becomes a point. And than he says 'this is my viewpoint'"
But there is evidence that radio broadcasting is devastating to your dental health! Listen:
In the 1800s and early 1900s, most people had fairly strong teeth, few cavities. Around 1920, radio broadcasters started popping up everywhere, and the average dental health dropped significantly, getting increasingly worse up until WW2.
During WW2, the German occupants confiscated all radio receives and closed down the transmitters. During the war years, we had almost no new dental cavities.
After the war, we got our receivers back, and radio listening rapidly rose, to an all-time-high sometime in the middle or late sixties. Dental health went the other way: In the 50s and 60s, it was so bad that some youth needed dentures before they were twenty years old.
In the late 1960s, TV gradually took over for radio; radio listening dropped significantly. And cavities dropped. Today, people essentially watch TV; radio listening is just for background music, and for car listening. Nowadays, people have stronger teeth than they had in the 1920s, thanks to the reduction in radio listening.
These observations can be fully supported by official statitics. Ther evidence is clear: Dental cavities are stongly correlated with amount of radio listening. So it is used a standard example used in statistics classes as an introduction to correlation.
Of course you also have have correlation with the availability of sugar, candy, sugared drinks, ..., and in the 1970s, fluoride toothpaste started making inroads. But let's keep it simple for now, we can look at those aspects later
Last Visit: 31-Dec-99 19:00 Last Update: 23-Jan-21 21:39