Initial
This commit is contained in:
6
.gitignore
vendored
Normal file
6
.gitignore
vendored
Normal file
@@ -0,0 +1,6 @@
|
|||||||
|
# to exclude Obsidian's settings (including plugin and hotkey configurations)
|
||||||
|
.obsidian/
|
||||||
|
|
||||||
|
# Add below lines to exclude OS settings and caches
|
||||||
|
.trash/
|
||||||
|
.DS_Store
|
||||||
41
01-Daily/2026-01-14.md
Normal file
41
01-Daily/2026-01-14.md
Normal file
@@ -0,0 +1,41 @@
|
|||||||
|
---
|
||||||
|
date: 2026-01-14
|
||||||
|
tags: [daily]
|
||||||
|
mood:
|
||||||
|
energy-level:
|
||||||
|
---
|
||||||
|
|
||||||
|
# 2026-01-We
|
||||||
|
|
||||||
|
## 🎯 Today's Focus
|
||||||
|
- [ ] Setup Obsidian
|
||||||
|
- [ ] Setup Gitea in synology
|
||||||
|
- [ ] Prepare the LinkedIn update
|
||||||
|
|
||||||
|
## 💼 Job Hunting Activities
|
||||||
|
- Applications sent:
|
||||||
|
- Responses received:
|
||||||
|
- Interviews scheduled:
|
||||||
|
- Follow-ups needed:
|
||||||
|
|
||||||
|
## 📚 Learning & Development
|
||||||
|
- Studied:
|
||||||
|
- Practice:
|
||||||
|
|
||||||
|
## 💭 Reflections
|
||||||
|
### What went well
|
||||||
|
|
||||||
|
### Challenges
|
||||||
|
Struggle with regret.
|
||||||
|
|
||||||
|
### Tomorrow's priorities
|
||||||
|
|
||||||
|
|
||||||
|
## 🔗 Links
|
||||||
|
- Related jobs:
|
||||||
|
- Related skills:
|
||||||
|
|
||||||
|
---
|
||||||
|
**Mood Check-in**:
|
||||||
|
**Consulting hours logged**:
|
||||||
|
**Billable hours (80% → competency fund)**:
|
||||||
76
02-Jobs/Active/SEB Data Architect.md
Normal file
76
02-Jobs/Active/SEB Data Architect.md
Normal file
@@ -0,0 +1,76 @@
|
|||||||
|
---
|
||||||
|
company: SEB
|
||||||
|
position: Data Architect
|
||||||
|
applied-date: 2024-12
|
||||||
|
status: rejected
|
||||||
|
priority: high
|
||||||
|
tags: [job-application, seb, data-architect]
|
||||||
|
broker: TBD
|
||||||
|
---
|
||||||
|
|
||||||
|
# SEB - Data Architect
|
||||||
|
|
||||||
|
## 📋 Overview
|
||||||
|
**Job URL**:
|
||||||
|
**Broker**: (Check with Henrik)
|
||||||
|
**Contact Person**:
|
||||||
|
**Applied**: December 2024
|
||||||
|
**Interview**: Completed - did not go well
|
||||||
|
**Status**: Waiting for final response
|
||||||
|
|
||||||
|
## 🎯 Position Match Analysis
|
||||||
|
### Requirements Match
|
||||||
|
- **Technical Skills**: 8/10 - Strong database and architecture background
|
||||||
|
- **Domain Knowledge**: 7/10 - Financial services experience
|
||||||
|
- **Modern Data Terminology**: 4/10 - **This was the problem**
|
||||||
|
- **Overall Fit**: 6/10
|
||||||
|
|
||||||
|
### Key Requirements
|
||||||
|
- [x] Database architecture expertise
|
||||||
|
- [x] Financial services experience
|
||||||
|
- [ ] Data Mesh understanding - **weak articulation**
|
||||||
|
- [ ] Data Governance knowledge - **conceptual only**
|
||||||
|
- [ ] Data Mart design - **not well communicated**
|
||||||
|
|
||||||
|
### My Strengths for This Role
|
||||||
|
1. 25+ years SQL Server expertise
|
||||||
|
2. Financial services domain (TCM, AbaSec)
|
||||||
|
3. Azure cloud architecture
|
||||||
|
4. Integration architecture
|
||||||
|
|
||||||
|
### Gaps That Hurt Me
|
||||||
|
- **Terminology gap**: Understood concepts but couldn't articulate in modern "data architect lingo"
|
||||||
|
- **Data Mesh**: Knew the concepts but couldn't discuss fluently
|
||||||
|
- **Preparation**: Should have studied terminology more before interview
|
||||||
|
|
||||||
|
## 💭 Interview Reflection
|
||||||
|
|
||||||
|
### What Went Wrong
|
||||||
|
- Struggled to articulate experience using modern data architecture terminology
|
||||||
|
- Data Mesh, Data Governance concepts - I understand them but couldn't speak the language
|
||||||
|
- Interviewer probably thought I lacked current knowledge
|
||||||
|
- Should have prepared more on translating my experience to their vocabulary
|
||||||
|
|
||||||
|
### What I Learned
|
||||||
|
- **Critical lesson**: Technical ability ≠ Interview ability
|
||||||
|
- Need to **study terminology** for data architect positions
|
||||||
|
- My experience is relevant - I just need to **translate it**
|
||||||
|
- Should have reviewed: Data Mesh, Data Fabric, Data Catalog, Data Governance frameworks
|
||||||
|
|
||||||
|
### If I Could Do It Again
|
||||||
|
1. Study modern data architecture terminology for 1-2 weeks
|
||||||
|
2. Practice translating my projects into Data Mesh concepts
|
||||||
|
3. Prepare examples of data governance from TCM work
|
||||||
|
4. Map my AbasecGateway work to modern patterns
|
||||||
|
|
||||||
|
## 🎓 Action Items for Future Similar Roles
|
||||||
|
- [ ] Complete Data Mesh learning module
|
||||||
|
- [ ] Study Data Governance frameworks
|
||||||
|
- [ ] Create translation guide: My experience → Modern terms
|
||||||
|
- [ ] Practice interview answers with new terminology
|
||||||
|
- [ ] Create "SEB post-mortem learning note"
|
||||||
|
|
||||||
|
## 🔗 Related
|
||||||
|
- Learning needed: [[Data Mesh]], [[Data Governance]], [[Modern Data Architecture Terminology]]
|
||||||
|
- Similar roles: Watch for more Data Architect positions
|
||||||
|
- Profile: [[Data Architect Profile]] - needs update with terminology
|
||||||
72
02-Jobs/Pipeline/Svenska Kraftnät .NET Developer.md
Normal file
72
02-Jobs/Pipeline/Svenska Kraftnät .NET Developer.md
Normal file
@@ -0,0 +1,72 @@
|
|||||||
|
---
|
||||||
|
company: Svenska Kraftnät
|
||||||
|
position: .NET Developer
|
||||||
|
applied-date: 2025-01-recent
|
||||||
|
status: submitted
|
||||||
|
priority: high
|
||||||
|
tags: [job-application, svenska-kraftnat, dotnet]
|
||||||
|
broker: TBD
|
||||||
|
---
|
||||||
|
|
||||||
|
# Svenska Kraftnät - .NET Developer
|
||||||
|
|
||||||
|
## 📋 Overview
|
||||||
|
**Job URL**:
|
||||||
|
**Broker**:
|
||||||
|
**Contact Person**:
|
||||||
|
**Applied**: Recently (early January 2025)
|
||||||
|
**Status**: Waiting for response
|
||||||
|
|
||||||
|
## 🎯 Position Match Analysis
|
||||||
|
### Requirements Match
|
||||||
|
- **Backend .NET**: 10/10 - Perfect fit
|
||||||
|
- **SQL Server**: 10/10 - Perfect fit
|
||||||
|
- **Azure**: 10/10 - Strong experience
|
||||||
|
- **ReactJS**: 3/10 - **Only gap**
|
||||||
|
- **Overall Fit**: 9/10 - Nearly perfect
|
||||||
|
|
||||||
|
### Key Requirements
|
||||||
|
- [x] .NET development - **Expert**
|
||||||
|
- [x] SQL Server - **25+ years**
|
||||||
|
- [x] Azure cloud - **Strong**
|
||||||
|
- [x] Backend architecture - **Strong**
|
||||||
|
- [ ] ReactJS - **Gap: We used Angular, not much UI work**
|
||||||
|
|
||||||
|
### My Strengths for This Role
|
||||||
|
1. **Perfect backend match**: .NET, SQL Server, Azure are my core
|
||||||
|
2. **Architecture experience**: Microservices, Clean Architecture
|
||||||
|
3. **Full pipeline experience**: CI/CD, DevOps
|
||||||
|
4. **Senior level**: Can lead and mentor
|
||||||
|
|
||||||
|
### The React Gap
|
||||||
|
- **Reality**: Haven't worked with React specifically
|
||||||
|
- **Related**: Have Angular experience from Tieto
|
||||||
|
- **UI work**: Limited - more backend focused
|
||||||
|
- **Mitigation**: Fast learner, modern frameworks share concepts
|
||||||
|
- **Plan**: Start React learning immediately
|
||||||
|
|
||||||
|
## 🎓 Preparation Plan
|
||||||
|
|
||||||
|
### React Learning Path
|
||||||
|
- [ ] Complete React fundamentals course (Udemy/Pluralsight)
|
||||||
|
- [ ] Build small React app with .NET backend
|
||||||
|
- [ ] Study React + .NET Web API integration
|
||||||
|
- [ ] Prepare to discuss: "I haven't used React in production but have Angular experience and am actively learning React"
|
||||||
|
|
||||||
|
### Interview Preparation
|
||||||
|
- [ ] Prepare backend architecture examples
|
||||||
|
- [ ] SQL Server optimization war stories
|
||||||
|
- [ ] Azure architecture decisions
|
||||||
|
- [ ] Team collaboration examples
|
||||||
|
- [ ] Address React gap honestly but positively
|
||||||
|
|
||||||
|
## 💬 React Gap Talking Points
|
||||||
|
|
||||||
|
**Honest approach**:
|
||||||
|
"I haven't worked with React in production. At Tieto we used Angular for our frontend work, though my primary focus was backend architecture. I understand React's component model and have started learning it because I see it's the industry standard. My strength is backend .NET and SQL Server, which is 90% of this role, and I'm confident I can pick up React quickly given my Angular background and general frontend understanding."
|
||||||
|
|
||||||
|
## 🔗 Related
|
||||||
|
- Profile: [[Backend Developer Profile]]
|
||||||
|
- Skills: [[.NET]], [[SQL Server]], [[Azure]]
|
||||||
|
- Learning: [[React Fundamentals]] - **START ASAP**
|
||||||
|
- Projects: [[AbasecGateway Project]] - great example
|
||||||
47
02-Jobs/Pipeline/Vattenfall ML Architect.md
Normal file
47
02-Jobs/Pipeline/Vattenfall ML Architect.md
Normal file
@@ -0,0 +1,47 @@
|
|||||||
|
---
|
||||||
|
company: Vattenfall
|
||||||
|
position: Architect - ML Initiative
|
||||||
|
applied-date: 2024-12
|
||||||
|
status: submitted
|
||||||
|
priority: high
|
||||||
|
tags: [job-application, vattenfall, ml-architect]
|
||||||
|
broker: TBD
|
||||||
|
---
|
||||||
|
|
||||||
|
# Vattenfall - Architect for ML Initiative
|
||||||
|
|
||||||
|
## 📋 Overview
|
||||||
|
**Job URL**:
|
||||||
|
**Broker**: (Check with Henrik)
|
||||||
|
**Contact Person**:
|
||||||
|
**Applied**: December 2024
|
||||||
|
**Status**: Waiting for response - Vattenfall known for slow process
|
||||||
|
**Expected Timeline**: Unknown
|
||||||
|
|
||||||
|
## 🎯 Position Match Analysis
|
||||||
|
### Initial Assessment
|
||||||
|
- **Architecture Experience**: Strong fit
|
||||||
|
- **Azure Cloud**: Strong fit
|
||||||
|
- **ML Architecture**: Need to learn specifics
|
||||||
|
- **Overall Fit**: TBD - depends on role details
|
||||||
|
|
||||||
|
### My Questions
|
||||||
|
- What level of ML expertise expected?
|
||||||
|
- More architecture role or ML engineering?
|
||||||
|
- Team structure and stakeholders?
|
||||||
|
|
||||||
|
## 📝 Follow-up Actions
|
||||||
|
- [ ] Check with Henrik on status
|
||||||
|
- [ ] Research Vattenfall's ML initiatives (if public)
|
||||||
|
- [ ] Prepare for potential interview
|
||||||
|
|
||||||
|
## 🎓 Preparation Needed
|
||||||
|
- [ ] Study MLOps patterns
|
||||||
|
- [ ] Azure ML services review
|
||||||
|
- [ ] Model deployment architectures
|
||||||
|
- [ ] ML governance and monitoring
|
||||||
|
|
||||||
|
## 🔗 Related
|
||||||
|
- Profile: [[Technical Architect Profile]]
|
||||||
|
- Skills: [[Azure]], [[Architecture Patterns]]
|
||||||
|
- Learning: [[MLOps Basics]]
|
||||||
109
04-Skills/Skills Inventory.md
Normal file
109
04-Skills/Skills Inventory.md
Normal file
@@ -0,0 +1,109 @@
|
|||||||
|
---
|
||||||
|
tags: [skills, inventory]
|
||||||
|
---
|
||||||
|
|
||||||
|
# Skills Inventory
|
||||||
|
|
||||||
|
## 🎯 Core Strengths (Expert Level)
|
||||||
|
|
||||||
|
### Databases & Data Architecture
|
||||||
|
- [[SQL Server]] - 25+ years, deep expertise
|
||||||
|
- Database design & optimization
|
||||||
|
- Data warehouse architecture
|
||||||
|
- Performance tuning
|
||||||
|
|
||||||
|
### Development
|
||||||
|
- [[.NET Framework & .NET Core]]
|
||||||
|
- [[C# Development]]
|
||||||
|
- [[REST API Design]]
|
||||||
|
- Microservices architecture
|
||||||
|
|
||||||
|
### Cloud & DevOps
|
||||||
|
- [[Azure Services]]
|
||||||
|
- CI/CD pipelines
|
||||||
|
- Azure DevOps
|
||||||
|
- Infrastructure as Code
|
||||||
|
|
||||||
|
### Enterprise Architecture
|
||||||
|
- Clean Architecture patterns
|
||||||
|
- Domain-Driven Design
|
||||||
|
- Integration patterns
|
||||||
|
- Legacy system modernization
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 📚 Currently Learning
|
||||||
|
|
||||||
|
### Data Architecture Modern Concepts
|
||||||
|
- [[Data Mesh]] - Need stronger grasp
|
||||||
|
- [[Data Governance]] - Understanding concepts
|
||||||
|
- [[Data Marts]] - Practical implementation
|
||||||
|
- Modern data architecture terminology
|
||||||
|
|
||||||
|
### Frontend Development
|
||||||
|
- [[React]] - For Svenska Kraftnät opportunity
|
||||||
|
- Modern JavaScript frameworks
|
||||||
|
- (Note: Have Angular experience but not recent)
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 🔧 Technologies by Category
|
||||||
|
|
||||||
|
### Microsoft Stack
|
||||||
|
- SQL Server (Expert)
|
||||||
|
- .NET Framework (Expert)
|
||||||
|
- .NET Core/.NET 8 (Advanced)
|
||||||
|
- Azure (Advanced)
|
||||||
|
- Power BI (Intermediate)
|
||||||
|
|
||||||
|
### Development Tools
|
||||||
|
- Azure DevOps
|
||||||
|
- Git
|
||||||
|
- Visual Studio
|
||||||
|
- SQL Server Management Studio
|
||||||
|
|
||||||
|
### Architecture & Patterns
|
||||||
|
- REST APIs
|
||||||
|
- Microservices
|
||||||
|
- Clean Architecture
|
||||||
|
- Domain-Driven Design
|
||||||
|
- SOLID principles
|
||||||
|
|
||||||
|
### Integration & Middleware
|
||||||
|
- REST API gateways
|
||||||
|
- Message queues
|
||||||
|
- Service buses
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 💼 Industry Domains
|
||||||
|
- Financial Services (Strong - TCM, AbaSec)
|
||||||
|
- Fund Management Systems
|
||||||
|
- Securities/Equities Trading Systems
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 🎯 Skills Gap Analysis
|
||||||
|
|
||||||
|
### For Data Architect Roles (e.g., SEB)
|
||||||
|
**Strong**: Database expertise, architecture, Azure
|
||||||
|
**Gap**: Modern data terminology, Data Mesh articulation
|
||||||
|
**Action**: Study Data Mesh, Data Fabric, modern data governance
|
||||||
|
|
||||||
|
### For ML/AI Architect Roles (e.g., Vattenfall)
|
||||||
|
**Strong**: Architecture patterns, Azure, .NET
|
||||||
|
**Gap**: ML-specific architecture patterns
|
||||||
|
**Action**: Study MLOps, model deployment patterns
|
||||||
|
|
||||||
|
### For Full-Stack/.NET Roles (e.g., Svenska Kraftnät)
|
||||||
|
**Strong**: Backend, .NET, SQL, Azure
|
||||||
|
**Gap**: React (they mention ReactJS)
|
||||||
|
**Action**: Complete React fundamentals course
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 🔗 Next Steps
|
||||||
|
- [ ] Create detailed note for each core skill
|
||||||
|
- [ ] Document projects that demonstrate each skill
|
||||||
|
- [ ] Create learning plans for gap areas
|
||||||
|
- [ ] Map skills to target job profiles
|
||||||
133
05-Projects/Tieto Experience Summary.md
Normal file
133
05-Projects/Tieto Experience Summary.md
Normal file
@@ -0,0 +1,133 @@
|
|||||||
|
---
|
||||||
|
company: TietoEVRY
|
||||||
|
duration: 2016-2025
|
||||||
|
tags: [career-history, tieto]
|
||||||
|
---
|
||||||
|
|
||||||
|
# TietoEVRY Experience Summary (2016-2025)
|
||||||
|
|
||||||
|
## 📅 Timeline Overview
|
||||||
|
**Total Duration**: ~9 years (2016-2025)
|
||||||
|
**Departments**: Funds (majority), Equities (final year)
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 🎯 Major Roles & Responsibilities
|
||||||
|
|
||||||
|
### Database Developer (Funds - Early Years)
|
||||||
|
**Focus**: Implementing features, microservice architecture
|
||||||
|
|
||||||
|
**Key Projects**:
|
||||||
|
- Feature development for TCM/TCM Lite products
|
||||||
|
- Microservices architecture implementation
|
||||||
|
- Database design and optimization
|
||||||
|
|
||||||
|
**Technologies**: SQL Server, .NET, Azure
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
### Senior Developer/Architect (Funds - Mid Years)
|
||||||
|
**Focus**: REST API layer, architecture transformation
|
||||||
|
|
||||||
|
**Key Project: AbasecGateway**
|
||||||
|
- **Problem**: Legacy AbaSec database needed modern API layer
|
||||||
|
- **Solution**: Designed and implemented REST API gateway
|
||||||
|
- **Responsibilities**:
|
||||||
|
- Architecture design
|
||||||
|
- Cross-cutting concerns (logging, metrics, OpenID auth)
|
||||||
|
- CI/CD pipeline creation
|
||||||
|
- Full end-to-end deployment pipeline to production
|
||||||
|
|
||||||
|
**Technologies**: .NET, REST APIs, Azure DevOps, OpenID Connect
|
||||||
|
|
||||||
|
**Duration**: ~2 years
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
### ToolSmiths Team (Equities - Final Year)
|
||||||
|
**Focus**: Version control and build/deploy tools maintenance
|
||||||
|
|
||||||
|
**Context**:
|
||||||
|
- Moved from Funds to Equities organization
|
||||||
|
- Team responsible for legacy tooling
|
||||||
|
- Many original developers had left
|
||||||
|
|
||||||
|
**Challenges**:
|
||||||
|
- Unfamiliar with much of the legacy AbaSec tooling
|
||||||
|
- Supporting junior colleagues constantly
|
||||||
|
- Felt increasingly stuck and stressed
|
||||||
|
- Knowledge drain as experienced people left
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 🏆 Major Achievements
|
||||||
|
|
||||||
|
### AbasecGateway Project
|
||||||
|
- ✅ Modern REST API layer on legacy system
|
||||||
|
- ✅ Complete CI/CD pipeline
|
||||||
|
- ✅ End-to-end testing framework
|
||||||
|
- ✅ Production deployment system
|
||||||
|
- ✅ Authentication/authorization implementation
|
||||||
|
- ✅ Comprehensive logging and metrics
|
||||||
|
|
||||||
|
### Architecture & Technical Leadership
|
||||||
|
- ✅ Clean Architecture transformations
|
||||||
|
- ✅ Microservices design patterns
|
||||||
|
- ✅ Azure cloud migrations
|
||||||
|
- ✅ DevOps practices implementation
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 📉 Product Context
|
||||||
|
- **TCM/TCM Lite**: Fund management products in decline
|
||||||
|
- **Customer attrition**: Multiple customers leaving platform
|
||||||
|
- **Market pressure**: Changing industry landscape
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 💭 Reasons for Leaving
|
||||||
|
|
||||||
|
### Primary Factors
|
||||||
|
1. **Role Mismatch**: Move to ToolSmiths felt like step backward
|
||||||
|
- More legacy maintenance than innovation
|
||||||
|
- Less architectural work
|
||||||
|
- Supporting vs leading
|
||||||
|
|
||||||
|
2. **Stress & Feeling Stuck**:
|
||||||
|
- Constant support of junior developers
|
||||||
|
- Unfamiliar legacy systems
|
||||||
|
- Knowledge gaps from departed colleagues
|
||||||
|
|
||||||
|
3. **Life Event Catalyst**:
|
||||||
|
- Former Sybase colleague passed away (September)
|
||||||
|
- Reflection on career at age 55
|
||||||
|
- Desire to try consulting while still able
|
||||||
|
|
||||||
|
4. **Product Decline**:
|
||||||
|
- Funds product losing customers
|
||||||
|
- Uncertainty about long-term prospects
|
||||||
|
|
||||||
|
### Regrets & Reflections
|
||||||
|
- **Regret**: Didn't communicate stress to manager (Patrik Svensson) sooner
|
||||||
|
- **Wonder**: Could issues have been resolved with better communication?
|
||||||
|
- **Recognition**: May have acted hastily due to stress
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 🎓 Skills Developed
|
||||||
|
- SQL Server architecture and optimization
|
||||||
|
- .NET development (various versions)
|
||||||
|
- REST API design
|
||||||
|
- Microservices architecture
|
||||||
|
- Azure cloud services
|
||||||
|
- CI/CD pipeline design
|
||||||
|
- DevOps practices
|
||||||
|
- Team leadership
|
||||||
|
- Cross-cutting concerns design
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 🔗 Related
|
||||||
|
- Projects to document in detail: [[AbasecGateway Project]], [[TCM Microservices]]
|
||||||
|
- Skills to emphasize: [[SQL Server]], [[.NET]], [[Azure]], [[REST APIs]]
|
||||||
|
- Interview talking points: [[Why I Left Tieto]]
|
||||||
36
07-Templates/Company.md
Normal file
36
07-Templates/Company.md
Normal file
@@ -0,0 +1,36 @@
|
|||||||
|
---
|
||||||
|
company-name:
|
||||||
|
industry:
|
||||||
|
tags: [company]
|
||||||
|
---
|
||||||
|
|
||||||
|
# {{company-name}}
|
||||||
|
|
||||||
|
## 📋 Basic Info
|
||||||
|
**Industry**:
|
||||||
|
**Size**:
|
||||||
|
**Headquarters**:
|
||||||
|
**Founded**:
|
||||||
|
**Website**:
|
||||||
|
|
||||||
|
## 💼 Business Model
|
||||||
|
|
||||||
|
|
||||||
|
## 🛠️ Tech Stack
|
||||||
|
Known technologies they use:
|
||||||
|
-
|
||||||
|
-
|
||||||
|
|
||||||
|
## 📰 Recent News
|
||||||
|
-
|
||||||
|
-
|
||||||
|
|
||||||
|
## 👥 Culture Notes
|
||||||
|
|
||||||
|
|
||||||
|
## 🎯 Why I'm Interested
|
||||||
|
|
||||||
|
|
||||||
|
## 🔗 Related
|
||||||
|
- Job applications:
|
||||||
|
- Contacts:
|
||||||
37
07-Templates/Daily Note.md
Normal file
37
07-Templates/Daily Note.md
Normal file
@@ -0,0 +1,37 @@
|
|||||||
|
---
|
||||||
|
date: {{date}}
|
||||||
|
tags: [daily]
|
||||||
|
mood:
|
||||||
|
energy-level:
|
||||||
|
---
|
||||||
|
|
||||||
|
# {{date: YYYY-MM-dd}}
|
||||||
|
|
||||||
|
## 🎯 Today's Focus
|
||||||
|
- [ ]
|
||||||
|
|
||||||
|
## 💼 Job Hunting Activities
|
||||||
|
- Applications sent:
|
||||||
|
- Responses received:
|
||||||
|
- Interviews scheduled:
|
||||||
|
- Follow-ups needed:
|
||||||
|
|
||||||
|
## 📚 Learning & Development
|
||||||
|
- Studied:
|
||||||
|
- Practice:
|
||||||
|
|
||||||
|
## 💭 Reflections
|
||||||
|
### What went well
|
||||||
|
|
||||||
|
### Challenges
|
||||||
|
|
||||||
|
### Tomorrow's priorities
|
||||||
|
|
||||||
|
## 🔗 Links
|
||||||
|
- Related jobs:
|
||||||
|
- Related skills:
|
||||||
|
|
||||||
|
---
|
||||||
|
**Mood Check-in**:
|
||||||
|
**Consulting hours logged**:
|
||||||
|
**Billable hours (80% → competency fund)**:
|
||||||
83
07-Templates/Job Application.md
Normal file
83
07-Templates/Job Application.md
Normal file
@@ -0,0 +1,83 @@
|
|||||||
|
---
|
||||||
|
company:
|
||||||
|
position:
|
||||||
|
applied-date:
|
||||||
|
status: draft
|
||||||
|
priority: medium
|
||||||
|
tags: [job-application]
|
||||||
|
broker:
|
||||||
|
---
|
||||||
|
|
||||||
|
# {{company}} - {{position}}
|
||||||
|
|
||||||
|
## 📋 Overview
|
||||||
|
**Job URL**:
|
||||||
|
**Broker**: ework/magnit/itx/direct
|
||||||
|
**Contact Person**:
|
||||||
|
**Deadline**:
|
||||||
|
**Expected Start**:
|
||||||
|
|
||||||
|
## 🎯 Position Match Analysis
|
||||||
|
### Requirements Match
|
||||||
|
- **Technical Skills**: /10
|
||||||
|
- **Domain Knowledge**: /10
|
||||||
|
- **Soft Skills**: /10
|
||||||
|
- **Overall Fit**: /10
|
||||||
|
|
||||||
|
### Key Requirements
|
||||||
|
- [ ] Requirement 1
|
||||||
|
- [ ] Requirement 2
|
||||||
|
- [ ] Requirement 3
|
||||||
|
|
||||||
|
### My Strengths for This Role
|
||||||
|
1.
|
||||||
|
2.
|
||||||
|
3.
|
||||||
|
|
||||||
|
### Gaps/Learning Needed
|
||||||
|
-
|
||||||
|
|
||||||
|
## 📝 Application Materials
|
||||||
|
**Profile Used**: [[Profile Name]]
|
||||||
|
**CV Version**:
|
||||||
|
**Cover Letter**:
|
||||||
|
**Submitted Date**:
|
||||||
|
|
||||||
|
## 🗣️ Interview Prep
|
||||||
|
### Company Research
|
||||||
|
- **Business model**:
|
||||||
|
- **Tech stack**:
|
||||||
|
- **Recent news**:
|
||||||
|
- **Culture notes**:
|
||||||
|
- **Size/structure**:
|
||||||
|
|
||||||
|
### Likely Questions
|
||||||
|
1. Tell me about your experience with...
|
||||||
|
2. Why are you leaving Tieto?
|
||||||
|
3. What interests you about this role?
|
||||||
|
|
||||||
|
### My Questions for Them
|
||||||
|
1. What does success look like in this role?
|
||||||
|
2. What's the team structure?
|
||||||
|
3. What are the biggest technical challenges?
|
||||||
|
4. Development/learning opportunities?
|
||||||
|
|
||||||
|
## 📅 Timeline
|
||||||
|
| Date | Event | Notes |
|
||||||
|
|------|-------|-------|
|
||||||
|
| | | |
|
||||||
|
|
||||||
|
## 💭 Post-Interview Reflections
|
||||||
|
### What went well
|
||||||
|
|
||||||
|
### What could improve
|
||||||
|
|
||||||
|
### Follow-up actions
|
||||||
|
- [ ] Thank you email
|
||||||
|
- [ ] Additional materials
|
||||||
|
- [ ] Check-in date
|
||||||
|
|
||||||
|
## 🔗 Related
|
||||||
|
- Similar roles:
|
||||||
|
- Skills to highlight:
|
||||||
|
- Projects to mention:
|
||||||
59
07-Templates/Profile.md
Normal file
59
07-Templates/Profile.md
Normal file
@@ -0,0 +1,59 @@
|
|||||||
|
---
|
||||||
|
profile-name:
|
||||||
|
primary-focus:
|
||||||
|
tags: [profile]
|
||||||
|
---
|
||||||
|
|
||||||
|
# {{profile-name}} Profile
|
||||||
|
|
||||||
|
## 🎯 Target Roles
|
||||||
|
-
|
||||||
|
-
|
||||||
|
|
||||||
|
## 💪 Core Value Proposition
|
||||||
|
*The 2-3 sentence pitch*
|
||||||
|
|
||||||
|
|
||||||
|
## 🛠️ Key Skills Emphasis
|
||||||
|
### Primary
|
||||||
|
- [[Skill 1]]
|
||||||
|
- [[Skill 2]]
|
||||||
|
- [[Skill 3]]
|
||||||
|
|
||||||
|
### Supporting
|
||||||
|
-
|
||||||
|
-
|
||||||
|
|
||||||
|
## 📊 Relevant Experience Highlights
|
||||||
|
### Project 1:
|
||||||
|
**Context**:
|
||||||
|
**My Role**:
|
||||||
|
**Impact**:
|
||||||
|
**Technologies**:
|
||||||
|
**Duration**:
|
||||||
|
|
||||||
|
### Project 2:
|
||||||
|
**Context**:
|
||||||
|
**My Role**:
|
||||||
|
**Impact**:
|
||||||
|
**Technologies**:
|
||||||
|
**Duration**:
|
||||||
|
|
||||||
|
## 🎓 Learning Path
|
||||||
|
Current focus areas for this profile:
|
||||||
|
- [ ]
|
||||||
|
- [ ]
|
||||||
|
|
||||||
|
## 📄 CV Variations
|
||||||
|
- [[CV - Version name]]
|
||||||
|
|
||||||
|
## 🗣️ Elevator Pitch
|
||||||
|
### 30 seconds
|
||||||
|
|
||||||
|
|
||||||
|
### 2 minutes
|
||||||
|
|
||||||
|
|
||||||
|
## 🔗 Related
|
||||||
|
- Jobs using this profile:
|
||||||
|
- Skills to develop:
|
||||||
42
07-Templates/Project.md
Normal file
42
07-Templates/Project.md
Normal file
@@ -0,0 +1,42 @@
|
|||||||
|
---
|
||||||
|
project-name:
|
||||||
|
company:
|
||||||
|
duration:
|
||||||
|
role:
|
||||||
|
tags: [project]
|
||||||
|
---
|
||||||
|
|
||||||
|
# {{project-name}}
|
||||||
|
|
||||||
|
## 📋 Overview
|
||||||
|
**Company**:
|
||||||
|
**Duration**:
|
||||||
|
**Team size**:
|
||||||
|
**My role**:
|
||||||
|
|
||||||
|
## 🎯 Problem/Challenge
|
||||||
|
|
||||||
|
|
||||||
|
## 💡 Solution
|
||||||
|
|
||||||
|
|
||||||
|
## 🛠️ Technologies Used
|
||||||
|
-
|
||||||
|
-
|
||||||
|
|
||||||
|
## 📊 Impact/Results
|
||||||
|
-
|
||||||
|
-
|
||||||
|
|
||||||
|
## 🎓 What I Learned
|
||||||
|
|
||||||
|
|
||||||
|
## 💬 Sound Bites for Interviews
|
||||||
|
*Short, memorable ways to describe this project*
|
||||||
|
|
||||||
|
1.
|
||||||
|
2.
|
||||||
|
|
||||||
|
## 🔗 Related
|
||||||
|
- Skills demonstrated:
|
||||||
|
- Similar projects:
|
||||||
41
07-Templates/Skill.md
Normal file
41
07-Templates/Skill.md
Normal file
@@ -0,0 +1,41 @@
|
|||||||
|
---
|
||||||
|
skill:
|
||||||
|
category: core/learning/emerging
|
||||||
|
proficiency: beginner/intermediate/advanced/expert
|
||||||
|
tags: [skill]
|
||||||
|
last-used:
|
||||||
|
---
|
||||||
|
|
||||||
|
# {{skill}}
|
||||||
|
|
||||||
|
## 📈 Current Level
|
||||||
|
**Self-assessment**: /10
|
||||||
|
**Market demand**: high/medium/low
|
||||||
|
**Priority for roles**:
|
||||||
|
**Years of experience**:
|
||||||
|
|
||||||
|
## 📚 Learning Resources
|
||||||
|
- [ ] Resource 1
|
||||||
|
- [ ] Resource 2
|
||||||
|
- [ ] Resource 3
|
||||||
|
|
||||||
|
## 💼 Where I've Used This
|
||||||
|
- [[Project 1]] - Brief description
|
||||||
|
- [[Job at Company]] - Brief description
|
||||||
|
|
||||||
|
## 🎯 Development Plan
|
||||||
|
### Short-term (1-3 months)
|
||||||
|
- [ ]
|
||||||
|
- [ ]
|
||||||
|
|
||||||
|
### Long-term (3-6 months)
|
||||||
|
- [ ]
|
||||||
|
- [ ]
|
||||||
|
|
||||||
|
## 📝 Notes & Examples
|
||||||
|
|
||||||
|
|
||||||
|
## 🔗 Related
|
||||||
|
- Complementary skills:
|
||||||
|
- Jobs requiring this:
|
||||||
|
- Projects to showcase:
|
||||||
58
07-Templates/Weekly Reflection.md
Normal file
58
07-Templates/Weekly Reflection.md
Normal file
@@ -0,0 +1,58 @@
|
|||||||
|
---
|
||||||
|
week:
|
||||||
|
year:
|
||||||
|
tags: [reflection, weekly]
|
||||||
|
---
|
||||||
|
|
||||||
|
# Week {{week}} - {{year}}
|
||||||
|
|
||||||
|
## 📊 Week Overview
|
||||||
|
**Mood trajectory**: ⬆️ / ➡️ / ⬇️
|
||||||
|
**Energy levels**: High / Medium / Low
|
||||||
|
**Overall rating**: /10
|
||||||
|
|
||||||
|
## 💼 Job Search Progress
|
||||||
|
### Applications This Week
|
||||||
|
- **Total sent**:
|
||||||
|
- **Responses received**:
|
||||||
|
- **Interviews**:
|
||||||
|
- **Offers**:
|
||||||
|
|
||||||
|
### What's working
|
||||||
|
|
||||||
|
|
||||||
|
### What needs adjustment
|
||||||
|
|
||||||
|
|
||||||
|
## 🎯 Goals Review
|
||||||
|
### Completed
|
||||||
|
- [x]
|
||||||
|
|
||||||
|
### In Progress
|
||||||
|
- [ ]
|
||||||
|
|
||||||
|
### Blocked/Postponed
|
||||||
|
-
|
||||||
|
|
||||||
|
## 💭 Personal Insights
|
||||||
|
### About leaving Tieto
|
||||||
|
|
||||||
|
|
||||||
|
### About consulting life
|
||||||
|
|
||||||
|
|
||||||
|
### About my skills/value
|
||||||
|
|
||||||
|
|
||||||
|
## 📚 Learning Progress
|
||||||
|
**New concepts mastered**:
|
||||||
|
**Practice time**:
|
||||||
|
**Confidence level**: /10
|
||||||
|
|
||||||
|
## 🔄 Next Week's Focus
|
||||||
|
1.
|
||||||
|
2.
|
||||||
|
3.
|
||||||
|
|
||||||
|
## 🔗 Links
|
||||||
|
[[Previous Week]] | [[Next Week]]
|
||||||
133
08-Resources/Interview-Prep/Interview Questions Master List.md
Normal file
133
08-Resources/Interview-Prep/Interview Questions Master List.md
Normal file
@@ -0,0 +1,133 @@
|
|||||||
|
---
|
||||||
|
tags: [interview-prep, questions]
|
||||||
|
---
|
||||||
|
|
||||||
|
# Interview Questions Master List
|
||||||
|
|
||||||
|
## 🎯 Common Questions & My Answers
|
||||||
|
|
||||||
|
### "Tell me about yourself"
|
||||||
|
**2-minute version**:
|
||||||
|
|
||||||
|
"I'm a senior data architect and developer with 25+ years of experience, primarily in SQL Server, .NET, and Azure. Most recently, I spent 9 years at TietoEVRY working on financial services platforms - fund management and securities trading systems.
|
||||||
|
|
||||||
|
My recent focus has been on modernizing legacy systems. I led the architecture for a REST API gateway on top of a complex legacy database, designing the entire solution including authentication, logging, and CI/CD pipelines all the way to production.
|
||||||
|
|
||||||
|
I've made a deliberate move to consulting through ExecuteIT - a firm of former colleagues - because I want to apply my expertise across different companies and industries, and continue growing in areas like modern data architecture and cloud-native solutions. At 55, this felt like the right time to make that transition and bring my experience to new challenges."
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
### "Why are you leaving Tieto?"
|
||||||
|
**Honest but positive version**:
|
||||||
|
|
||||||
|
"After 9 years, I felt it was time for new challenges. I was moved to a team focused on legacy tooling maintenance, which was less aligned with my strengths in architecture and modernization.
|
||||||
|
|
||||||
|
The combination of my former colleague's unexpected passing in September and being at a point in my career where I wanted to try consulting led me to make this move. I have tremendous respect for Tieto and the work we did - I built some great systems there - but I'm excited to apply my experience across different companies and industries now."
|
||||||
|
|
||||||
|
**If pressed on stress/problems**:
|
||||||
|
"I'll be honest - in hindsight, I could have communicated better with my manager about feeling stuck before making the decision to leave. But the move to consulting was something I'd been considering, and this felt like the right time."
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
### "Why consulting vs another permanent role?"
|
||||||
|
"At 55, with 25+ years of experience, I wanted to expand my impact beyond one organization. Consulting lets me:
|
||||||
|
- Apply my expertise across different companies and industries
|
||||||
|
- Learn from diverse technical environments
|
||||||
|
- Solve varied problems rather than one company's specific challenges
|
||||||
|
- Continue growing while helping multiple organizations
|
||||||
|
|
||||||
|
I'm doing this through ExecuteIT, a small firm of former colleagues from my Sybase days, which gives me the support and connection of people I know and trust."
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
### "What's your biggest weakness?"
|
||||||
|
**Modern Data Architecture Version**:
|
||||||
|
"Articulating my extensive practical experience using the latest data architecture terminology. I recently interviewed for a data architect role where I understood the concepts - Data Mesh, data governance - but struggled to discuss them fluently.
|
||||||
|
|
||||||
|
I realized I have 25 years of doing data architecture, but the language has evolved. So I'm actively studying modern terminology and frameworks to better communicate what I've been doing all along. It's a translation challenge, not a knowledge gap, but it's something I'm actively addressing."
|
||||||
|
|
||||||
|
**Alternative - React Version**:
|
||||||
|
"Frontend development isn't my primary strength. At Tieto, we used Angular and I was mostly backend-focused. I'm currently learning React because I see it's become the standard, but my core expertise is in backend architecture, databases, and APIs. I'm upfront about that because I want to work on projects where my strengths add the most value, while still being able to contribute across the stack."
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
### "Tell me about a challenging project"
|
||||||
|
**AbasecGateway story**:
|
||||||
|
|
||||||
|
"At Tieto, I architected a modern REST API layer on top of a legacy financial database called AbaSec. The challenge was that this 20+ year old system had no API - just direct database access - and we needed to modernize it without breaking existing functionality.
|
||||||
|
|
||||||
|
I designed the solution from the ground up:
|
||||||
|
- REST API gateway with proper authentication using OpenID Connect
|
||||||
|
- Comprehensive logging and metrics
|
||||||
|
- Clean Architecture pattern to isolate legacy database complexity
|
||||||
|
- Complete CI/CD pipeline for automated testing and deployment to production
|
||||||
|
|
||||||
|
The toughest part was balancing the need to modernize with maintaining 100% backward compatibility for critical financial operations. We couldn't afford downtime or data issues.
|
||||||
|
|
||||||
|
The result was a production-grade API that became the new standard way to interact with AbaSec, and a deployment pipeline that reduced our release cycle from weeks to hours. It also positioned the platform for future microservices migration."
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
### "Where do you see yourself in 5 years?"
|
||||||
|
"I see myself as a trusted technical advisor and architect, working across multiple organizations through consulting. I want to be someone who can:
|
||||||
|
- Walk into a complex legacy system and know how to modernize it
|
||||||
|
- Design cloud-native solutions that actually fit the business need
|
||||||
|
- Mentor teams in good architecture practices
|
||||||
|
- Bridge the gap between technical implementation and business value
|
||||||
|
|
||||||
|
I'm at a point in my career where I'm more interested in impact and variety than climbing a corporate ladder. Consulting gives me that, and I want to be known for delivering solid, maintainable solutions."
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 🎯 Technical Deep-Dive Questions
|
||||||
|
|
||||||
|
### SQL Server / Database
|
||||||
|
- "Optimize a slow query" - Have specific examples ready
|
||||||
|
- "Design a data warehouse" - Use TCM/AbaSec experience
|
||||||
|
- "Explain indexing strategy" - Performance tuning war stories
|
||||||
|
|
||||||
|
### Architecture
|
||||||
|
- "Design a microservices system" - AbasecGateway experience
|
||||||
|
- "Handle authentication/authorization" - OpenID Connect implementation
|
||||||
|
- "Design for high availability" - Azure patterns
|
||||||
|
|
||||||
|
### .NET
|
||||||
|
- "Async/await best practices" - Real examples
|
||||||
|
- "Dependency injection" - Clean Architecture approach
|
||||||
|
- ".NET 8 vs Framework" - Migration experience
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## ❓ My Questions for Them
|
||||||
|
|
||||||
|
### About the Role
|
||||||
|
1. "What does success look like in this role after 6 months? After a year?"
|
||||||
|
2. "What are the biggest technical challenges the team is facing?"
|
||||||
|
3. "How much is greenfield development vs working with legacy systems?"
|
||||||
|
|
||||||
|
### About the Team
|
||||||
|
1. "Tell me about the team structure and who I'd be working with"
|
||||||
|
2. "How does the team handle knowledge sharing and technical decisions?"
|
||||||
|
3. "What's the balance between solo work and collaboration?"
|
||||||
|
|
||||||
|
### About Technology
|
||||||
|
1. "What's your tech stack and where is it heading?"
|
||||||
|
2. "How do you handle technical debt?"
|
||||||
|
3. "What's your approach to DevOps and CI/CD?"
|
||||||
|
|
||||||
|
### About Growth
|
||||||
|
1. "What learning and development opportunities are available?"
|
||||||
|
2. "How do you support staying current with technology?"
|
||||||
|
3. "Is there a budget for conferences, training, certifications?"
|
||||||
|
|
||||||
|
### About Culture
|
||||||
|
1. "How would you describe the team culture?"
|
||||||
|
2. "How are decisions made - top-down or collaborative?"
|
||||||
|
3. "What do people love about working here?"
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 🔗 Related
|
||||||
|
- [[SEB Data Architect]] - learn from this
|
||||||
|
- [[Why I Left Tieto]]
|
||||||
|
- [[AbasecGateway Project]]
|
||||||
101
08-Resources/Learning Roadmap.md
Normal file
101
08-Resources/Learning Roadmap.md
Normal file
@@ -0,0 +1,101 @@
|
|||||||
|
---
|
||||||
|
tags: [learning, roadmap]
|
||||||
|
---
|
||||||
|
|
||||||
|
# Learning Roadmap 2025
|
||||||
|
|
||||||
|
## 🎯 Priority 1: Interview Essentials
|
||||||
|
|
||||||
|
### Data Architecture Terminology (For SEB-like roles)
|
||||||
|
**Timeline**: 2 weeks
|
||||||
|
**Why**: Failed SEB interview due to terminology gap
|
||||||
|
|
||||||
|
- [ ] Data Mesh concepts and principles
|
||||||
|
- [ ] Data Governance frameworks
|
||||||
|
- [ ] Data Fabric vs Data Mesh
|
||||||
|
- [ ] Modern data architecture patterns
|
||||||
|
- [ ] Data Catalog and metadata management
|
||||||
|
- [ ] Create translation document: My work → Modern terms
|
||||||
|
|
||||||
|
**Resources**:
|
||||||
|
- "Data Mesh" by Zhamak Dehghani
|
||||||
|
- Azure Data Architecture documentation
|
||||||
|
- Data governance frameworks overview
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
### React Fundamentals (For Svenska Kraftnät)
|
||||||
|
**Timeline**: 3-4 weeks
|
||||||
|
**Why**: Job requirement, have Angular background
|
||||||
|
|
||||||
|
- [ ] React basics: Components, Props, State
|
||||||
|
- [ ] Hooks (useState, useEffect, etc.)
|
||||||
|
- [ ] React Router
|
||||||
|
- [ ] Integration with .NET Web APIs
|
||||||
|
- [ ] Build sample project: Todo app with .NET backend
|
||||||
|
|
||||||
|
**Resources**:
|
||||||
|
- React official documentation
|
||||||
|
- "React - The Complete Guide" (Udemy)
|
||||||
|
- Build personal project
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 🎯 Priority 2: Strengthen Core
|
||||||
|
|
||||||
|
### Modern .NET Patterns
|
||||||
|
**Timeline**: Ongoing
|
||||||
|
|
||||||
|
- [ ] .NET 8 new features
|
||||||
|
- [ ] Minimal APIs
|
||||||
|
- [ ] New authentication patterns
|
||||||
|
- [ ] Performance improvements
|
||||||
|
|
||||||
|
### Azure Architecture
|
||||||
|
**Timeline**: Ongoing
|
||||||
|
|
||||||
|
- [ ] Azure Well-Architected Framework review
|
||||||
|
- [ ] Cost optimization patterns
|
||||||
|
- [ ] Security best practices
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 🎯 Priority 3: Emerging Skills
|
||||||
|
|
||||||
|
### MLOps (For Vattenfall-type roles)
|
||||||
|
**Timeline**: 1-2 months
|
||||||
|
|
||||||
|
- [ ] ML model deployment patterns
|
||||||
|
- [ ] Azure ML services
|
||||||
|
- [ ] Model monitoring and governance
|
||||||
|
- [ ] MLOps pipelines
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 📅 Weekly Learning Schedule
|
||||||
|
|
||||||
|
### Monday
|
||||||
|
- 1 hour: Data Architecture reading
|
||||||
|
|
||||||
|
### Tuesday
|
||||||
|
- 1 hour: React practice
|
||||||
|
|
||||||
|
### Wednesday
|
||||||
|
- 1 hour: Technical articles/blogs
|
||||||
|
|
||||||
|
### Thursday
|
||||||
|
- 1 hour: React practice
|
||||||
|
|
||||||
|
### Friday
|
||||||
|
- 1 hour: Review and consolidation
|
||||||
|
|
||||||
|
### Weekend
|
||||||
|
- Build projects, experiment
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 🔗 Related
|
||||||
|
- [[Skills Inventory]]
|
||||||
|
- [[Data Mesh]]
|
||||||
|
- [[React]]
|
||||||
|
- [[Current Focus]]
|
||||||
37
09-ExecuteIT/Team/ExecuteIT Team Overview.md
Normal file
37
09-ExecuteIT/Team/ExecuteIT Team Overview.md
Normal file
@@ -0,0 +1,37 @@
|
|||||||
|
---
|
||||||
|
tags: [executeit, team]
|
||||||
|
---
|
||||||
|
|
||||||
|
# ExecuteIT Team Overview
|
||||||
|
|
||||||
|
## 👥 Leadership
|
||||||
|
### Henrik Ernerot - VD (CEO)
|
||||||
|
**Background**: Former colleague from Sybase days
|
||||||
|
**Role**: CEO, primary contact for job opportunities
|
||||||
|
**Notes**:
|
||||||
|
- Helping with CV review and job applications
|
||||||
|
- Knows the consulting market well
|
||||||
|
- Connection to ework, magnit, itx brokers
|
||||||
|
|
||||||
|
### Göran Schwarz - Vice VD
|
||||||
|
**Background**: Former Sybase colleague
|
||||||
|
**Role**: Vice CEO
|
||||||
|
**Notes**:
|
||||||
|
|
||||||
|
### Inger Sörlen
|
||||||
|
**Background**: Former Sybase colleague
|
||||||
|
**Role**:
|
||||||
|
**Notes**:
|
||||||
|
|
||||||
|
## 📋 Company Info
|
||||||
|
**Founded**:
|
||||||
|
**Focus**: Consulting services leveraging deep technical expertise
|
||||||
|
**Culture**: Small firm of experienced ex-Sybase professionals
|
||||||
|
|
||||||
|
## 💰 Business Model
|
||||||
|
- **Billable hours**: 80% contributes to competency development fund
|
||||||
|
- **Consulting model**:
|
||||||
|
|
||||||
|
## 🔗 Resources
|
||||||
|
- Company website:
|
||||||
|
- Internal systems:
|
||||||
73
Home.md
Normal file
73
Home.md
Normal file
@@ -0,0 +1,73 @@
|
|||||||
|
---
|
||||||
|
tags: [dashboard]
|
||||||
|
---
|
||||||
|
|
||||||
|
# 🏠 ExecuteIT Consulting Dashboard
|
||||||
|
|
||||||
|
> Welcome to your consulting journey tracking system
|
||||||
|
|
||||||
|
## 📅 Quick Links
|
||||||
|
- **Today**: [[{{date:YYYY-MM-DD}}]]
|
||||||
|
- **This Week**: [[Week {{date:YYYY-[W]WW}}]]
|
||||||
|
- [[ExecuteIT Team Overview]]
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 🎯 Active Job Applications
|
||||||
|
|
||||||
|
*Once you install Dataview plugin, you'll see a dynamic table here*
|
||||||
|
|
||||||
|
**Manual tracking until then:**
|
||||||
|
- [ ] List active applications here
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 📈 This Week's Stats
|
||||||
|
- **Applications sent**:
|
||||||
|
- **Interviews scheduled**:
|
||||||
|
- **Skills practiced**:
|
||||||
|
- **Billable hours**:
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 🚀 Current Focus
|
||||||
|
**Primary Profile**:
|
||||||
|
**Learning Priority**:
|
||||||
|
**Next Interview**:
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 💭 Recent Thoughts
|
||||||
|
*Quick capture - process into reflections later*
|
||||||
|
|
||||||
|
-
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 🔗 Important Pages
|
||||||
|
- [[Skills Inventory]]
|
||||||
|
- [[Tieto Experience Summary]]
|
||||||
|
- [[Interview Questions Master List]]
|
||||||
|
- [[Learning Roadmap]]
|
||||||
|
- [[Consulting Tips]]
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 📊 Monthly Goals
|
||||||
|
### January 2025
|
||||||
|
- [ ] Set up vault and tracking system
|
||||||
|
- [ ] Define 3-4 core profiles
|
||||||
|
- [ ] Document all Tieto projects
|
||||||
|
- [ ] Apply to 10+ positions
|
||||||
|
- [ ] Complete 1 technical interview
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## 🎓 Current Learning Focus
|
||||||
|
- **Data Architecture**: Data Mesh, Data Governance concepts
|
||||||
|
- **Frontend**: React basics (for Svenska Kraftnät role)
|
||||||
|
- **Interview Skills**: Articulating experience in modern terminology
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
*Last updated: {{date:YYYY-MM-DD}}*
|
||||||
238
MANUAL_SETUP_INSTRUCTIONS.md
Normal file
238
MANUAL_SETUP_INSTRUCTIONS.md
Normal file
@@ -0,0 +1,238 @@
|
|||||||
|
# Manual Setup Instructions for ExecuteIT Consulting Vault
|
||||||
|
|
||||||
|
## ✅ Vault Structure Created
|
||||||
|
The complete folder structure and templates have been created automatically.
|
||||||
|
|
||||||
|
## 🔌 Recommended Community Plugins Setup
|
||||||
|
|
||||||
|
### Step 1: Enable Community Plugins
|
||||||
|
1. Open Obsidian
|
||||||
|
2. Go to Settings (gear icon) → Community plugins
|
||||||
|
3. Click "Turn on community plugins"
|
||||||
|
4. If prompted about safe mode, click "Turn off Safe Mode"
|
||||||
|
|
||||||
|
### Step 2: Install Recommended Plugins
|
||||||
|
|
||||||
|
#### Essential Plugins
|
||||||
|
|
||||||
|
**1. Dataview**
|
||||||
|
- Click "Browse" in Community plugins
|
||||||
|
- Search for "Dataview"
|
||||||
|
- Click Install, then Enable
|
||||||
|
- **Purpose**: Dynamic tables and queries for job tracking
|
||||||
|
- **Configuration**: Settings → Dataview → Enable JavaScript Queries
|
||||||
|
|
||||||
|
**2. Templater**
|
||||||
|
- Search and install "Templater"
|
||||||
|
- **Purpose**: Advanced template functionality with dynamic dates
|
||||||
|
- **Configuration**:
|
||||||
|
- Settings → Templater → Template folder location: `07-Templates`
|
||||||
|
- Enable "Trigger Templater on new file creation"
|
||||||
|
|
||||||
|
**3. Calendar**
|
||||||
|
- Search and install "Calendar"
|
||||||
|
- **Purpose**: Visual calendar navigation for daily notes
|
||||||
|
- **Configuration**:
|
||||||
|
- Settings → Calendar → Dot threshold: 1
|
||||||
|
|
||||||
|
#### Highly Recommended Plugins
|
||||||
|
|
||||||
|
**4. Kanban**
|
||||||
|
- Search and install "Kanban"
|
||||||
|
- **Purpose**: Visualize job pipeline as a kanban board
|
||||||
|
- **Usage**: Create a kanban board in `02-Jobs` to track application stages
|
||||||
|
|
||||||
|
**5. Advanced Tables**
|
||||||
|
- Search and install "Advanced Tables"
|
||||||
|
- **Purpose**: Better table editing experience
|
||||||
|
- **Usage**: Auto-formats tables as you type
|
||||||
|
|
||||||
|
**6. Tag Wrangler**
|
||||||
|
- Search and install "Tag Wrangler"
|
||||||
|
- **Purpose**: Easier tag management
|
||||||
|
- **Usage**: Rename tags across all notes easily
|
||||||
|
|
||||||
|
#### Optional but Useful
|
||||||
|
|
||||||
|
**7. Periodic Notes**
|
||||||
|
- For advanced weekly/monthly note creation
|
||||||
|
- Works with Calendar plugin
|
||||||
|
|
||||||
|
**8. Graph Analysis**
|
||||||
|
- Better graph view with more options
|
||||||
|
- Useful for seeing connections between jobs, skills, projects
|
||||||
|
|
||||||
|
**9. Excalidraw**
|
||||||
|
- For drawing diagrams and architecture sketches
|
||||||
|
- Great for technical interviews prep
|
||||||
|
|
||||||
|
### Step 3: Configure Daily Notes (Already Done)
|
||||||
|
The daily notes configuration is already set up, but verify:
|
||||||
|
- Settings → Daily notes → Date format: `YYYY-MM-DD`
|
||||||
|
- New file location: `01-Daily`
|
||||||
|
- Template file location: `07-Templates/Daily Note`
|
||||||
|
|
||||||
|
### Step 4: Configure Templates (Already Done)
|
||||||
|
The templates configuration is already set up, but verify:
|
||||||
|
- Settings → Templates → Template folder location: `07-Templates`
|
||||||
|
|
||||||
|
## 📊 Setting Up Dataview Queries
|
||||||
|
|
||||||
|
Once Dataview is installed, add these queries to your Home.md dashboard:
|
||||||
|
|
||||||
|
### Active Jobs Table
|
||||||
|
```dataview
|
||||||
|
TABLE
|
||||||
|
status as Status,
|
||||||
|
priority as Priority,
|
||||||
|
applied-date as Applied,
|
||||||
|
company as Company
|
||||||
|
FROM "02-Jobs/Active"
|
||||||
|
WHERE contains(tags, "job-application")
|
||||||
|
SORT priority DESC, applied-date DESC
|
||||||
|
```
|
||||||
|
|
||||||
|
### Recent Daily Notes
|
||||||
|
```dataview
|
||||||
|
LIST
|
||||||
|
FROM "01-Daily"
|
||||||
|
SORT file.name DESC
|
||||||
|
LIMIT 7
|
||||||
|
```
|
||||||
|
|
||||||
|
### Skills by Category
|
||||||
|
```dataview
|
||||||
|
TABLE
|
||||||
|
proficiency as Level,
|
||||||
|
category as Category
|
||||||
|
FROM "04-Skills"
|
||||||
|
WHERE contains(tags, "skill")
|
||||||
|
SORT proficiency DESC
|
||||||
|
```
|
||||||
|
|
||||||
|
## 🎨 Appearance Settings (Optional)
|
||||||
|
|
||||||
|
### Theme Recommendations
|
||||||
|
1. Settings → Appearance → Themes → Manage
|
||||||
|
2. Try these popular themes:
|
||||||
|
- **Minimal**: Clean, professional look
|
||||||
|
- **Things**: GTD-inspired theme
|
||||||
|
- **Blue Topaz**: Feature-rich with good color coding
|
||||||
|
|
||||||
|
### CSS Snippets (Optional)
|
||||||
|
You can create custom CSS snippets in `.obsidian/snippets/` for:
|
||||||
|
- Custom callout styles
|
||||||
|
- Better table formatting
|
||||||
|
- Tag coloring
|
||||||
|
|
||||||
|
## 📱 Mobile Setup (Optional)
|
||||||
|
|
||||||
|
### Obsidian Mobile App
|
||||||
|
1. Download Obsidian from App Store/Google Play
|
||||||
|
2. Open existing vault from iCloud/Dropbox/local storage
|
||||||
|
3. Same plugins available on mobile
|
||||||
|
|
||||||
|
### Sync Options
|
||||||
|
- **Obsidian Sync** (paid, official, most reliable)
|
||||||
|
- **iCloud** (free for Mac/iOS users)
|
||||||
|
- **Dropbox/Google Drive** (free, works cross-platform)
|
||||||
|
|
||||||
|
## ⚙️ Additional Configuration
|
||||||
|
|
||||||
|
### Graph View
|
||||||
|
Settings → Graph view:
|
||||||
|
- Enable "Show attachments"
|
||||||
|
- Groups: Create color groups for tags (jobs, skills, reflections)
|
||||||
|
- Forces: Adjust for better layout
|
||||||
|
|
||||||
|
### Hotkeys
|
||||||
|
Set up custom hotkeys for frequent actions:
|
||||||
|
- Settings → Hotkeys
|
||||||
|
- Recommended:
|
||||||
|
- "Open today's daily note" → Ctrl/Cmd + T
|
||||||
|
- "Insert template" → Ctrl/Cmd + Shift + T
|
||||||
|
- "Quick switcher" → Ctrl/Cmd + O
|
||||||
|
|
||||||
|
### File & Links
|
||||||
|
Settings → Files & Links:
|
||||||
|
- Default location for new notes: `00-Inbox`
|
||||||
|
- Automatically update internal links: ON
|
||||||
|
- Default location for attachments: `08-Resources/Attachments`
|
||||||
|
|
||||||
|
## 🎯 First Actions Checklist
|
||||||
|
|
||||||
|
After setup is complete:
|
||||||
|
|
||||||
|
- [ ] Open vault in Obsidian
|
||||||
|
- [ ] Install Dataview plugin
|
||||||
|
- [ ] Install Templater plugin
|
||||||
|
- [ ] Install Calendar plugin
|
||||||
|
- [ ] Create first daily note (Ctrl/Cmd + P → "Open today's daily note")
|
||||||
|
- [ ] Review and customize [[Home]] dashboard
|
||||||
|
- [ ] Fill out [[Skills Inventory]]
|
||||||
|
- [ ] Create profiles in `03-Profiles/`:
|
||||||
|
- [ ] Data Architect profile
|
||||||
|
- [ ] Backend Developer profile
|
||||||
|
- [ ] Technical Architect profile
|
||||||
|
- [ ] Move existing job applications to proper folders:
|
||||||
|
- [ ] SEB application → `02-Jobs/Active/`
|
||||||
|
- [ ] Vattenfall application → `02-Jobs/Pipeline/`
|
||||||
|
- [ ] Svenska Kraftnät → `02-Jobs/Pipeline/`
|
||||||
|
- [ ] Document 2-3 major Tieto projects in `05-Projects/`
|
||||||
|
- [ ] Create first weekly reflection
|
||||||
|
|
||||||
|
## 📚 Learning Obsidian
|
||||||
|
|
||||||
|
### Quick Start Resources
|
||||||
|
- Obsidian Help Vault (Help → Open help vault)
|
||||||
|
- [Official Documentation](https://help.obsidian.md/)
|
||||||
|
- [Obsidian Hub Community](https://publish.obsidian.md/hub)
|
||||||
|
|
||||||
|
### Key Concepts
|
||||||
|
- **Double brackets [[]]**: Create links between notes
|
||||||
|
- **Tags #**: Categorize and filter notes
|
||||||
|
- **Frontmatter**: YAML metadata at top of notes
|
||||||
|
- **Backlinks**: See what notes link to current note
|
||||||
|
- **Graph view**: Visualize connections
|
||||||
|
|
||||||
|
### Markdown Basics
|
||||||
|
- `#` Headers
|
||||||
|
- `**bold**` and `*italic*`
|
||||||
|
- `- [ ]` Checkboxes
|
||||||
|
- Tables with `|`
|
||||||
|
- `> ` Blockquotes
|
||||||
|
|
||||||
|
## 🆘 Troubleshooting
|
||||||
|
|
||||||
|
### Dataview not showing results
|
||||||
|
- Check that plugin is enabled
|
||||||
|
- Verify frontmatter YAML is correct (no typos)
|
||||||
|
- Check query syntax
|
||||||
|
|
||||||
|
### Templates not working
|
||||||
|
- Verify template folder path in settings
|
||||||
|
- Check that Templater plugin is enabled
|
||||||
|
- Ensure template files exist in `07-Templates/`
|
||||||
|
|
||||||
|
### Sync issues
|
||||||
|
- Check sync service status
|
||||||
|
- Verify folder permissions
|
||||||
|
- Try manual sync/refresh
|
||||||
|
|
||||||
|
## 💡 Tips for Success
|
||||||
|
|
||||||
|
1. **Start simple**: Don't try to use every feature immediately
|
||||||
|
2. **Daily notes are key**: Build the habit of daily journaling
|
||||||
|
3. **Link generously**: Create connections between related notes
|
||||||
|
4. **Review weekly**: Use weekly reflections to see progress
|
||||||
|
5. **Customize gradually**: Adjust system as you learn what works
|
||||||
|
6. **Backup regularly**: Your vault is just a folder - back it up!
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
**Need help?**
|
||||||
|
- Obsidian Forum: https://forum.obsidian.md/
|
||||||
|
- Obsidian Discord: https://discord.gg/obsidianmd
|
||||||
|
- Reddit: r/ObsidianMD
|
||||||
|
|
||||||
|
**Ready to start?** Open [[Home]] and begin your consulting journey!
|
||||||
44
README.md
Normal file
44
README.md
Normal file
@@ -0,0 +1,44 @@
|
|||||||
|
# ExecuteIT Consulting Vault
|
||||||
|
|
||||||
|
This Obsidian vault is designed to support your consulting journey, job hunting, and professional development.
|
||||||
|
|
||||||
|
## 📁 Vault Structure
|
||||||
|
|
||||||
|
- **00-Inbox**: Quick capture area for new ideas and information
|
||||||
|
- **01-Daily**: Daily notes for journaling and tracking
|
||||||
|
- **02-Jobs**: Job applications organized by status
|
||||||
|
- **03-Profiles**: Different professional personas/profiles for various role types
|
||||||
|
- **04-Skills**: Skill tracking and development plans
|
||||||
|
- **05-Projects**: Past project documentation
|
||||||
|
- **06-Reflections**: Weekly and monthly reflection notes
|
||||||
|
- **07-Templates**: Reusable templates for various note types
|
||||||
|
- **08-Resources**: Reference materials, interview prep, guides
|
||||||
|
- **09-ExecuteIT**: Company-specific information
|
||||||
|
|
||||||
|
## 🚀 Getting Started
|
||||||
|
|
||||||
|
1. Open this vault in Obsidian
|
||||||
|
2. Start with [[Home]] - your dashboard
|
||||||
|
3. Create your first daily note (Ctrl/Cmd + P → "Open today's daily note")
|
||||||
|
4. Set up your [[Skills Inventory]]
|
||||||
|
5. Document your Tieto experience (started in [[Tieto Experience Summary]])
|
||||||
|
|
||||||
|
## 📝 Daily Workflow
|
||||||
|
|
||||||
|
1. **Morning**: Open daily note, set priorities
|
||||||
|
2. **Throughout day**: Log job activities, learning, thoughts
|
||||||
|
3. **Evening**: Reflect on day, plan tomorrow
|
||||||
|
|
||||||
|
## 📅 Weekly Workflow
|
||||||
|
|
||||||
|
1. **Sunday evening**: Create weekly reflection note
|
||||||
|
2. **Monday**: Review goals, scan job boards
|
||||||
|
3. **Friday**: Review progress, follow up on applications
|
||||||
|
|
||||||
|
## 🔌 Recommended Next Steps
|
||||||
|
|
||||||
|
See the manual setup instructions for enabling community plugins to enhance functionality.
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
**Start here**: [[Home]]
|
||||||
Reference in New Issue
Block a user