What's something you're good at? And what advice to you have for those who aren't good at this thing?

Programming.

My advice for those looking to learn? Power through the beginning where you learn the basics with Java/Python/C++/whatever you've started with, then start working on stuff that interests you ASAP. Find projects or ideas that directly interest you and start to build them. Even if you go for something too ambitious at first, you'll learn a lot in the process.

I'm the person people go to, to talk to.
I learned how to listen about a decade ago, and I have my friends full confidence. They come to me for advice about things, or to work through their feelings about something. The secret sauce is, I think, validating their feelings. You don't have to agree with what they're feeling about something, or how they're handling it, but internalize how they're feeling and do your best to understand how they came to feel that way. Empathize. We're talking apes, flying through the cosmos on a bluey-green spaceship, and nobody knows what we're doing here. Not really. Cut your friends some slack, and they will come to you. You will open an avenue of closer friendship, and deeper intimacy, than you might have thought possible.

Also, I'm allegedly "good at snapchat", whatever that means.

Solving problems. It's vague and it probably sounds kind of boring, sure, but it's the underlying interest that ties together a lot of the things I enjoy, from programming, to tinkering with things, to playing with puzzles, and even improving my cooking.

As for advice for getting better at solving problems, it boils down to a few essential points:

• Practice. Seriously, just practice a lot. Solve any problem and it will exercise your problem-solving skills. It will help you figure out the best general process for approaching problems, which is incredibly transferable across different disciplines. Moreover, you'll get comfortable with the problems you're solving, so when those problems end up being part of larger, more complex problems, you'll be able to identify and solve those parts easily.
• On that note, learn to view large problems as just a collection of smaller problems. Isolate those smaller problems and solve them, and before you know it you will have solved the larger problem.
• Challenge yourself. Is that problem you're working on easy? Or is it a challenge that you've been banging your head against for hours? If it's easy, then it's like taking a brief walk. Sure, it will help keep you in shape, but it's not going to make you any stronger. But intense workouts that end up making you sore afterward? Those will make the workouts that seem difficult now feel trivial in the future. The same goes with challenging yourself mentally!
• Expose yourself to different problem spaces. Take math for example. Sure, it's technically more difficult to add and subtract many large numbers vs. a couple of small ones, but if all you're ever doing is making the numbers larger and throwing more of them in the mix, you're not really doing yourself a favor. You need to step out of that comfort zone and start getting comfortable with concepts like multiplication and division, working your way up to things like geometry, algebra, and possibly calculus. Willful exposure to new kinds of problems means you're less likely to get completely lost when a new kind of problem inevitably hits you unexpectedly down the line. You may even find that you recognize a type of problem you've solved before in a place you weren't expecting!
• Learn to walk away from a problem. No, really. Sometimes you just don't have the capability of solving the problem yet, and that's okay, just come back to it later. Or, maybe it's something you definitely can solve, but for some reason it's stumping you, in which case walking away from the problem allows you to avoid tunnel vision and fatigue and your brain can mull over the problem in the background while you screw around doing something else. That last bit is a very real thing, and programmers in particular know that walking away from their screens can often be more productive than sitting in front of it!
• Experiment. Always be asking why things work the way they do, researching the answer or coming up with your own ideas, and then testing to see if your understanding matches up with reality. If you can see the pathway from action to result first-hand, then you'll understand the problem better. What should happen if I change X? What do I expect to happen if I remove X entirely? What's so important about X, anyway? Asking yourself these kinds of fundamental questions and trying to squeeze the answers out yourself can be incredibly valuable, and in the process the new understanding you gain will stick a lot better than someone just telling you.
• Don't be too quick to dismiss a problem as impractical or more difficult than anything else you'll have to do in the real world. Going back to the exercising analogy, think of difficult problems like weightlifting or bench pressing. When are you ever going to have to lie on your back and repeatedly lift and lower a heavy object? When are you ever going to have to pull your chin above a bar? When are you ever going to sit down and repeatedly do curls with the same heavy object? Realistically, probably never. But it does make you stronger, and when the time comes that you have to lift something heavy e.g. you're moving furniture, it'll end up being way easier than if you never did those kinds of exercises.
  I could go on about this subject for quite a while, but I've already added quite a bit, so I'll stop here :)

Talking in front of groups of people.

I did some theater in middle school and high school and I think that helped significantly. I ended up in a career that's entirely non-theater related, but that does require me to speak to groups of people frequently. I'm pretty comfortable with it now. While I will sometimes type out what I want to say, I almost never rely on my notes when I'm actually doing it. It's better if they serve as a vague outline for a presentation and I just read the crowd and go with whatever fits best. I often speak to children and while they can sometimes be a brutally judgmental audience, they're also often really easy to get excited.

I'm alright at giving presentations, whether it's for groups or small committees. My advice in every case would boil down to a few points:

• Speak clearly and in a set Rhythm, don't over-compensate for a perceived lack of emotion, don't be as dry as possible. Talk the way you'd talk in normal life. If you're still unsure speaking/enunciation courses are actually pretty useful.
• Speaking somewhat slower and more understandable beats being detailed, nobody is going to be impressed if they can't follow what you're saying.
• Look around, let your eyes rest on people every now and again, even if they don't respond. Avoid continuously looking at your slides (if you have them)
• Don't recite or read from notes, it's going to make you stilted. Learn the global points and precise details and improvise the connective text between them.
• That said, do practice beforehand if you can. Mostly to see if you remember your points and talk about them in order.
• Keep your slides simple, you don't need to do it TED style but a few images and bullet points with specific details are fare more useful then walls of text.
• If you're using your slides as notes you're doing it wrong. (see above)

My English and Spanish are really good (I think)

My advice for learning a new language would be to immerse yourself with it. Buy a book that teaches the language, download Duolingo or some language learning app, find chat groups in that language and use a dictionary to try to communicate, listen to music, watch movies, read books, play games in that language, etc...

In a nutshell, try to get as much contact to that language as you can and try to understand it. If you follow that path and you keep going, you will get better little by little until one day you'll be really good at it to the point that it feels second nature

I'm a security and network analyst and a good portion of my job is to help troubleshoot problems that aren't necessarily network issues (it's never the network /s).
My biggest piece of advice is learn basic network troubleshooting tools and thought processes.

If you can't get to a website or something out on the network, try pinging (open command prompt, type "ping $destination"). This doesn't always guarantee a result either way if firewall policies block ICMP (network protocol that ping uses). This also helps to determine latency as the response time is also displayed when running the command. Run "ping -t $destination" to have the command run in perpetuity, useful when doing testing or basic monitoring, saves running the command over and over again.

Another option to see where a potential issue may arise as to traceroute (tracert $destination). This will hit each router in the path to the destination, useful for determining a tiring issue, either if you can't get to a destination or if you're curious about the path your network traffic is taking too get to a destination.

The final piece of advice I have to give is for technical issues overall. Do some initial research and testing. If a user or sysadmin comes to me with an issue that they'd like my help investigating, I will go the extra mile for someone who can tell me what they've already tested and go into any more detail than just "it doesn't work". I much prefer helping people who try to retain information or learn so I don't have to do the same thing over and over again and self-research is a huge signal of at least some effort which I hugely support.

PS: If you need technical help and don't have anyone to ask, shoot me a message and if it's in an area that I have knowledge/experience in I will definitely try to help.

I am very good at procrastinating.

I am a dedicated, focused procrastinator.

I'm pretty good at editing. I'm good at taking the work of other people, seeing its strengths and weaknesses, and improving it, giving feedback, and creating new features off of a strong platform. I'm something of an early adopter, but I'm not usually a bleeding-edge user and rarely a creator.

I have found out how to take this ability and bend it into other useful abilities. I'm a decent project manager. I'm not likely going to build some new program or start my own business, but I'm good at coordinating people and getting them to work together on that new program or new business. I can "edit" behaviors and habits and turn them into something a little more efficient.

And I can "edit" a person's beliefs to teach them new things. I can see the strengths and weaknesses in their understanding of the world--where it is shaky, and where it is strong. And I can help them to strengthen the shaky parts--that's why I'm studying to be a teacher.

It's something I first realized about myself in some form when I was little. I would play lots of strategy games and I always loved to organize my party/team and strategize on how to beat the next level or accomplish some goal. And then I realized I liked that in real life too.

I can throw a disc (frisbee) pretty well, in a variety of different ways. Mostly it comes down to manual dexterity and strength, so if you want to get good a throwing a disc, there's three things to do:

• throw several thousand discs
• work out to accumulate strength
• throw several thousand more discs