everything

notes/other/My development.md

@@ -0,0 +1,144 @@
+Hey hey. I've been thinking a bit after our last 1:1 and your proposal on discussing what kind of goals I would like to go for. I found a small writing to be the most convenient. If you have a minute to read this before our next 1:1, I think it can act as an agenda/reference. So here are few thoughts into where I would like to point myself towards to:
+
+- Leadership: I have always naturally enjoyed being proactive, standing up when most people and getting things moving. I enjoy it and I think I could even say I *need* it to a certain degree. There are several areas where I think this leadership-craving can turn into applicable stuff here at Lola:
+	- I enjoy leading more junior colleagues and mentoring people, as well as managing teams. I understand this is no trivial request and I'm not expecting a junior person tomorrow reporting to me, but I want you to know that you can count on me leading other colleagues in the data team when it becomes necessary. I also would enjoy taking the lead on more ephemeral, project-specific teams.
+	- I enjoying partnering up with business people and becoming their technical/data go-to person. Opposite to what tends to be the case with technical profiles, I actually find this very pleasant and I guess it was one of the things that put me through consulting successfully. Overtime, I would like to play this go-to role for some area or team within Lola. Let's discuss how that fits with the bigger picture and roadmaps.
+- Technical: I enjoy the tech side of things. I am the kind of person who will code on his free time. I like best practices, building stuff and testing new tools. I think this, mixed with the previous bullet on leadership, brings me to certain ideas:
+	- I enjoy being the person that has to play around with new tech to assess if it works for something (I brought Great Expectations into my unit at ACN, and have similar stories at previous companies). I think I can bring a lot with this attitude, both from the software side and the optimization/statistics/ml side for operations.
+	- My values are very aligned with the open-source mindset. If some day we consider open-sourcing something we build inside Lola, I would support that strongly and would enjoy taking the lead.
+	- I also enjoy participating in technical groups, events, discussions, meetups, etc. On this subject, I have to very specific proposals:
+		- We could run a technical blog together with the tech team. This is large effort, so again, I understand many pieces will have to fit for this to happen. But I think it would yield value over time. And our successful competitors are doing this (https://blog.picnic.nl/).
+		- A less-resourceful endeavor: there are many Python/Data Engineering/Data Science meetups in Porto, Madrid, Barcelona, Lisbon. I would love to tour around those explaining interesting things about what we build in Lola, and this could also be helpful for our PR as a tech-hiring company.
+- Others
+	- My position teaching in University gets me in touch with researchers and students. I think there are opportunities to be untapped from relating with this groups that might be worth exploring. I would be happy to discuss them and lead whatever may come out of it.
+
+
+And to complement, a few things I would *not* like:
+- Drop all my technical work and end up in 100% business focused position
+- Stay stuck only on technical work and be miles away from business colleagues and their problems/challenges.
+- Never assume any leadership and stay at the individual contributor level.
+
+## Discussion 20220907
+
+- Blog: aim for early 2023 to get it started
+
+GOALS:
+- Take the lead for data in polish operations
+- Blog up and running before 15/12/2022
+	- Subdomain ready
+	- Blogging platform ready
+	- 4 articles ready
+	- Explicit agreement with stakeholders on ownership and responsibilities of each of us
+- Give a talk in a meetup in at least Porto and Madrid before January
+
+Liliana
+- Blog
+- PR in meetups
+- University
+
+
+# Discussion 20220920
+
+- [x] Barcelona Meetup
+- [x] I'll talk now with Liliana
+- [ ] Berlana and the blog? Not yet
+
+- [x] Feedback
+	- Great feedback from the team
+	- João agrees, good hire
+- [ ] Any news from Poland?
+
+
+
+
+# Discussion 20221004
+
+- [x] Berlana and the blog? 
+	- They already tried to go for it but never followed through.
+	- Berlana is happy about going for it. 
+	- He would like it to be a bottom-up.
+	- We agree to wait until Poland is clearer and they are less overburdened.
+	- We can already write material stuff.
+- [x] I discussed with Liliana, she's onboard. We just... need to do it.
+- [x] Sponsoring PyBCN day and giving talks
+
+
+
+
+# Goals for 2023
+
+- Lead the junior Data Engineer
+- Keep making our systems better
+	- Make the basic, foundational stuff work so well that we get plenty of time for advanced stuff
+- Keep learning
+	- Swallow a few books: MySQL, AWS, Prefect, Python, Spark, Kafka
+- Fun stuff
+	- Blog, Uni, Meetups
+	- Come up with a few crazy engineering ideas
+
+## Performance Review 2022-12-21
+
+- "You do things that fall outside of your area, you never comply."
+- "You use time efficiently"
+- "One thing I like of working for you is: you have an ideal solution for a problem, but if the team wants to do something else, you adapt." Not tyrannical.
+- "Always getting new tasks"
+- Four words:
+	- "Organized"
+	- "Innovator" :D
+	- "Efficient"
+	- "Good comunicator"
+
+- Start: more involved with other teams (not a critic, but a wish), some advanced data projects.
+- Stop: Nothing here. :D
+- Continue: 
+	- Innovating
+	- Adapting to team decisions
+
+- "I know you all have plenty of opportunities out there."
+
+
+
+
+
+
+# 1:1 20230110
+ 
+- Liliana
+- Junior guy
+- I'm glad with how things are popping
+
+
+
+# 1:1 20230207
+
+- Mindmap
+- Trip to Porto? In mid march
+- Uni
+	- Starting next week one hour a week
+	- Will have a bit more load than expected, but I don't think it's going to be troublesome since the additional effort is on evenings
+	- I'll send you a summary of my expected OOF patterns
+
+
+- Benefits
+	- 25 days of holidays
+	- Birthday off (even if one weekend)
+	- Picking team day
+	- Voluntary days
+
+
+# 1:1 20230307
+
+- What happened with Ana Martins?
+- Class hours
+- Holidays
+- Trip to porto confirmed
+- Technical blog: I have a couple of articles ready
+- Multi-drop suggestion service: where do we start
+
+
+# 1:1 20230711
+
+- Contract situation. What the hell is going on? Can't we just move my contract to a new company already?
+- Yearly review. Should we wait?
+- Morale is quite low
+- Afonso, flexibility and expectations

notes/other/Order Bundling White Paper.md

@@ -0,0 +1,73 @@
+
+This White Paper describes the idea of Order Bundling. It's part of a brainstorming effort, not a plan. It's purpose is to stir ideas that could lead to a more specific plan of action.
+
+## TLDR
+
+Order bundling consists on performing more than one delivery in a same drive. It is an opportunity to improve operational efficiency by reducing the driving time needed for the same number of orders. The improvement in efficiency mainly derives from skipping trips back to the picking location to pick the goods for the next delivery. Bundling is attractive under conditions X,Y,Z. Bundling is hard to execute under conditions X,Y,Z. 
+
+## What is Order Bundling
+
+Order bundling is the idea of having a shopper or driver deliver two orders in a single ride. This means that, instead of:
+- Picking location -> first customer location -> picking location -> second customer location -> picking location (for next order)
+We would do:
+- Picking location -> first customer location -> second customer location -> picking location (for next order)
+
+The goal of order bundling is to spend less time driving to serve the same amount of orders.
+
+### Anatomy of an order
+
+- Picking
+	- Picking time
+	- Checkout time
+	- Loading time
+- Driving
+	- Drive to customer location
+	- Delivery
+	- Drive back to picking location
+
+
+
+
+### Factors that favour bundling
+- Orders that are close in space and time.
+	- High volume of orders (higher chances of multiple orders in same or adjacent timeslots)
+	- Operational areas that are small in physical area (higher chances of customers being close to each other)
+- Picker + driver operating model.
+- Great temperature-control (lower chances of frozen/chill products going bad)
+
+### Factors that discourage bundling
+- Orders that are far in space and time.
+	- Low volume of orders (lower chances of multiple orders in same or adjacent timeslots)
+	- Operational areas that are large in physical area (lower chances of customers being close to each other)
+- Single shopper operating model.
+- Poor temperature-control (higher chances of frozen/chill products going bad)
+
+
+
+
+
+
+
+## How can Order Bundling be executed
+
+## Benefits and estimated opportunity size
+
+The main financial cost for Lolamarket's operation is the shopper's compensation. 
+
+Making shopper's significantly more productive allows at the same time cost saving for Lolamarket and an increase in hourly compensation for the shopper. An increase in efficiency basically makes the pie of each order bigger, which is independent of how this pie is split between shopper and Lolamarket. We could get greedy and hoard all the efficiency savings for ourselves. We could be selfless and let the shoppers take home all the efficiency gains. Or we could be moderate and strike a balance somewhere in between.
+
+## Estimated opportunity size
+
+- Pick a time frame
+- Pick a geographical area
+- Define several tiers of close-ness (<10driving-min, <20driving-min, <30driving-min)
+- Report on what percentage of orders where candidates for bundling
+- Make an assumption on the saved human time 
+
+
+## Roadmap
+
+1. Backwards looking estimation of opportunity
+2. Simple 3 day ahead bundling suggestion service
+3. Integration in shopper app and order backoffice
+4. Fine tuning

notes/other/Prefect Flow Checklist.md

@@ -0,0 +1,17 @@
+## The Flow itself
+
+- [ ] **No secrets, passwords or similar in place.**
+- [ ] No unnecessary hard-codings (if some piece of data acts as constant in several flows, it's better to make it part of the `env`)
+- [ ] The right `reference_tasks` are indicated, or the defaults are good enough
+- [ ] The flow has a proper clean-up/tear-down (if something fails, finishing activities like closing connections or deleting files will still happen)
+- [ ] There is no unnecessary boilerplate imports, configs, variables, constants and functions in the script (if you can remove something and the flow will still always work properly, remove it)
+- [ ] The flow has a way to be run and tested without consequences (i.e. write to a production database)
+- [ ] You have run the flow succesfully at least once in its final state before registering
+- [ ] You have run the flow succesfully at least once from the prefect server
+
+
+## Scheduling
+- [ ] You have set up a slack warning so that failures are notified
+- [ ] You have intentionally made the flow fail to verify that notifications work properly
+- [ ] The right parameters are set with the scheduled run
+- [ ] You have verified manually that the first scheduled run went well and produced the expected output

notes/other/ideas for team meet up on sept-22.md

@@ -0,0 +1,9 @@
+# Ideas for Data Conclave
+
+I've been thinking a bit on different things that we could do to profit from all of us being together. Sharing in no particular order:
+
+- Hold a session with Gonçalo and/or Ricardo to discuss Data within Lola. It doesn't necessarily need to be about anything important, but could be a nice little boost for team morale to get in touch with team and have a few nice words. Optionally, if we have some more future-looking ideas that we thing are worth raising to them, we can leverage the opportunity.
+- North-star brainstorming: linking with the previous, we could take the chance to step away from the day-to-day work and dream awake about what could Data do for Lolamarket. If we feel like it, we could even meet with managers (Mónica, Luis, Lukasz) from different areas one by one to discuss specific ideas on their teams.
+- Meeting with the Portuguese tech team to do a bit of bonding (I guess this one is specially relevant for Dani and I mainly).
+- I would personally really like to go and do a bit of shopping, although if our stay is going to be short this might eat up too much valuable time.
+- The conclave might also be a good idea to do any internal data team training we might have in our backlog. We could even dedicate some time to have each of us bring interesting technologies/techniques/knowledge we have with the team.

notes/other/travel expenses.md

@@ -0,0 +1,24 @@
+# 27-27 Sept 2022
+
+- Vueling go
+	- 16€
+- Vueling return
+	- 16€
+- Cabify 27/09 BCN
+- Uber 27/09 Porto
+- Uber 28/09 Porto
+- Dinner at the Porto airport
+- Cabify 28/09 BCN
+
+
+# 23-24 MAR23
+
+- Vueling: 12,65 + 39,00 €
+- Cabify go: 23,40 €
+- Uber go: 9,35 €
+- Uber return: 9,29 €
+- Cabify return: 24,44 €
+- Francesinha: 
+- Airport dinner: 
+
+**TOTAL**: