vault backup: 2024-08-08 15:47:33

This commit is contained in:
2024-08-08 15:47:33 -05:00
parent 59d0938651
commit dc590594d2
492 changed files with 104 additions and 72 deletions

View File

@@ -0,0 +1,28 @@
Questions
- How are teams structured? Leads, with 4-9 engineers, focused around platform/tech
- Mobile team
- Web team
- All full stack
- Share
- On-call rotation, online services
- Backend e-commerce, backside to logos.com
- Internal tools, content production for datasets
- How are teams divided among projects? Web? Logos software? Mobile?
- Remote position permanently? Travel to home office?
- What is the QA process like?
- What are the best qualities of a Senior .NET dev to succeed?
- Reporting structure?
- Timelines?
- Remote works ok?
Alan palmer, hiring manager
100 devs
Teams into business units
30 devs on his team
Software for 20+ years
Opening office in pueblo, mx
Multi-stages to interview
Pairing session with engineer to solve some problem
Group interview

View File

@@ -0,0 +1,54 @@
Minesweeper implementation
- Default to 8x8 board with 10 mines
- Variables
- numRows
- numCols
- numMines
- Structs
- Squarestate
- hasFlag
- hasMine
- hidden
- Numneighboringmines
- For grid
- Multidimensional array of squarestates
- Setup
- Ask for num rows (default 8)
- Ask for num cols (default 8)
- Ask for num mines (make sure it's not more than num of squares)
- Q to quit
- F1,2 format for flag setting
- 1,2 for "opening" square
- Init array with rows and cols
- Use random to get col idx and row idx for mine until we reach number of mines
- As we do, increment neighbor mine counts
Summary
Your task is to implement the logic (not necessarily the GUI) of the classic Windows “Minesweeper” game.
Game Description
The game board is a rectangular grid; placed randomly within the grid are “mines”. (The grid size and number of mines are user-configurable but default to an 8×8 with 10 mines.)
Initially, all grid squares are “hidden”.
The player chooses one square at a time to “reveal”. If the square contains a mine, the player loses and the game is over.
Otherwise, the square is changed to show the total number of immediate neighbor squares (diagonal and orthogonal) that contain mines (with a maximum of 8). If no neighboring squares contain mines (i.e., the count for this square is 0), then all neighboring squares are automatically revealed. (And if one of those squares has no neighbors that are mines, then all its neighbors are automatically revealed, and so on.)
The player can choose to “flag” a square that they think might contain a mine. This has no impact on gameplay; it is just to help the player record their guesses.
When the player has revealed every non-mine square, they win.
Detailed Objectives
• Create data structures to represent an 8×8 grid
• Lay 10 mines in random locations
• For each square, calculate the total number of immediate neighbors that contain mines
• Display the board to the user (with all squares “hidden”)
o Note: This can use console/text mode UI if thats quicker
• Accept user input to reveal or flag a square
o If the square is a mine, the game is over
o If the square has non-zero mine neighbors, display its count
o If the square has zero mine neighbors, reveal all adjacent squares
• Repeat until the player has revealed all non-mine squares

View File

View File

@@ -0,0 +1,83 @@
Questions
- Righpoint
- Can you describe how Rightpoint likes to position itself for clients? Partner? Vendor? Most-valuable partner?
- What's the culture like at Rightpoint? How does this concept of "intrapeneur" play out?
- What's the pitch process like?
- Solutions architect
- Most important quality of a solutions architect to succeed at Rightpoint?
- What's the typical team structure for a project?
- How many projects is a solutions architect typically responsible for?
- How my freedom does a solutions architect have?
- Developers
- How much opportunity is given to developers to train and study for certification? - What's the covid-19 plan? Returning to offices soon? Permanently remote possible?
Preparation
- What Episerver commerce does well
- Flexibility to be shaped as you see fit
- Can totally work around it
- Extend it
- Pick pieces here and there
- Can stand alone for smaller solutions
- Can be integrated relatively easily with larger enterprises
- Clear that Episerver is paying attention to it, improving it tremendously
- Weaknesses of Episerver commerce
- Flexibility - not a Shopify solution a business stakeholder can setup
- Relatively few plugins
- Old UI
- Most important for team
- Communication
- Used to say communication, but that's too generic and unclear
- Ability to actively listen to clients and team members
- Understanding as others speak
- Asking clarifying questions
- Repeating to ensure understanding
- Accurately "go and do" based on what was said
- Wise risk-taking
- Don't be afraid to fail
- Know how to recover if you do
Notes:
- Drew
- Premier platinum partner with epi
- Bigger opportunities coming in
- Will love DXP
- Thomas john commerce practice lead
- Keith
- Aniket on keith's team, digops
- Aniket is keith's direct report
- Post implementation support, like Electrolux
- Joseph Lee is head of digops, keith on his team
- All of qa reports up through
- Dev team is 40 devs, half in us half in india
- Hasn't worked on epi
- Mostly Sharepoint dev in early days
- Genpact in the backend transformation busniess, were part of GE, spin off
- Bought rightpoint as digital experience company
- Good SA
- Raport with clients, have it, build it
- Comfortable with change
- Comfortable speaking to technology generally, not specifics, comfortable
- Fully remote definitely possible
- Joseph
- Leads digops unit
- Managed services--providing production support
- Lots of freedom to decide where to work, what to do

View File

@@ -0,0 +1,12 @@
Base salary 145000
Bonus typically 3-7%
Signus, switching to BlueCross
Vision
dental
401k, 2.5%, two year vesting
Vacation: flexible, not 10 weeks!
Any questions
Start classes every other Monday.

View File

@@ -0,0 +1,12 @@
| | | | | | | | |
|---|---|---|---|---|---|---|---|
|Accepting Rightpoint offer||||Staying at VML||||
|Pros|Weight|Cons|Weight|Pros|Weight|Cons|Weight|
|Salary increase|8|New people to meet|5|Familiar processes|6|No pay increase|3|
|Lots of work|10|Unknown exact job requirements|6|Familiar, good people|10|Uncertain work load future|7|
|Interesting colleagues|5|Less coding|5|Large company, probably solid|5|Un-inspiring boss|4|
|Grow in Episerver expertise|6|More client-facing|3|Potential to build Episerver practice and business|8|Liberal-minded company/employees|5|
|Promotion--more authority, influence|5|More travel|8|Potentially more time to do side projects, especially in the near term|10|||
|||Lose contact with VMLers (probably…not definite though)|1|||||
|||Switching insurance, 401k, etc|1|||||
||34||29||39||18|