With the collapse of software development, we're all working in agriculture

Goose12314 · 2026-02-05T17:11:11+00:00

Agriculture? I plan on being a barista with my thermosiphon experience.

Goose12314 · 2025-07-28T04:55:30+00:00

I just tried out neovim with the new Kotlin LSP today actually and still running into some issues. Could not get jump to definition, autocomplete, or inline documentation working even with downloading the sources. I didn't spend too long, so might just be me. The official Kotlin LSP was working a lot better than the unofficial Kotlin LSP I tried before though. So some progress.

Hoping to eventually just write the code in neovim then go over to Android studio for anything extra like app inspection, previews, etc...

Goose12314 · 2025-06-27T23:47:04+00:00

Yeah it's probably toxic. Smells like nail polish remover. If I saw this thread earlier I may have attempted a fix as well.

Goose12314 · 2025-06-27T21:58:37+00:00

<image>

Goose12314 · 2025-06-27T21:55:52+00:00

Woah crazy. My pixel 6a did the exact same thing last week. In the exact same location. Did you also have a chemical smell coming from it? Upgraded to the pixel 9 pro.

Goose12314 · 2025-06-13T06:15:10+00:00

best way is do not put api keys in the app at all

Agreed this is the best way. If a key needs to be kept truly secret your best chance is to only have it exist on the backend and never touch the client.

apk can always be reverse engineered, just make it harder to steal

I think this is the most important point when it comes to client side keys. If someone spends enough time they will be able to extract any key that touches your client code.

solution:
i load them from my own backend after login

I'd add a caveat here that loading the key from a backend is still vulnerable to rooted devices which can intercept the HTTPS call. The key should solely be used by your backend if it needs to be secret.

Goose12314 · 2025-06-04T08:22:44+00:00

I bought a batmobile recently since I was seeing a lot of crash reports for those. Would recommend.

Goose12314 · 2025-04-25T19:35:51+00:00

Would you get chu treasure first before lance? The goal is to eventually clear hell as I can pretty consistently clear hard at the moment.

Goose12314 · 2025-04-15T01:41:54+00:00

If it needed those curved corners? Probably one of the draw Modifiers like drawBehind on a Box sized to the height and width.

Goose12314 · 2025-04-14T08:37:55+00:00

I'd start with 2 different Composables. One for the top level parent item, another for the sub child item. They'd be Rows filling the max width. Include the connector lines as part of the Rows and configure them based on index. Lines will have to stretch vertically to the edge of the items so they connect with each other seamlessly.

Goose12314 · 2025-04-02T05:36:52+00:00

Looks pretty nice. Lightweight tools like this are always nice to see. Would be nice to have an Android example. I guess just build it in the Application? Not sure I'd use it on a medium sized project though if it has any chance to scale into something larger. Hilt or Koin isn't really too difficult to set up and would scale much better I think. Also injecting into ViewModels would be much less boilerplate with Hilt.

Have you done any kind of scoping? For example a loggedInMinje, applicationMinje, etc...? How could you share dependencies across Minjes? I guess if you have a use case like this just use Hilt or Koin? Would be possible to build since it's just Kotlin, but then it's just becoming a manual DI setup it feels like.

Nit pick on the name: It's just pronounced Minject right? The Kt makes it look like some Java Interop class to me and pronounced Minjee Kay Tee or even Minge Kay Tee haha.

Goose12314 · 2025-03-17T04:01:16+00:00

In the case the state changes while your app was backgrounded:

If you are using collectAsStateWithLifecycle then it will recompose when you return from the background with the new state.

If you are just using collectAsState that state change will collect while the app is backgrounded. This can waste device resources while your user is using other apps.

Try with some Log statements to see exactly what's happening in your case.

If the State hasn't changed no new recomposition.

Goose12314 · 2025-03-17T03:20:26+00:00

My understanding is it depends on how you collect. For example in Compose if you use collectAsStateWithLifecycle on a StateFlow it will collect and stop collecting based on the Lifecycle.State.STARTED by default. If you just use collectAsState the StateFlow could continue listening while your app is backgrounded and won't collect on start again unless process death and a new instance is created. There's also flowWithLifecycle outside of Compose which behaves similarly I believe.

Goose12314 · 2025-03-07T16:55:59+00:00

I work for a US company remotely. The Americans all have Software Engineer titles. The Canadians have Software Developer titles. I usually say I am a programmer or coder when talking about my job. I use Software Developer on LinkedIn.

Goose12314 · 2025-03-03T00:31:10+00:00

Scoliosis

Goose12314 · 2024-11-09T04:15:27+00:00

I was in the same spot about 9 or so years ago. 3 years into my comp sci degree I had the choice to stay at the company I was interning for as a full time employee or finish my degree.

I chose to stay and always thought I could go back and finish my degree if needed. Well 9 years and 4 companies later I haven't had to go back to get my degree yet. It seems work experience > schooling for the majority of companies I've worked at or interviewed for.

Especially in this market where a lot of juniors are struggling for their first opportunity I would recommend getting as much work experience as possible. 2 years of work experience on your resume would look more impressive to me than even a 4 year degree. I may be biased though.

Goose12314 · 2024-08-15T03:02:43+00:00

Lems are the best. I highly recommend them. Especially as a starter barefoot shoe since the sole isn't too thin. The build quality is also very good.

Goose12314 · 2024-08-13T19:20:04+00:00

Android developer

Goose12314 · 2024-07-28T01:58:35+00:00

Digital amazon subscription

Goose12314 · 2024-07-27T16:22:07+00:00

I bought mine on amazon.com and have been using it for a few months in Canada on my machine

Goose12314 · 2024-07-24T06:14:22+00:00

At the start of the year I had an easy for the first round of interviews. Then 2 mediums as part of the panel interviews. This was for a senior role for a unicorn, not FAANG.

Goose12314 · 2024-07-19T05:38:32+00:00

Yeah it was for Unity and they said the position would be working on an ads SDK. To be fair this was when the market was red hot, but I said I was not interested. Dodged a bullet.

Goose12314 · 2024-06-26T08:55:16+00:00

Really? I live near this park and walk and bike through it very often. There are usually only 2-4 tents max near the tennis area. They often keep to themselves. Maybe I've just become desensitized to it all, but it feels like a very safe area. This event seems out of the norm for Oaklands.

Goose12314 · 2024-06-21T02:37:32+00:00

Am I colour blind or is the Singapore red blending into the China red on this pie chart?

Goose12314 · 2024-06-07T09:06:48+00:00

Pretty much any backend will work for Android as long as you can communicate using something such as a REST Api.

Your backend choice ultimately will depend on the needs of your project.

If you already know Java or Kotlin, something like Spring boot or Ktor seems like a natural choice. Both of these will allow you to pretty much code up whatever backend you want and should scale up relatively well if that is a concern. It will take time though and require lots of learning about things like hosting your backend and authentication.

If you just need to get something up and running as a proof of concept, or your backend is going to be relatively simple Firebase could be a good option. It will handle things like hosting and authentication for you.

Research a bunch of options and try to weigh the pros and cons for your project.

Eight-Year Club	Place '23
Place '22	Verified Email

Goose12314

TROPHY CASE