Portal Guide - Home

Excerpt

The Modern Portal Project Is Complete! »

Sign Up for Site Manager Training »

LAN IDs, Employee IDs, and Responsibility Codes do not currently show in modern search on a person's profile card. Please use our specialized People Search Page or access the information in Delve.

The Portal is your default home page when you launch the Internet on your Duke Energy workstation. You can also access the Portal from your personal laptop or mobile device.

The Portal is a robust communication tool designed to be informative and engaging. On the home page, top company stories and employee features are posted frequently. The home page also contains media articles, company events, and personnel announcements. You are encouraged to add comments to articles and submit company-sponsored events and accomplishments.

The Portal also provides access to key transactional items such as company facts and branding, HR information (e.g., benefits and pay), policies, services (e.g., mail service and expense management), departments, operations, and other tools and applications.

Portal Site Managers

Brand, Creative & Digital

Contact & Personal Information

Contingent Worker Actions

COVID-19 Employee Resources

COVID-19 Manager Resources

Customer Experience & Services

PORTAL GUIDE

Manage Your Information

Delve profile pages exist for everyone with a LAN ID who is an employee of or contingent worker for Duke Energy.

Where did my profile information come from?

The organizational and location information in your Delve Portal profile comes from Active Directory.

This section of your Delve Profile is optional. You can choose to enter additional information about yourself, including:

• About me

• Home phone

• Projects

Filling in this information will help others find you when they're looking for someone with knowledge or experience about your areas of expertise, or it can help you connect with others who share your interests.

To edit this information, go to your and click the Update Profile button.

Manage Your Photo in Workday

Manage Your Photo in O365

Instructions for O365 Photos

When you go to Delve, click Me in the left navigation. Use the camera icon over your photo to change your picture. This will change it throughout the O365 environment, including Outlook, Teams, and SharePoint. Changing your photo here will not push it to Workday. Work is underway to enable the Workforce Photo Tool to integrate with O365.

Photo Guidelines

Your photo must be business-appropriate. That would be:

• A forward-facing, head-and-shoulders shot of you without sunglasses, ball cap, kids or family dog serves as a good starting point. Consider the limited space that will display your face when you select a photo. The goal is to see what you look like!

• Please follow copyright rules when selecting a photo to update. You must own rights to any image you post.

PORTAL GUIDE

Accessing the Portal Remotely

You can access the Portal from any computer or mobile device. You do not need to be on the Duke Energy network, and you do not need to use a Duke Energy computer or device that is in the Personal Mobile Device program.

From the SharePoint App

• You can download the SharePoint app from an app store. The home icon in the app takes you to the Portal homepage.

From a Mobile Browser

• Open your web browser (i.e., Edge, Chrome or a similar Web browser)

• Type in the address bar at the top of your Web browser and press Enter.

• If you are not on the network or on a device managed through the Personal Mobile Device program, you will need to log into your Office 365 account.

Keep in mind that some Duke Energy applications, are not available when you are off the network, and you will experience errors if you click links to them.

PORTAL GUIDE

Intranet Design Awards

The top ten intranets in the world, published annually by the Nielsen Norman Group. We purchase and publish these reports so that we can get a glimpse behind firewalls into the best practices with other companies. Duke Energy is a two-time winner.

PORTAL GUIDE

BitLocker keys for LAPTOP-9LGJ3JGS

• OPERATING SYSTEM DRIVEKey ID:\ f035f7c1-b011-4a97-ad86-a1e2b994037d\ Recovery key:\ 277827-520718-692857-678557-601997-238381-127116-121748

Code Reviews

• Created by Anonymous, last modified on Oct 08, 2020

"Everybody is junior at something", or so they say. You may be fairly early on in your career but have some experience working in a large enterprise or business where structured Code Reviews were the order of the day. Or you may have many years experience on a loose team that didn't really take Code Review very seriously. Thus, you may find that while you are a senior developer, you are "junior" (I honestly hate that term) when it comes to Code Reviews, and vice versa. Whatever the case, Ninja Turtles values Code Review. Let's talk about it.

The purpose of this document is to create a discussion from which we may create a kind of Working Agreement around Code Review on Ninja Turtles. It sets out to do so by addressing the following:

• The current state of our code review process

• Suggestions about moving forward

• How to improve at Code Reviews and PRs in general

State of the Code Review

The way that Ninja Turtles does Code Review is pretty much exclusively via Pull Requests; if you are a developer on Ninja Turtles, this is where most of your feedback will come from. At present, the most experienced of our team does most of the Code Review, and indeed it sometimes seems as though every PR is reviewed by 1 or 2 people, one of whom approves the PR before it is merged. Put simply, it's sort of the exemplification of the in action. For the purposes of this conversation, I will refer to the ones doing most of the reviewing as "the 20%" (following the adage that 80% of the work is done by 20% of the team) and the devs that are doing less of the reviewing as "the 80%". Obviously this is not exact, but you get the idea.

The goal should be to get all developers to the point where they're contributing (and receiving) a more equitable share of Code Review, rather than the current 80/20 divide.

Why Improve Code Review?

As noted above, Ninja Turtles is a team that benefits from a diversity of experience levels, but the natural consequence of this is that the developers with the most knowledge and experience with code review (the 20%) end up doing most of the code review. This stands to reason, and is actually quite normal, and probably beneficial. But it can be taxing for those devs doing the lion's share of the reviewing. It is a knife that cuts both ways; while those experienced devs may begin to feel resentment that the responsibility rests on them, the other devs feel inadequate, that they're not pulling their weight, or that they aren't given a fair chance to review before the stuff in their wheelhouse is "taken". Thus, everyone gets further entrenched in their respective roles. This is not great, but it's a problem that won't solve itself. It will require action as a team (more on this later).

But beyond that, there are several compelling reasons for us to improve on our Code Reviews.

1. From a development standpoint, Code Review is the least expensive way to catch mistakes.

2. Code Review provides opportunities to spread domain knowledge across the team, thereby preventing a complete reliance on trickle-down economics, er, knowledge.

3. Code Reviews can provide opportunities to learn, mentor, and teach.

"Effectiveness of code review for determining faults in software is between 30% and 35% more effective than standard unit testing"

• Steve McConnell, Code Complete

So, we understand the value of Code Review and we see a need to improve, but exactly how do we improve them?

Going Forward

I did a lot of reading and consulted some mentors to arrive at some of these conclusions. I will provide the resources I consulted below; I found them to be quite useful, and I encourage all who are interested to review them. After this, I propose a few changes. I will lay them out here and my hope is we can have a conversation about which changes we would like to adopt going forward and thus create something of a "Working Agreement" surrounding Code Reviews. Doing so obviously won't cause a miraculous change overnight, but I think implementing some of these suggestions is a good first step toward moving away from the 80/20 divide described above and getting everyone on the same level.

General suggestions:

• With two approvals now required to on a PR, perhaps it would make sense to rotate a more senior reviewer with a less senior reviewer or two (this would fall inline with guidelines I've seen) and let them tackle it independently. Ideally, they are both able to approve or provide feedback to the dev until they are ready to approve, but if not, after a certain period of time, the devs could come together and talk about why they are not feeling comfortable approving the PR.

• Maybe we should define our a little bit more clearly (currently, it has exactly one entry ) and we should definitely set up linting to enforce some of the simple things, such as consistent formatting. Devs should not be pushing up code that has completely preventable errors and reviewers should not be wasting precious cognitive energy on simple errors that can be caught by computers

Things to think about and maybe discuss:

• Expecting someone to get better at code reviews by simply looking at someone else's code just isn't a very good or efficient methodology. (See Jim Bird's article below). What can we do bridge that gap in a more proactive way? Perhaps some kind of structured "pair reviewing"?

• I touched on this above but another thing that Jim Bird suggests is keeping the number of reviewers small. In the long run, I see the value in having all the devs swarm it and knocking out a PR, but in the shorter term, it might make sense to slow down and focus on the quality over quantity and getting all devs up to around the same contribution level?

For the 20% currently doing 80% of the reviewing:

• Consider alternating PRs. Maybe everyone doesn't need to look at every PR, but a few people look at different ones?

  • Not sure what this would look like, but I'm sure it's doable.

• Step back. Don't be the first to review. Give some space to let some of the other devs (the 80%) step up. This will hopefully take a bit of the pressure off of you and lets the 80% leave the kind of feedback that may be easier for them to recognize as they level up their Code Review game.

For the 80%:

• for things you want to review. Below you'll find an overview of the kinds of things to look for.

• Step up.

• If we implement the changes suggested above, you will have some room to make some suggestions early on. But having the 20% step back only works if the 80% step up.

Sources:

Installing, Configuring, and Uninstalling Citrix Workspace on Chrome OS Devices

Contents

****

Installing Citrix Workspace on Chrome OS Devices ............................................................. 2

Configuring Citrix Workspace on Chrome OS Devices.......................................................... 3

Secondary configuration of Citrix Workspace on Chrome OS Devices…………………. 6

Uninstalling Citrix Workspace on Chrome OS Devices ......................................................... 9

\

Installing Citrix Workspace on Chrome OS Devices

1. On the Chrome OS device, open the Chrome Web Store and search for ‘Citrix Workspace’. Select ‘Citrix Workspace for Chrome OS’. Click Add to Chrome and Add App When prompted.

****

Configuring Citrix Workspace on Chrome OS Devices

****

1. Upon installation, click the Launcher Icon and then click the Citrix Workspace icon. You may need to click on All Apps to see the Citrix Workspace icon.

****

2. You will be prompted to enter a server address: Enter

****

3. Next, enter your Username, Password and your Passcode when prompted. Click Log On once you’ve finished entering your information.

NOTE:

• When using a physical key fob, your Passcode is your unique PIN + RSA token ID.

• When using a soft token, the PIN is not included as part of the Passcode.

4. The available Citrix applications and desktops should now appear as icons. You have successfully installed the Citrix Workspace software on your computer.

5. To launch a virtual desktop, select the Desktops tab at the bottom of the screen and select the assigned desktop. And to launch a virtual application, select the Apps tab at the bottom of the screen and select the application.

****

****

****

****

****

****

****

****

****

****

****

****

Secondary configuration of Citrix Workspace on Chrome OS Devices

****

****

NOTE: If you have not set up an authentication method in O365, by using this job aid , please do so BEFORE adding the Multifactor Authentication Citrix Portal URL

****

• • Be sure you set up a primary authentication method and a secondary authentication method.

****

o Choose your preferred primary authentication method from the drop-down box under “what’s your preferred option?”

****

1. Upon installation, click the Launcher Icon and then click the Citrix Workspace icon. You may need to click on All Apps to see the Citrix Workspace icon.

2. You will be prompted to enter a server address: Enter in order to setup the Citrix Portal that utilizes Multifactor Authentication. Afterwards, select Connect.

3. Next, enter your Username and Password when prompted. Click Log On once you’ve finished entering your information.

****

NOTE: You will be prompted to authenticate via the method that you setup within your Office 365 Authentication Profile:

· Via a call to a phone number you provided during setup (e.g., mobile phone number, secondary mobile phone number, or home phone number where you will be working)

· The Microsoft Authenticator application

****

****

4. To access your assigned virtual desktops or virtual applications, click either the DESKTOPS or APPS buttons at the top of the page.

****

Uninstalling Citrix Workspace on Chrome OS Devices

1. Open the Launcher (Magnifying glass) on your taskbar. Click the upward arrow to show all installed apps and locate the Citrix Workspace icon.

2. Right-click the Citrix Workspace Icon. If you are not using a mouse, then press the Alt key when you click on the Citrix Workspace icon to bring up the ‘right click’ menu options

3. Click Uninstall. Click Remove when asked to confirm removal.

****