Creative people consistently say that they don't spend a lot of time thinking about what they want to create. They just work on something. Often something nonsensical and useless. Sometimes something that's meant to practice something they want to improve upon. Sometimes it's half of an idea. Almost always it's something that won't ever be finished. In the process of working on whatever it is they're engaged in, they get ideas for the next thing they want to work on. That's how ideas come. Not from thinking about what the next idea will be, but by being engaged with an existing idea.
An easy way to start is to start journaling. Write down something good that happed during your day. Elaborate on it. Write your thoughts. Don't edit them or care about spelling or grammar. Just engage with your existing thoughts.
I wouldn't expect that you could go from zero experience with Neovim/Vim to more efficient than the editor you've been using extensively in less than a month. most of the people that responded here had been using Vim prior to switching. The one that had no prior Vim experience took half a month to get the basics down and be comparable with their prior editor (VScode).
Everything you're after is available, but trying to learn it all at once can be overwhelming as you've been experiencing.
Reinstall a fresh stable version of NeoVim and if you haven't already followed the tutorial, follow it.
Install ripgrep for full, in file, text search for the current (or specified) directory.
Install kickstart.nvim and watch the kickstart.nvim walkthrough video to learn how configuration and plugins work in Neovim. (It also includes a Fuzzy Finder [fzf] that works with ripgrep inside of NeoVim.)
Practice Vim Motions so they become second nature to you. Watch the first 5 videos of The Primeagen's Vim Video Playlist to see the fundamental movements beyond what's in the tutorial. You could use a VSCode extension that replicates Vim Modal Editing with Vim Keybindings to get used to the Vim Motions while you're still using VSCode.
Get familiar with the Neovim User Documentation which han be accessed and navigated with Vim Motions by typing :help while in Normal mode in Neovim
Watch videos on multiword/mulitline editing options with Neovim (Part 1) | (Part 2)
The best chat beginner community for Neovim that I know of is in The Odin Project Discord. There's a Neovim thread in the #odin-general channel there. (Bonus, while you're in the Discord you can help out others trying to learn web development.)
The point is to find your own way by learning from others, not to simply mimic others. Although up front, mimicing what others are doing is a good way to get started.
Unfortunately, in this case I'm not interested in a summary. I already watched the video and would need to refer back to it for details, not general concepts.
I'll definitely use that site in the future though.
Edit: looks like it's not so good for long videos.
It's a shame that he didn't do a writeup on this. It's nice to have a video to demo the workflow, but it's really annoying to go back to the video to get details to try it yourself.
Well I kinda suck at this moderation thing. I read this post previously, not realizing that it was in CSCareerQuestions. This post probably doesn't fit here as is. But it's been 2 days and wouldn't be worthwhile asking for you to edit your post to present a clear question at this point.
In the future, please include a question in your post in this community.
I don't think this gets at what they are trying to do. I think they want to set up access control to the repo. They want access to the repo to be private but also use it for themselves like any other repo.
This is something companies do, but I believe acess control is by firewall/VPN not the repo tools. As far as I can tell, if you can access the IP address of the URL assets you can get the assets. So making it private is a matter of setting up access to the server(s) not a configuration of the tools that manage the repository.
I'd ask on a debian focused irc/chat room/ mailing list to find out more.
I prefer Podverse, you can pay $18 per year (after a 3 month trial) to have multiple devices sync through a hosted account or just use the clients independently or host your own host your own instance.
The only thing it's missing for me is an easy way to get to the source url or download the media to your device.
Overall I'm happy to pay them $1.50 a month for them to keep it actively developed.
I try to be positive here on programming.dev but someone gave you an incredibly thoughtful reply and you returned the favor with absolute disrespect. I think the only positive outcome here would be for me to simply block you and encourage others to do the same.
I'm going to throw this out there not being sure how true it is, but I find it interesting to think about.
XMPP is much more widely used than Matrix if you count WhatsApp (Meta/Facebook). ActivityPub is much more widely used than AT Protocol and nostr combined if you count Threads (Meta/Facebook). So reasons why people aren't talking about XMPP include not wanting to recognize that Meta is hugely influential in this space and that most people don't talk about the underlying protocols of the services and tools they're use at all leaving a self selected group of people looking for alternatives with traction that don't depend on Meta. Outside of WhatsApp, there's not a lot of traction with any particular XMPP implementation. And none of the XMPP implementations have a Discord-ish organization of chat rooms that's popular and familiar right now. Matrix has both right now (although I don't think it will ever be more than a small niche in the mobile messaging space).
I'm fine with using Matrix for what it is. There are programming language communities that have been very helpful for me and a number of Lemmy related communities that have been nice to be a part of.
No. There are a lot of small frustrations that add up to a sense of futility. These frustrations can only be addressed one at a time and are annoyingly orthogonal to the task you're trying to complete.
Even more frustrating is that the people who write tutorials are typically well past that early stage of learning and have forgotten about many of the little details they no longer need to think through and are unconscious of the knowledge they are leveraging gained from their early stage of learning. So you can find a lot of tutorials that simply don't address the issues you are likely to run into. Which is understandable to not want to include every possible issue in a focused tutorial, but there are often no hints or resources linked to help someone with the unstated prerequisite knowledge.
Also, you seem to be using Linux and that tutorial has a bunch of screenshots examples for MacOS. This is another annoying trend from the silicon valley based developers of assuming that everyone outside of their bubble is using the same technology stack as they are and often the newest and most expensive hardware options. (Which I suspect is a big influence on Android Studio being as resource heavy as it is.)
Do I have to use Android Studio or it there some kind of native linux alternative?
You don't need to use Android Studio for Android development, but it's probably the path with the least friction for getting started.
But there are a few non-Kotlin options for Android development, Flutter and Progressive Web Applications (PWAs) are two different pathways for Android development which don't require Kotlin.
Ultimately, I suggest that you stick with Android Studio and learn the annoying details that it requires to be used effectively. You'll feel like you're moving much slower than you want to at first but you'll get up to speed eventually. And you can ask here or on forums or chat rooms for help as you're figuring out the details of Android Studio.
My takeaway from this is to use CSP to minimize your reliance on others doing things intelligently. And that Datadog is not doing things intelligently at the inconvenience of their consumers.
The authors of the blog post seem aware of the limitations of their focus:
In contrast, ReLU and its variants are often preferred for the hidden layers on large datasets and deeper models as they accelerate training. CNNs frequently benefit from the ReLU variants and the Swish activation function. When training a DNN, Leaky ReLU is generally a good starting point. Alternatively, one can chose ReLU activations and inspect the percentage of dead neurons, switching to LeakyReLU or PReLU if required. GeLU shines in NLP tasks despite its computational cost. Swish, while promising, is relatively new and requires further exploration, interpretability and testing.
The activation function landscape is rich and diverse, offering a spectrum of choices to cater to various neural network needs. I hope this guide served as a good starting point for more exploration based on your requirements and network design.
Keep us in the loop 🤠