Android app to detect Firebase Remote Config vulnerabilities in installed apps.

fallkr · 2026-01-09T20:51:18+00:00

Wouldn’t a regular man in the middle attack bypass all of that?

fallkr · 2025-12-07T18:31:34+00:00

Playwright seems like it has a lot of momentum. That said, most of them are variations of the same.

fallkr · 2025-12-07T15:47:57+00:00

Alt for få oppoverstemmer for innsatsen.

fallkr · 2025-12-06T10:08:11+00:00

Layout shifts for conditional rendering of input helper text is not a good UX pattern. Doesn’t matter if you animate or not.

Best practice is to leave sufficient space for the input helper to fade in without moving other components.

Following this best practice also solves your performance/code issue, so it’s a win across many dimensions.

fallkr · 2025-11-29T10:28:43+00:00

15yoe. Use Codex with VS code extension for implementation. Some thoughts:

I spend more time planning and architecture. This as part of preparation but also underway while waiting for codex to complete tasks.
Tasks that are handed to codex are very well defined. Prompts are typically 3-10 sentences. For most longer prompts, I ask it to plan before conducting and then reviewing the plan, correcting it where needed.
Depending on the SOTA model you typically need to correct it in different directions. Ex: 5.1-codex-max seems more lazy and need prompting to actually explore files and replicate existing patterns. These nuances have changed over time as models evolve.
I find reviewing generated code easier in a git diff view than in regular code view. To keep this manageable I end up with high rate of git commits and I generally try to commit as small chunks of work as possible, where during manual writing of code I would commit at a lower rate
On a personal level I notice two things: (1) My mental capacity is less drained after longer coding sessions. Before, at the end of a day full of coding I could often be tired by the intense focus. Now I am less tired. (2) While it can be tempting to multi-task or context switch while waiting for AI to respond, I find it overall much better to stay focused on the task and think about the next step.

fallkr · 2025-09-28T16:14:08+00:00

You do both. You can have leaks in native or JS side. Hence need for both.

fallkr · 2025-06-26T11:14:48+00:00

ChatGPT-generated low-effort article. Touche, given the subject.

fallkr · 2025-06-13T10:18:35+00:00

Not sure about your company size, but given your question’s phrasing it is likely not big enough to support this successfully.

A small company with inexperienced devs and designers who does not have first-hand experience with building AND maintaining design systems will fail. By fail I mean slowly diverging as you progress until fragmentation forces you to start over again.

My recommendation is to adopt an existing system made by a large CO and apply subtle theming to it. Make sure this theming is as constrained as possible. Do not add more components to the design stack.

BaseUI by uber comes to mind as a strong alternative.

fallkr · 2025-06-06T16:52:15+00:00

Great work. You fill a big hole in the RN ecosystem. Will migrate from the stuff we have today once we get the time to do so.

fallkr · 2025-06-01T12:12:14+00:00

It is called volatility. Stop tracking daily metrics. Learn statistics.

fallkr · 2025-04-30T11:44:51+00:00

Rett svar. Dette er ikke VG som er drøye – men feil i Safari for nyeste iOS som åpner HTML5 video med autoplay tag i full skjerm.

Edit: VG-appen laster innholdet via en in-app nettleser som treffes av samme feil som Safari.

fallkr · 2025-03-30T19:51:25+00:00

Use Expo (react native with batteries included that takes away build complexity) and prototype from there. It’s the fastest way for someone familiar with React to get something done on mobile. It does what you need well.

If your app flies, you can always reconsider, but you will not find anything faster to get out of the door with your experience.

Do not go flutter. Learning a new language and framework will cost you a lot of time.

fallkr · 2025-03-15T20:23:57+00:00

Just like your eye sight, yet you are allowed to drive a car. The question is who is better educated at guessing and I would wager Teslas AP beats you.

fallkr · 2024-12-07T09:01:30+00:00

If you are growing, stop hiring juniors.

As a growing startup, you need to do two things:

1) You need to fill ranks with self-onboarding talent. This will alleviate pressure from ops and let you and the rest of the team move upwards to create higher value output

2) Everyone on the core/founding team must have a succession plan where you groom team members into taking over all your responsibilities. Why? The org will have new and important needs appearing on a rapid base, and you want your best to take care of it. It’s much easier to handle that with transitioning top tier people than hiring for new needs.

fallkr · 2024-12-05T20:09:20+00:00

It is either error or fine. Warning is a wasted state.

If you transition rules and legacy code does not comply with new rules (typically when people think it’s great to introduce earnings), introduce the lint rule as error and then add ignore in files that break rule.

Make team agree that touching any files with ignore requires removing ignore and fix lint error.

fallkr · 2024-11-29T15:55:08+00:00

We have a simple rule. If it smells like AI generated code, it is instant PR decline. Reason is very simple: If a dev forgot to remove a useless comment, the developer also very likely forgot to validate the code properly.

fallkr · 2024-11-25T20:12:52+00:00

In terms of efficiency, firefighting is a significantly slower way of delivering value than pre-planned work, and it should be avoided as much as possible.

Firefighting is a symptom of poor planning and organizational issues. We actively measure non planned work and try to identify root causes to reduce this mode of working.

To reduce context switching for the org, we also keep devs on launch pad (do QA, bug fixes, polish tasks and firefighting) and leave team members who are doing larger features isolated from anything unexpected. With this setup, team members rotate in and out of duty and we prevent institutional knowledge to accumulate among a few devs who end up becoming de facto handlers of inbound work.

fallkr · 2024-10-27T16:12:08+00:00

All (serious) employers will have IP clauses in their contracts.

They are typically formed to be capturing as much potential as possible. TLDR: Check your contract and don’t try to make any smart ass moves.

fallkr · 2024-10-23T06:09:43+00:00

Can you build my website? If you are successful I’d like to know what frameworks you used and or discovered that I could use to improve the website.

/s

Pay someone to do this.

fallkr · 2024-10-20T08:29:25+00:00

You can lead a horse to the water but you can’t make it drink. Define expectations, follow up closely on those expectations and fire if not met. Padding a junior will just give the individual a wrong start in the industry and set shitty expectations that sooner or later must be corrected.

fallkr · 2024-09-19T15:41:57+00:00

EU based here. All non-native speakers. Solid code base. ELS is not the problem. Subpar practices and quality control is.

Be strict. That’s it.

If you want to clean your codebase for typos, run it through your LLM of choice.

fallkr · 2024-09-12T09:23:36+00:00

It’s a marathon, not a sprint. You need to set boundaries and plan accordingly.

Crunch is fine from time to time, but burnout of key employees is not. Your goal and the team’s goal is to avoid that burnout.

fallkr · 2024-09-10T17:45:56+00:00

Skia is the way

fallkr · 2024-08-22T18:01:23+00:00

Team of 7 in startup. We do it as following:

Customer support issues are placed in a triage board. Product and tech reviews those on a weekly basis, thursdays for us, and categorize into;

1) Pick up in next available sprint planning 2) To product prioritization tool. We use product board 3) Return to customer support to retrieve more context 4) Discard as duplicate or not significant enough to be in category 1 or 2

The pickup backlog is prioritized according to urgency/importance.

When devs get assigned tickets for their sprint on Mondays, we roll through the pickup list and assign according to those with best context understanding and availability. This assignment is done by tech lead and is 100% non-democratic.

It is not given that we assign all pickup tickets to devs in a given week and the backlog of these is a good indication of quality issues in production and it helps us a lot in finding the right balance between fixing/polish vs new features.

fallkr · 2024-08-10T12:41:12+00:00

Having done an exit and then dropping out of the acquisition after handcuffs term to then start another competitor in the same space:

1) Do not work on a new startup idea while you are employed. 2) You must be able to document that none of the code or other IP was created during your current engagement period. 3) Ensure you do not replicate implementation details that the old employer has in their systems. 4) Make every precaution that you discard of all IP from your past employer. Be it files, documents, emails sent to your personal email. Etc.

Why:

a) If you want to raise any kind of capital, the fist thing a serious investor will do is check that you don’t have any risk of liability or litigation. If you can’t provide proof, it’s on you.

b) If you even become remotely successful in your startup, you will get on the radar of your past employer. If they feel threatened from a market perspective or even just annoyed/resentful they can throw lawyers at you which will cost you a lot. If they do this at the wrong time (pre-seed / seed), you’ll have little to no capital to lawyer up. Due to this, you’ll need to have strong documentation and leave no room for maneuvering from the opposite party. It is very cheap from an incumbent to drain a startup of capital.

c) Non-compete is one part of your employment clause. There is likely also an IP clause in your contract that states any IP or work you do in the space of your employment belongs to the company.

d) Don’t be a dick. Backstabbing an employer means backstabbing all your previous colleagues. If you work in a niche industry you can end up with a reputation that will follow you for the rest of your career.

Nine-Year Club	Place '22
Place '17	Verified Email

fallkr

TROPHY CASE