yep, or someone engaging with enough bad faith that the distinction makes no difference. I usually give folks the benefit of the doubt once and then move on.
Since you seem to know what you’re talking about, I’m looking for some advice: I work for a large and very well known engineering company and currently our incredibly terrible workflow looks something like this: Develop locally using VStudio -> transfer repo to network drive -> login to tester via three layers of Remote Desktop Connections -> run and debug code live on tester RDC The tester setup is virtually all GUI based. It’s also located on the other side of Asia which is the reason of logging in via RDC. Is there possibly a better way of making this workflow more contained in a terminal/single ide environment, without having to jump through the RDC loops?
I'm no networking wizard so this isn't really my area of expertise but I have a few thoughts and questions. Why do you need three layers of RDC? Is this due to networking constraints, where the ultimate server (I'll call it the prod server) you are trying to reach is unreachable from the internet directly? You might be able to tunnel into the server using ssh tunnels (see this guide [1]) through an intermediate server which your computer and the prod server both have access to, and then you'd be able to directly scp or rsync files to the server, as well as run commands over ssh, but this would be increasing your attack exposure from a security perspective, which folks may not be happy about since you're at a large engineering company.
A few questions that would help me give more actionable advice: What is the "tester" you're using? Is it essential to interact with it via a GUI or does it have a command line interface you would prefer to use? Is the OS Linux or Windows? What are the the three layers of RDC?
Feel free to email me at my hn username @gmail.com to discuss further since this is getting pretty specific to your setup! Sounds like a fun problem to try and solve :)
Since you seem to know what you’re talking about, I’m looking for some advice:
I work for a large and very well known engineering company and currently our incredibly terrible workflow looks something like this:
Develop locally using VStudio -> transfer repo to network drive -> login to tester via three layers of Remote Desktop Connections -> run and debug code live on tester RDC
The tester setup is virtually all GUI based. It’s also located on the other side of Asia which is the reason of logging in via RDC.
Is there possibly a better way of making this workflow more contained in a terminal/single ide environment, without having to jump through the RDC loops?
Is there a way to do your testing without a gui? I have no idea what your testing setup requires, but is there some technical reason why tests are not done automatically in your ci/cd pipeline?
If it must be done manually, can you just ssh/rdp directly into the testing box? The network where the testing box exists could use some tunneling protocol (stunnel, socks, wireguard, vpc peering...) to make it more accessible from your dev machine or your company VPN.
I had similar experiences but some layers are Citrix and others RDC. Seeing your situation brought back my anxiety on those connections.
Sorry for this. Is there any terminal servers to be able to ssh port forwarding? Thus to reduce layers, while as the test setup is gui based at least one layer of RDC is required. Reducing nested Remote Desktop would for sure help with the experience.
Sorry again for you situation.
Even those among us that have for years recognised the hypocrisy of the West in condemning practises in other countries which they themselves implement, this trial of Assange is so explicit in nature that it's quite unsettling. There was an understanding that this type of thing was a line that a liberal democratic Western nation simply would not cross.
>You don’t need to invade the US just to stop extraditions.
That's absolutely true. However the post that I responded to said nothing about extraditions.
Rather, it said:
>No government which supports this behavior, should be allowed to sit another democratic session.
Unless I'm having serious reading comprehension problems (which I suppose is possible), OP is suggesting the dissolution of the US Government. I merely asked how they thought that should be accomplished, then wished them luck.
You are having comprehensions. I was indeed referring to the nature of this article, which is Julian's heinous torture and rendition to the United States.
This isn't just 'extradition', any more.
The real free world, i.e. Europe, needs to stand up to this thuggery and do something about it, fast.
UK is showing itself incapable of catching this real attack on free society. With this precedent set - NOBODY is safe, not even one single civilian - to openly discuss the war crimes of our war industry.
Incorrect. After implementing a lockdown, and getting R<1, essentially brings you back to square one. That's when contact tracing is implemented and lockdown ends. The contact tracing will keep R<1 until a vaccine/better treatments/ICU's are implemented. A secondary lockdown might be needed in case people another outbreak occurs.
The feasibility of contact tracing has nothing to do with the R. It's practicality is purely based upon your ability to contact people who are infected.
Sure, tech tools that automate part of that process, increase that number - maybe even benefit more rural place - but if you launched it in NYC right now, it'll just notify literally everyone in the city, day one. That's not useful.
I don't know how you can fail to see how an organised and unified workforce will always benefit all workers in a firm. Pitting 'top performers' against the rest, scaremongering about 'lazy workers' etc. just divides the workforce and allows management/owners to exploit/underpay workers as a whole. The company would not be able to function/make as good a profit as it does without ALL workers contributing. If a worker truly is lazy/not pulling their weight, they get fired. A union doesn't stop that. A union is a unified voice for workers that can demand rightfully, better working conditions, better pay, better benefits.
This fiction that somehow tech workers should avoid unions because their pay is so well is utter corporate propaganda. The money won't always be this good people, especially as more and more are told to enter the industry. I know HackerNews is an entrepreneurial haven but it's funny to me how people here, with all their technical wisdom, are so blind to any benefits to workers and aversion to anything seen as 'socialist'.
>I don't know how you can fail to see how an organised and unified workforce will always benefit all workers in a firm.
Because historically it hasn't in the US. Unions end up implementing a seniority-based compensation/benefits scheme and there is nothing given to employees who outperform everyone else. This even fosters an environment where top performers are discouraged by their peers for "making everyone else look bad".
> This even fosters an environment where top performers are discouraged by their peers for "making everyone else look bad".
You don't need a union for this. Most large companies that do software (not the FAANGs, but the non-tech-first ones) generally don't know what to do with top performers, because consistency and predictability is more valuable to them. Especially a top performer who's bad at politics so they come off as attacking whole other departments or teams.
A union won't fix it, but probably won't make it worse, in those places.
Someone who comes off as attacking other departments or teams is probably a toxic individual to work with. Even if they crank out good code quickly, at some point senior engineers are expected to influence others, and attacking others is not conducive to that.
As for rewarding top performers, most places have annual or biannual reviews where people are given bonuses based on individual and company performance. The difference between underperforming and overperforming can be a lot of cash.
My god, all those links refer to Irish Americans. If anything, it shows that Americans hold grudges throughout generations. It's quite telling that an American conflates Irish-Americanism with being 'Irish'. The hyphen is there for a reason.
