Selçuk Cihan selcukcihan

I am interviewing for senior software engineering jobs. There are some questions or topics that I don't feel comfortable answering and I want to get to the bottom of those. I am looking for that "aha" moment, like the light bulb to suddenly turn on, the idea to click so that I have a way forward answering the question.

I am not looking for detailed end to end responses, I am more in search of that trigger, that clue which will lead me to the satisfactory answer.

You will be the clue provider to me. I'll choose a topic, then you'll suggest some good quality technical questions and I'll pick one. Then, you'll give me the gist of it, that clue which will light that bulb for me. When I am interviewing, I sometimes get stuck at a point where I need something more than a nudge, that's what I am looking for from you.

NodeJS and JavaScript
- Event loop
- Parallel programming
- Async
- Libuv and the thread pool
- Streams and backpressure
- Worker threads vs child processes
- Memory model (V8 heap, garbage collection, memory leaks)
- CommonJS vs ESM modules
Clustering and process management (PM2, cluster module)

Project Rules

These instructions apply to every task performed in this repository.

Purpose

Treat this file as the project-wide source of truth for repository-specific working rules.
Read and follow these instructions before making changes in this repo.

Working Style

Prefer minimal, targeted changes over broad refactors.

Make minimum amount of changes. I want to keep the diffs very small because I review them.
Do not write any tests unless specifically asked.
Keep the current code style and format, do not deviate.
Follow the principle of single responsibility by keeping unrelated functions or modules separate.
Do not make implicit assumptions, try to surface the assumptions so we can review them and guide you if necessary.

Yazılım Mülakatlarına Hazırlık - Ders Programı

Hafta 1: Başlangıç ve Strateji

Ders 1: Mülakatlara Genel Bakış ve Hazırlık Stratejisi

Kursa giriş, beklentilerin belirlenmesi
Mülakat türleri: Telefon, online, onsite
Şirket türlerine göre mülakat yaklaşımı (startup vs big tech)
Ön hazırlık süreci:
CV ve LinkedIn optimizasyonu

Refactoring UI

These are my notes from https://www.refactoringui.com

Starting

Start with a feature, not a layout. Details comes later, defer choices like color.
Establish a system (of choices): font size, weight, line height, colors, spacing, shadows etc.
Refrain from using font weights under 400 for UI work, to de-emphasize some text, use a lighter color or smaller font size instead.

	{
	"schemaVersion": "1.0.0",
	"appId": "6757076667",
	"versionString": "1.0",
	"pricing": {
	"baseTerritory": "USA",
	"prices": [
	{
	"price": "0",
	"territory": "USA"

	`POST https://api.cloudflare.com/client/v4/accounts/a6003e408a448be5fcc801b316519998/browser-rendering/json`

	request body

	```json
	{
	"url": "https://jobs.elastic.co/jobs/department/engineering?size=n_20_n",
	"prompt": "Give me a list of job postings on this page, include the title and url of each job. I only care about senior roles in engineering positions.",
	"gotoOptions": {
	"waitUntil": "networkidle0"

	import sys
	import pathlib


	def parse_kindle_notes(input_file):
	with open(input_file, "r") as file:
	lines = [x.strip() for x in file.readlines()]
	notes_dict = {}
	current_book = None
	current_notes = []

	class TrieNode:
	def __init__(self, char, value=None):
	self.char = char
	self.children = []
	self.terminates = False
	self.value = value

	def __str__(self):
	if self.value is not None:
	return f"word: {self.value}"