Writing Clearly Answer Key

[Hermalindo Lepicier]

Thereare many good guides to clear philosophical writing available online. Probably the best is Jim Pryor's, and you should also take a look at his guide to reading philosophy, as the processes of learning to think, read, and write clearly about philosophy are intimately related. There's a very long, but interesting guide to philosophical writing from Cambridge, particularly noteworthy for its analysis of sample topics and essays. And Joshua May has a quick guide that covers the major points, which might be a good thing to read first. As for whether claiming not to understand someone is a fallacy: philosophers tend to find talk of logical fallacies uninformative, since there is much more to the goodness/badness of an argument than its logical validity. If readers often have trouble understanding your prose, chances are they have correctly identified an area (clear writing) in which you should improve. On very rare occasions, philosophers use the accusation that a certain author (say, Wittgenstein or Derrida) is incomprehensible as a reason to dismiss their work, but the vast majority of philosophers genuinely mean what they say when they report being unable to understand a given sentence, paragraph, or paper.

As was posted in the comment section, there are guides to writing good essays. Most advice you will read IME can be summarised as: keep trying to say it. i.e. don't expect the reader to get it without a concerted effort to structure, write and summarise it as clearly as possible.

One example from my study: I was writing an essay on a poet, who treats the landscape as something that depends on her; toward the end of the essay I noted that she doesn't imagine the landscape is created by her.

It is rather the same thing happening with the English Language; it becomes ugly and inaccurate because our thoughts are foolish; but the slovenliness of our language makes it easier to have foolish thoughts.

This mixture of vagueness and sheer incompetence is the most marked characteristic of modern English prose; and especially of political writing. As soon as certain topics are raised the concrete melts into the abstract, and no-one seems to be able to think of turns of phrase that are not hackneyed:

Most projects I work on are very 'by the seat of your pants' with very poor organization and planning. Projects are always teetering on the verge of failure and it's a pretty stressful place to work- the problem is I don't know for a fact that places I'm applying are. I can do lots of research until I feel confident that the place I'm applying isn't going to have these problems but in the end I'm not sure it sounds appropriate- if someone asks, "why are you applying here" to say "from what I've read it sounds like projects are really organized at your company and that's something I'm looking for", since it is merely speculation.

Similarly but more subjectively, I enjoy working with people who care about the quality of their code, people who like to use SOLID when writing their code, people who unit test- in general, people who think about how they can improve their skills, what techniques or methodologies would be appropriate, improving re-usability, maintainability, and readability, and stuff like that. At my current company most people just write code "line-by-line" and don't think about things on this level- repeating the same mistakes over and over and in general being frustrating to work with (or for, in the case of the leads who are the same way). The problem I've found with this is that it is extremely hard to express in an interview especially with but not limited to non-technical people in a way that is clear and not really presumptuous sounding. And again, it is merely speculation that people at that company are any different.

Couldn't you specify that you want a company with a more mature development methodology and that you're curious to see how mature is the development process at this company? That does answer the question in the sense of stating what technical components you want to know and if the person is technical they may answer that they use "Agile" and have done so for X years that you could follow-up afterward if you want something more specific.

The key is to acknowledge that your current employer isn't a great fit because you'd prefer a more mature process with better structure and want to find that in another place. The key is to ask the company, "What do you use for unit tests?" or "How do you apply the SOLID principles here?" for the technical staff if that is a litmus test for you. The key is to be able to state what the bar is for where you want to be and note that your current employer doesn't meet this requirement despite various efforts that haven't worked and thus you want to work in a different environment that you believe better suits your talents and preferences.

Unless there's a very good reason to mention it in your cover letter, I wouldn't bring up your reasons for leaving your current employer. A very good reason would be that you've been there for less than a year. Your cover letter should focus solely on how you are a great fit for the role for which you're applying.

During an interview, as a software engineer, "I'm interested in a new challenge" is usually a perfectly-acceptable answer to the question of why you're looking for a new role. If you're asked to expand on it, focus your answer on your skills and what you want to learn. For example, if your current company doesn't follow an agile methodology, you could say that you've been reading about agile methodologies and are interested in gaining expertise in such a thing. (And if your current company does follow an agile methodology, you could say that you've experienced that and now want to see how it compares to other methods.)

When asked "why are you applying to this role", then you focus on what you think that particular role will do for your career. You can discuss career growth, or you can discuss wanting to learn more about a technology or language or domain, or you can discuss your interest in growing your technical leadership skills. Tell them what it is about their role that made you interested in it, not how you think that their role differs from what you're currently experiencing.

You do want to learn about a potential new employer in your interview, though. The interview is a two-way street: not only does the hiring team want to see if you're a good fit for their needs, you are there to evaluate whether this might be a position that you want. Now that you've experienced some things that you find undesireable, you can formulate questions to ask your interviewers about their position. For example, you can ask how they manage their codebase and ensure that it's scalable, reliable, etc. You can also ask them what their development lifecycle looks like. You can ask about the mechanisms that they make available to their employees to grow their skills, such as mentorship, training, attendance of conferences, and so on.

In general, your demeanor should be unfailingly positive. You should be positive about your current role, as well as how you would be a great fit for the role that you're interviewing for. Your questions about the role you're interviewing for should also be phrased such that you're not saying anything negative about your current employer. Complaining about your current employer rarely reflects positively on you. Practice your answers (yes: say them out loud) so that your answers flow easily and sound natural.

One person may see a really nice landing page, and then go into a 'parametric search' for embedded controller chips and discover the data is accurate but the presentation isn't working on your browser. Is this major or minor?

I had a hard time writing this week's article. I was distracted by the events in the Ukraine. It's challenging to reflect on work challenges, when people elsewhere have more direct and serious issues in their lives.

Don't just start answering! They don't want to know about a time you disagreed with a co-worker. Seriously. So many people get lost in answering interview questions that they forget to figure out the point of the question.

Can you clearly explain your opinion, and the other person's opinion? Do you understand both sides of an argument? You can't be a valuable participant in a complex debate if you don't understand both sides.

3. "We had to make a decision. While I felt that Y would turn out better, it was important to move forward, so I suggested we could proceed with X, and measure the results. They agreed, and we began the rollout."

1. "As the discussion got heated, I wanted to ensure we maintained a good relationship, so I offered that we continue the discussion over lunch together. Sometimes I find that getting out of a conference room helps calm a situation."

3. "After X ended up failing, we pivoted to Y. While it was my original proposal, there was no way to know that I was right at the beginning. We had valid reasons to believe that X could work. I think making the group decision was the right one."

3. \\\"We had to make a decision. While I felt that Y would turn out better, it was important to move forward, so I suggested we could proceed with X, and measure the results. They agreed, and we began the rollout.\\\"

1. \\\"As the discussion got heated, I wanted to ensure we maintained a good relationship, so I offered that we continue the discussion over lunch together. Sometimes I find that getting out of a conference room helps calm a situation.\\\"

3a8082e126