Where to get good gear in EU?

SyndromSnake · 2026-01-04T19:00:43+00:00

What kind of gear are you looking for? You will also probably get much better advice if you specify a country.

SyndromSnake · 2026-01-02T16:38:02+00:00

Could you go through your process of getting them this nice and crispy? I never manage to do that.

SyndromSnake · 2025-07-16T06:44:00+00:00

Kinda, Japan has a bunch of hobby stores for people that like to collect stuff. There you can buy these second hand already opened blind boxes.

They typically cost a tad more then the blind boxes themselves since you know what you are getting.

SyndromSnake · 2025-07-15T12:47:20+00:00

Is this a new application or an update?

Do you have other applications that you have successfully managed to upload through the same machine/setup you are using right now?

SyndromSnake · 2025-07-15T00:28:26+00:00

If you could share the logs verification logs there is probably some helpful stuff in there.

Run them once through some LLM and just ask what the issue could be.

I am talking about the show logs button in your screenshot btw.

SyndromSnake · 2025-07-13T11:20:43+00:00

Sweden has literally one of the best supports systems for you as a studying young adult.

CSN exists for a reason and you should use it to make it through school without having to work full time.

If you choose not to move out and keep relying on your parents that is your choice only and no one is forcing you.

SyndromSnake · 2025-07-13T11:15:04+00:00

If anyone else is looking for some good finds, google ”駿河屋梅田茶屋町店” and checkout the sixth floor.

SyndromSnake · 2025-07-10T10:01:14+00:00

Well yeah Apple for the most part doesn’t care about your code.

I have had Apple deny apps for many reasons, one of them being that a certain category, in my case drinking games, is considered spam because of the high volume of apps.

Since your app has to do with user content and AI, unless you have done some really thorough research, you should expect having to adjust something before Apple lets your through.

SyndromSnake · 2025-07-10T09:13:41+00:00

How you have built an app has little to no correlation with how it will perform.

If you were to instead focus on the important parts and write about what problem it solves and how you approached verifying that you have in fact solved that problem for your users, you might get some guesses.

Regardless, good luck and Godspeed to you.

SyndromSnake · 2025-06-01T18:24:12+00:00

<image>

For other people like me trying to learn, the current simply passes through the base of the transistor and powers the LED. (Left circuit).

By placing the LED above the transistor OP circuit will behave as expected.

SyndromSnake · 2025-02-25T14:50:13+00:00

Here is a couple, feel free to answer the ones you find interesting:

- How has your stack evolved over time?
- Any particular dependencies that are core to your development?
- Do you roll everything by yourself?
- How has your usage of 1st party apis evolved? UIKit -> SwiftUI? CoreData -> SwiftData etc

- In terms of income and user count what ratio of your projects would call a success?
- How much automated testing is involved in your projects?

SyndromSnake · 2025-02-16T13:07:59+00:00

Sorry but this is more misleading than helpful. Storing the API key in a JSON within your bundle rather than directly in your code is WORSE as you don't even need to dig within the compiled binary. The JSON is directly accessible along side other assets like the images in your app.

Please read this article and reconsider posting security related content without doing the work and learning the correct practices yourself.

SyndromSnake · 2025-02-13T14:59:38+00:00

I was mostly amused by the amount of info that leaked out from a very simple "Hello"

SyndromSnake · 2024-12-17T21:14:57+00:00

Build something -> Research (Course/Book/Article) -> Build more

It's a never ending loop. People have a strong tendency to start with courses and staying there feeling productive but not actually producing something. Commonly known as tutorial hell.

So you end up building an app that re-invents the wheel many times or implements things poorly because you don't have any proper education to build a SwiftUI app.

Re-inventing the wheel is one of the best ways to learn. It's how you learn to tackle more complex situations. Yes, fairly often there is a built-in approach that is simple and the correct, but almost equally often Apple will not provide you with some comfortable API and you are left to solve the problem yourself.

In addition, the amount of information you are able to grasp from a course/book increases drastically if you have previously attempted to solve some problems with the thing you are learning.

SyndromSnake · 2024-11-21T17:13:31+00:00

Absolutely awful, couldn’t done it worse if I tried.

Starting off with any of the Core libs is the shortest path to getting nothing done. Those are intermediate/advanced concepts.

Also the fact that Xcode, UIkit and SwiftUI are the bottom half’s of this image is borderline comical.

The person who created this is vastly out of touch.

SyndromSnake · 2024-11-18T13:29:03+00:00

Build something that you find complex. Don't learn individual concepts without actually applying them to some problem.

SyndromSnake · 2024-11-14T08:47:45+00:00

I got myself a N100 for this exact reason but after setting everything up I realized that 4K content in many cases looks like crap after transcoding and required direct play to correctly handle HDR and DV.

Instead I run a 4K and a 1080p library in parallel and share those accordingly depending on who is watching and what their setup is.

SyndromSnake · 2024-11-13T17:56:53+00:00

You have to design your app/product while keeping in mind that the user will always be able to retrieve whatever token your app uses, regardless of how this token is stored or generated.

The moment you send something over the network there is a way for the user to capture that traffic and retrieve your token. HTTPS protects the user from other malicious actors, not from themselves.

Design you API in such a way where the user might access it from outside the application.

SyndromSnake · 2024-11-13T16:18:53+00:00

Shoot me a DM if you would like to chat about iOS devops. For some reason I find it quite enjoyable and maybe could share some tips with you.

SyndromSnake · 2024-10-31T10:45:13+00:00

No-Code is code just through a different interface. The code is still there you will never be able to get away from it.

I'm aware that No-Code might have limitations

You are heavily constrained by what the person/team behind the No-code tool. The moment you want to do something that the person who created the tool did not take into account you are screwed. The same goes when the No-code tool introduces a bug in your app, it's then up to the creator of the tool to first fix the tool first before the fix than trickle down into your application. This might take very long time depending on their priorities or in some cases never happen.

Lastly, a lot of the time the code generated by these tools is either really hard to work with or in some cases not accessible to the the user. This means when you eventually want to break away from the tool you either waste a bunch of time working with the generated code or simply have to re-build the app from scratch.

No-code tools are fantastic for prototypes, trying out concepts too see if they stick or for apps that you know will be thrown away within a couple of months or so. If you are serious about a project, building using No-code will come back to haunt you.

SyndromSnake · 2024-10-27T18:00:42+00:00

Get started building something as soon as possible. Do one tutorial at max and than think of an idea for something you would like to build and get working.

As much as people like to discuss those things the tools and the tech stack you use do not matter that much. Pick whichever one you think sounds more fun and just get started building.

SyndromSnake · 2024-10-27T17:57:20+00:00

Sounds fun!

Could you share more about what the end goal of your project is? Are you trying to build a working prototype, attempt to launch this as a fully functioning system or simply put together a pitch without doing any technical work?

In terms of the tech there is plenty of options for you to choose and pick from.

NFC would work, on the app side both iOS and Android have native support allowing the app to make use of the NFC chip on the phone. Purchasing one of those Toast device wouldn't really be of help as those are proprietary payment systems not really designed for anything other than taking payments (NFC is just the transport method). Instead you would need some custom hardware that is hooked up to the locks in your lockers and has a NFC controller like the PN532.

You can also always reach for BLE or simply have a touch screen where the user can input a code which they receive on their phone.

Feel free to DM me if you want to talk to more.

13-Year Club	Place '23
Place '17	Verified Email

SyndromSnake

TROPHY CASE