Simone Spaccarotella simonespa

With reference to the job description please use this section to fully explain how your skills, abilities and experience meet the specific requirements of this role.

I have a solid understanding of data science and machine learning principles gained through the Level 7 (MSc) AI Apprenticeship I started in Feb 2023 and a robust working knowledge developed during the attachment period with the iPlayer Recommendation team of data scientists (previously known as iRex).

To pass the apprenticeship assessment, I had to produce an original solution to demonstrate my contribution towards a BBC need/objective. During the attachment period I personally built a Content-To-Content similarity recommendations system of iPlayer programmes. The novel solution consisted of an Autoencoder network able to generate metadata embeddings from Passport tags, to improve similarity calculations compared to the existing solution. I presented this project to the DS team and various stakeholders and got overall positive feedback plus

Get the name of the branch containing this commit

git branch -a --contains 9f12d89998fbd38a3fd3a1d21e7b028b9659c107

Search this commit in the PR

gh pr list --search "${SHA}" --state merged gh pr list --search 9f12d89998fbd38a3fd3a1d21e7b028b9659c107

BBC Mission

Set out in our Royal Charter, the BBC’s Mission is:

To act in the public interest, serving all audiences through the provision of impartial, high-quality and distinctive output and services which inform, educate and entertain.

The BBC's Public Purposes, which describe what the BBC must do for its audiences, are also laid out in the BBC's Royal Charter. Our use of AI must be consistent with them.

To provide impartial news and information
To support learning for people of all ages

Data Fetching with React Server Components

Notes taken from https://www.youtube.com/watch?v=TQQPAU21ZUw

Properties

Good User Experience Cheap maintenance Fast performance

Next JS questions and features requests

Environment Variables that are "environment aware" on server and client

The default behaviour is as it works right now, with no environments
The number and names of environments are flexible and defined by the user. They can be configured in the nextjs.conf file
If defined, the client bundle(s)/asset(s) can refer to the environment name/label to lookup the appropriate config value. The bundle doesn't contain the environment value hardcoded but a reference to an external asset that is prefixed with the environment.
All of this is transparent to the user

A mechanism to read values globally and share them across multiple requests on the server-only

Recoil

https://recoiljs.org/

Flexible shared state

Useful when two components are not under the same line of inheritance (from two separate branch) and use the same shared state and need to keep the state in synch.

Atom

	import {
	SyntheticEvent,
	useCallback,
	useEffect,
	useRef,
	useState,
	} from "react";

	import RadioList from "@/ui/radio-list";

	import http from "k6/http";
	import { check } from "k6";

	const URL = "https://example.com"; // Target URL

	export let options = {
	// If a cert is required to access the endpoint
	//
	// tlsAuth:
	// [

	from sklearn.metrics import confusion_matrix
	import seaborn as sns
	import matplotlib.pyplot as plt

	cm = confusion_matrix(y_test, y_pred)

	plt.figure(figsize=(12,12))

	sns.heatmap(data=cm, # Data to plot
	square=True, # Make the cells square, looks nicer.

	- https://www.youtube.com/watch?v=Uv7I75pLmb4
	- https://aws.amazon.com/solutions/implementations/distributed-load-testing-on-aws/