#best app development programming languages

Mistake 1: Asymmetrical Studying

Assuming you don't just want to do a single activity in a language, or are learning a language like ASL, a language requires 4 parts to be studied: Speaking, Listening, Writing, Reading. While these have overlap, you can't learn speaking from reading, or even learn speaking from just listening. One of my first Chinese teachers told me how he would listen to the textbook dialogues while he was biking to classes and it helped him. I took this information, thought "Yeah that's an idea, but sounds boring" and now regret not taking his advice nearly every day.

I think a lot of us find methods we enjoy to study (mine was reading) and assume that if we just do that method more ™ it will eventually help us in other areas (sometimes it does, but that's only sometimes). Find a method that works for you for each area of study, even better find more than one method since we use these skills in a variety of manners! I can understand a TV program pretty well since I have a lot of context clues and body language to fill in any gaps of understanding, but taking a phone call is much harder—the audio is rougher, there's no body language to read, and since most Chinese programs have hard coded subtitles, no subtitles to fall back on either. If I were to compare the number of hours I spent reading in Chinese to (actively) training my listening? Probably a ratio of 100 to 1. When I started to learn Korean, the first thing I did was find a variety of listening resources for my level.

Fix: Find a variety of study methods that challenge all aspects of the language in different ways.

A variety of methods will help you develop a more well-rounded level of mastery, and probably help you keep from getting bored. Which is important because...

Mistake 2: Inconsistent Studying

If there is one positive to a language app, it is the pressure it puts on keeping a streak. Making studying a part of your everyday routine is the best thing you can do. I benefited a lot from taking a college language course since I had a dedicated time to study and practice Chinese 5 days out of the week (and homework usually filled the other two). Memorization is a huge part of language learning, and stopping and starting is terrible for memorization. When I was in elementary school, we had Spanish maybe a couple times a month. Looking back, it seems like it was the first class to be cut if we needed to catch up on a more important course. Needless to say, I can't even speak Spanish at an elementary level.

However, I'm sure many people reading this don't have the time to do ultra-immersion 4-hour study sessions every day either. Find what days during the week you have time to focus on learning new vocab and grammar, and use the rest of the week to review. This can be done on your commute to school/work, while you do the dishes, or as a part of your morning/evening routine. Making this as realistic as possible will help you actually succeed in making this a habit. (Check this out for how to set realistic study goals)

Fix: Study regularly (ideally daily) by setting realistic goals. Avoid "binge" studying since remembering requires consistent repetition to be most effective.

Mistake 3: Resource Choice

This is really composed of two mistakes, but I have a good example that will cover them both.

First, finding resources that are at or slightly above your level is the most important thing. Easy resources will not challenge you enough and difficult resources will overwhelm you. The ideal is n+1, with n as what you know plus 1 new thing.

Second, getting distracted by fancy, new technology. Newer isn't always better, and there are often advantages that are lost when we've made technological developments. I often found myself wanting to try out new browser extensions or organizational methods and honestly I would've benefitted from just using that time to study. (Also, you're probably reading this because of my DL post so I don't think it has to be said that AI resources suck.)

A good example of this was my time using Clozemaster. I had actually recommended it when I first started using it since I thought the foundation was really solid. However, after long term use, I found that it just wasn't a good fit. The sentences were often too simple or too long and strange for memorization at higher levels or were too difficult at lower levels. I think that taking my textbook's example sentences from dialogues into something like Anki would've been a far better use of my time (and money) as they were already designed to be at that n+1 level.

Fix: "Vet" your resources—make sure they will actually help you. If something is working for you, then keep using it! You don't always have to upgrade to the newest tool/method.

Mistake 3.5: Classrooms and Textbooks

A .5 since it's not my mistake, but an addendum of caution. I think there is a significant part of the language learning community that views textbooks and classroom learning as the worst possible resource. They are "boring", "outdated", and "ineffective" (ironically one of the most interesting modern language learning methods, ALG, is only done in a classroom setting). Classrooms and textbooks bring back memories of being surrounded by mostly uninterested classmates, minimal priority, and a focus on grades rather than personal achievement (imagine the difference between a class of middle schoolers who were forced to choose a foreign language vs. adult learners who self-selected!) People have used these exact methods, or even "cruder" methods, to successfully learn a language. It all comes down to what works best for you. I specifically recommend textbooks for learning grammar and the plentiful number of dialogues and written passages that can function great as graded readers and listening resources. (Also the distinction made between "a youtube lesson on a grammatical principle" which is totally cool, and "a passage in a grammar textbook" is more one of tone and audio/written than efficacy).

Classrooms can be really great for speaking practice since they can be a lot less intimidating speaking to someone who is also learning while receiving corrections. Speech can be awkward to train on your own (not impossible if you're good at just talking aloud to yourself!), and classrooms can work nicely for this. Homework and class schedules also have built in accountability!

Fix: Explore resources available to you and try to think holistically about your approach. CI+Traditional Methods is my go to "Learning Cocktail"

Mistake 4: Yes, Immersion, But...

I realized this relatively quickly while learning Chinese, but immersion at a level much higher than your current level will do very little for you. What is sometimes left out of those "Just watch anime to learn Japanese" discussions is that you first need to have a chance at understanding what is being said. Choosing materials that are much higher than your level will not teach you the language. It doesn't matter how many times someone at HSK 1 hears “他是甘露之惠，我并无此水可还”, they will not get very far. Actual deduction and learning comes from having enough familiar components to be able to make deductions—something different than guessing. An HSK 1 learner, never having heard the word 老虎 will be able to understand "tiger" if someone says “这是我的老虎” while standing next to a tiger. This is not to say you can never try something more difficult—things should be challenging—but if you can't make heads or tails of what's being said, then it's time to find something a bit easier. If mistake 2 is about the type of method, this is about the level. If you wouldn't give a kindergartener The Great Gatsby to learn how to read, why would you watch Full Metal Alchemist to start learning a language?

Side note: Interesting video here on the Comprehensible Input hypothesis and how it relates to neurodivergence.

Fix: Immerse yourself in appropriate content for your level. It's called comprehensible input for a reason.

Mistake 5: On Translation

I work as a translator, so do you really think I'm going to say translation is all bad? Of course not. It's a separate skill that can be added on to the basic skills, but is really only required if you are A. someone who is an intermediary between two languages (say you have to translate for a spouse or family member) or B. It is your job/hobby. In the context of sitting down and learning, it can be harmful. I think my brain often goes to translation too often because that's how I used to learn. Trying to unlearn that is difficult because, well, what do people even mean when they say "don't translate"? They mean when someone says "thank you", you should not go to your primary language and translate "you're welcome" from that. You should train yourself to go to your target language first when you hear the word for "thank you". A very literally translated "thank you" in Chinese "谢谢你" can come off as cold and sarcastic. I don't tell my friends that, I say "谢啦～". Direct translation can take away the difference in culture, grammar, and politeness in a language. If there is a reason you sound awkward while writing and speaking, it's probably because you're imposing your primary language on your target language.

Fix: Try as hard as you can to not work from your primary language into the target language, but to work from the structures, set phrases, and grammar within the target language that you know first.

Mistake 6: The Secret Language Learners Don't Want You To Know...

...is that there is no one easy method. You are not going to learn French while you sleep, or master Korean by doing this one easy trick. Learning a language requires work and dedication, the people that succeed are those that push through the boredom of repetition and failure. The "I learned X in 1 year/month/week/day!" crowd is hiding large asterisks, be it their actual level, the assistance and free time available to them, "well actually I had already studied this for 4 years", or just straight-up lying. Our own journeys in our native tongue were not easy, they required years and years of constant immersion and instruction. While we are now older and wiser people that can make quick connections, we are also burdened with things like "jobs", "house work", "school work", and the digital black hole that is "social media" that take up our time and energy. Everything above is to help make this journey a little bit easier, quicker, and painless, but it will never be magic.

I find that language learning has a lot in common with the fitness community. People will talk about the workout that changed their life and how no other one will do the same—and it really can be the truth that it changed their life and that they feel it is the ultimate way. The real workout that will change your life is the one you're most consistent with, that you enjoy the most. Language learning is just trying to find the brain exercise that you can be the most consistent with.

Fix: Save your energy looking for shortcuts, and do the work, fail, and come back for more. If someone tells you that you can become fluent in a ridiculously short amount of time, they are selling you a fantasy (and likely a product). You get out what you put in.

For those that made it to the end, here are some of my "universal resources":

Refold Method: I don't agree with their actual method 100%, but they've collected a lot of great resources for learning languages. I've found their Chinese and Korean discords to also be really helpful and provided even more resources than what's given in their starter guides.

Language Reactor: Very useful, and have recently added podcasts as a material! The free version is honestly all you need.

Anki: If I do not mention it, the people with 4+ year streaks with a 5K word deck will not let me forget it. It can be used on desktop or on your phone as an app. If you need a replacement for a language learning app, this is one of them. Justin Sung has a lot of great info on how to best utilize Anki (as does Refold). It's not my favorite, but it could be yours!

LingQ: "But I thought you said language apps are bad!" In isolation, yes. Sorry for the clickbait. This one is pretty good, and more interested in immersing you in the language than selling a subscription to allow you to freeze your streak so the number goes up.

Grammar Textbooks: For self-taught learning, these are going to be the best resource since it's focused on the hardest part of the language, and only that. If you're tired of seeing group work activities, look for a textbook that is just on grammar (Modern Mandarin Chinese Grammar is my rec for Chinese, and A Guide to Japanese Grammar by Tae Kim is the most common/enthusiastic rec I've heard for Japanese).

Shadowing: Simply repeat what you hear. Matt vs Japan talks about his setup here for optimized shadowing (which you can probably build for a lot cheaper now), but it can also just be you watching a video and pausing to repeat after each sentence or near simultaneously if you're able.

Youtube: Be it "Short Story for Beginners", "How to use X", "250 Essential Phrases", or a GRWM in your target language, Youtube is the best. Sometimes you have to dig to find what works for you, but I imagine there is something for everyone at every level. (Pro tip: People upload textbook audio dialogues often, you don't even have to buy the textbook to be able to learn from it!)

A Friend: Be it a fellow learner, or someone who has already mastered the language, it is easier when you have someone, not only to speak to, but to remind you why you're doing this. I write far more in Chinese because I have friends I can text in Chinese.

Pen and Paper: Study after study, writing on paper continues to be the best method for memorization. Typing or using a pen and tablet still can't compare to traditional methods.

The Replies (Probably): Lots of people were happy to give alternatives for specific languages in the replies of my DL post. The community here is pretty active, so if this post blows up at least 20% of what the last one did, you might be able to find some great stuff in the replies and reblogs.

“We are not far from a world—I think we’ll be there in three to six months—where AI is writing 90 percent of the code,” Dario Amodei, CEO of Anthropic, said at a Council on Foreign Relations event in March. “And then in 12 months, we may be in a world where AI is writing essentially all of the code,” he added.

But many experts warn that even the best models have a way to go before they can reliably automate a lot of coding work. While future advancements might unleash AI that can code just as well as a human, until then relying too much on AI could result in a glut of buggy and hackable code, as well as a shortage of developers with the knowledge and skills needed to write good software.

David Autor, an economist at MIT who studies how AI affects employment, says it’s possible that software development work will be automated—similar to how transcription and translation jobs are quickly being replaced by AI. He notes, however, that advanced software engineering is much more complex and will be harder to automate than routine coding.

Autor adds that the picture may be complicated by the “elasticity” of demand for software engineering—the extent to which the market might accommodate additional engineering jobs.

“If demand for software were like demand for colonoscopies, no improvement in speed or reduction in costs would create a mad rush for the proctologist's office,” Autor says. “But if demand for software is like demand for taxi services, then we may see an Uber effect on coding: more people writing more code at lower prices, and lower wages.”

Yegge’s experience shows that perspectives are evolving. A prolific blogger as well as coder, Yegge was previously doubtful that AI would help produce much code. Today, he has been vibe-pilled, writing a book called Vibe Coding with another experienced developer, Gene Kim, that lays out the potential and the pitfalls of the approach. Yegge became convinced that AI would revolutionize software development last December, and he has led a push to develop AI coding tools at his company, Sourcegraph.

“This is how all programming will be conducted by the end of this year,” Yegge predicts. “And if you're not doing it, you're just walking in a race.”

The Vibe-Coding Divide

Today, coding message boards are full of examples of mobile apps, commercial websites, and even multiplayer games all apparently vibe-coded into being. Experienced coders, like Yegge, can give AI tools instructions and then watch AI bring complex ideas to life.

Several AI-coding startups, including Cursor and Windsurf have ridden a wave of interest in the approach. (OpenAI is widely rumored to be in talks to acquire Windsurf).

At the same time, the obvious limitations of generative AI, including the way models confabulate and become confused, has led many seasoned programmers to see AI-assisted coding—and especially gung-ho, no-hands vibe coding—as a potentially dangerous new fad.

Martin Casado, a computer scientist and general partner at Andreessen Horowitz who sits on the board of Cursor, says the idea that AI will replace human coders is overstated. “AI is great at doing dazzling things, but not good at doing specific things,” he said.

Still, Casado has been stunned by the pace of recent progress. “I had no idea it would get this good this quick,” he says. “This is the most dramatic shift in the art of computer science since assembly was supplanted by higher-level languages.”

Ken Thompson, vice president of engineering at Anaconda, a company that provides open source code for software development, says AI adoption tends to follow a generational divide, with younger developers diving in and older ones showing more caution. For all the hype, he says many developers still do not trust AI tools because their output is unpredictable, and will vary from one day to the next, even when given the same prompt. “The nondeterministic nature of AI is too risky, too dangerous,” he explains.

Both Casado and Thompson see the vibe-coding shift as less about replacement than abstraction, mimicking the way that new languages like Python build on top of lower-level languages like C, making it easier and faster to write code. New languages have typically broadened the appeal of programming and increased the number of practitioners. AI could similarly increase the number of people capable of producing working code.

Bad Vibes

Paradoxically, the vibe-coding boom suggests that a solid grasp of coding remains as important as ever. Those dabbling in the field often report running into problems, including introducing unforeseen security issues, creating features that only simulate real functionality, accidentally running up high bills using AI tools, and ending up with broken code and no idea how to fix it.

“AI [tools] will do everything for you—including fuck up,” Yegge says. “You need to watch them carefully, like toddlers.”

The fact that AI can produce results that range from remarkably impressive to shockingly problematic may explain why developers seem so divided about the technology. WIRED surveyed programmers in March to ask how they felt about AI coding, and found that the proportion who were enthusiastic about AI tools (36 percent) was mirrored by the portion who felt skeptical (38 percent).

“Undoubtedly AI will change the way code is produced,” says Daniel Jackson, a computer scientist at MIT who is currently exploring how to integrate AI into large-scale software development. “But it wouldn't surprise me if we were in for disappointment—that the hype will pass.”

Jackson cautions that AI models are fundamentally different from the compilers that turn code written in a high-level language into a lower-level language that is more efficient for machines to use, because they don’t always follow instructions. Sometimes an AI model may take an instruction and execute better than the developer—other times it might do the task much worse.

Jackson adds that vibe coding falls down when anyone is building serious software. “There are almost no applications in which ‘mostly works’ is good enough,” he says. “As soon as you care about a piece of software, you care that it works right.”

Many software projects are complex, and changes to one section of code can cause problems elsewhere in the system. Experienced programmers are good at understanding the bigger picture, Jackson says, but “large language models can't reason their way around those kinds of dependencies.”

Jackson believes that software development might evolve with more modular codebases and fewer dependencies to accommodate AI blind spots. He expects that AI may replace some developers but will also force many more to rethink their approach and focus more on project design.

Too much reliance on AI may be “a bit of an impending disaster,” Jackson adds, because “not only will we have masses of broken code, full of security vulnerabilities, but we'll have a new generation of programmers incapable of dealing with those vulnerabilities.”

Learn to Code

Even firms that have already integrated coding tools into their software development process say the technology remains far too unreliable for wider use.

Christine Yen, CEO at Honeycomb, a company that provides technology for monitoring the performance of large software systems, says that projects that are simple or formulaic, like building component libraries, are more amenable to using AI. Even so, she says the developers at her company who use AI in their work have only increased their productivity by about 50 percent.

Yen adds that for anything requiring good judgement, where performance is important, or where the resulting code touches sensitive systems or data, “AI just frankly isn't good enough yet to be additive.”

“The hard part about building software systems isn't just writing a lot of code,” she says. “Engineers are still going to be necessary, at least today, for owning that curation, judgment, guidance and direction.”

Others suggest that a shift in the workforce is coming. “We are not seeing less demand for developers,” says Liad Elidan, CEO of Milestone, a company that helps firms measure the impact of generative AI projects. “We are seeing less demand for average or low-performing developers.”

“If I'm building a product, I could have needed 50 engineers and now maybe I only need 20 or 30,” says Naveen Rao, VP of AI at Databricks, a company that helps large businesses build their own AI systems. “That is absolutely real.”

Rao says, however, that learning to code should remain a valuable skill for some time. “It’s like saying ‘Don't teach your kid to learn math,’” he says. Understanding how to get the most out of computers is likely to remain extremely valuable, he adds.

A: Sometimes, it's okay not to have a plan. You've probably seen this before, but writing is a nonlinear process where you write things that don't necessarily happen next in your story but you feel a strong urge to write them. Art doesn't need to have a concrete plan, you can let yourself free with how you write it. I get my best ideas for scenes at 3am.

But regardless, my answer to this would be that I make a checklist of "scenes" for myself. You have to address all characters' conflicts and keep track of them, and I can't do that easily unless I make a concrete plan for every scene. I also really like checklists, because I probably have undiagnosed ADHD and can't function without that dopamine hit. Same reason why I never like having a lot of asks unanswered in my inbox, so all the pending requests are kinda driving me crazy right now LOL.

If it helps, write out each character's "plotline" and how they're going to grow, then think of scenes that make that growth tangible to the reader. I have a LOT of trouble with this in bridgerton!gojo, which is the most plot filled. gojo is a complex character, so i have to keep reminding myself of his issues right now. for example, gojo currently is someone who has a lot of responsibility on him, and he has been conditioned to think that he can't love to stay on the grind. reader infuriates him because she's the first one who's really posed a challenge for him. he's going to realize that he enjoys spending time with reader BECAUSE of that challenge and how it simulates him, which simulataneously making him panic because he forgets who he is and the vow to himself to never engage with a woman/prospective match that could lead to animosity at home. since he doesn't want to have unecessary fights or feelings that could distract him from his duty.

however, he's actively fighting the happiness/weird feeling in his heart whenever he sees reader, especially if he sees her with another man (after this whole gojo manor arc). he's going to be extremely irrational and threatening any man who chooses to actively court her, and this makes him realize that he does deserve love, that there can be space for love while prioritizing your responsibilities.

now, im just going to make this into scenes, writing something similar for reader and any other character that may need to show character growth. and boom! series planned.

Q: Do you use a program or anything?

A: I write on Google Docs because it automatically saves and I can write from my phone or laptop, whichever one I have on hand. Particularly useful when I get an idea at 3AM. It's also useful to share with beta readers. I wouldn't say I use anything else, but I know notion is sometimes helpful. There exist resrouces for (professional) romance writers, so I would check those out since they're also applicable!

Some other things:

If English is your second language/not your native language, or you get stuck on how to write things, read. Read fanfics on ao3, read real books, read the newspaper, read political critique, read essays, watch video essays. I learned English using Harry Potter (and having to wake up at 5am to go to school early to do Rosetta Stone in elementary school). Develop your own writing style. Ever get stuck on scene? Read how someone else did it/how they wrote. Doesn't even have to be a similar scene