Is there a site that allows me to see how my resume will be parsed by an ATS? I see resumeworded.com and while it's slightly helpful, a bit more of an understanding of how it's ingested and parsed would be helpful.
Here's my code and the error message that comes up in check50:
#include <cs50.h>
#include <stdio.h>
#include <ctype.h>
#include <string.h>
#include <math.h>
int count_letters();
int count_words();
int count_sentences();
int main(void)
{
string word = get_string("Text: ");
int letters = count_letters(word);
int word_count = count_words(word);
int sentences = count_sentences(word);
float L = ((float)letters * 100) / word_count;
float S = ((float)sentences * 100) / word_count;
float index_raw = (0.0588 * (float)L - 0.296 * (float)S - 15.8);
int index = round(index_raw);
if (index < 1)
{
printf("Before Grade 1\n");
}
if (index >= 1 && index <= 16)
{
printf("Grade %i\n", index);
}
if (index > 16)
{
printf("Grade 16+\n");
}
}
int count_letters(string word)
{
int letters = 0;
for (int i = 0, n = strlen(word); i < n; i++)
{
if (isalpha(word[i]))
{
letters ++;
}
}
return letters;
}
int count_words(string word)
{
int word_count = 1;
for (int i = 0, n = strlen(word); i < n; i++)
{
if (isspace(word[i]) && isalpha(word[i+1]))
{
word_count ++;
}
}
return word_count;
}
int count_sentences(string word)
{
int sentences = 0;
for (int i = 0, n = strlen(word); i < n; i++)
{
if ((word[i]) == '.'|| (word[i]) == '!'|| (word[i]) == '?')
{
sentences ++;
}
}
return sentences;
}
Naming things is hard. And naming tests is no exception. But XCTest adds another layer of complexity: test names have to be functions.
The framework creates a test for every function that starts with “test” in your XCTestCase subclass. Examples from Apple’s docs include:
class NetworkReachabilityTests: XCTestCase {
func testUnreachableURLAccessThrowsAnError()
func testUserJSONFeedParsing()
}
I find these a bit hard to understand. Humans weren’t meant to read camel case, that’s why we have spaces! I would much rather write tests like Kotlin, as a string.
class MyTestCase {
@Test fun `number of cells with no data is zero`()
}
Turns out, we can get something very close to this Swift, but there are a few tradeoffs. Add the following extension to your test suite.
extension XCTestCase {
func test<T>(_ description: String, block: () throws -> T) rethrows -> T {
try XCTContext.runActivity(named: description, block: { _ in try block() })
}
}
We are taking advantage of XCTActivity to wrap everything in “test” with some syntactic sugar. Now we can write tests like this!
class TestCase: XCTestCase {
func test_numberOfCells() throws {
test("is zero when there is no data") {
/* ... */
}
test("is equal to the number of items") {
/* ... */
}
}
}
I really like how this reads. It’s obvious what’s going on and each assertion gets its own space to breath. However, there are a few downsides to this approach.
How do you test?
Looking ahead, I’d love to create a micro-library that can generate tests on the fly. Think Quick, but without any of the nesting or BDD stuff.
What do you use to test your Swift code? Do you use any third-party libraries? I’d love to know! Mention or DM me on Twitter to get in touch.
I also blog about Swift and testing on Masilotti.com.
If you're trying to test the text color contrasts against a UI interface, do check out https://designs.ai/colors/text
The higher the WCAG score, the more legible it is.
https://preview.redd.it/27bz7azdpla51.png?width=1346&format=png&auto=webp&s=6d3b94ebe844436f5886b19179cdf985b2e69257
Hello r/computerscience
I'm a PhD student at the Washington State University and I'm a part of a research lab here that investigates the comprehension of source code in order to further our understanding, and to develop better tools and processes to support software developers. Here are some examples of work we have done in the past:
A Model to Detect Readability Improvements in Incremental Changes (2020)
Improving source code readability: theory and practice (2019)
We need your help with something we are working on currently and we think you would find this interesting if you don't particularly love writing unit tests :). Although its not a well known fact, there are several tools that can write unit tests for you, and while they are far from replacing manually written tests, they are making rapid progress in their effectiveness. However, one thing holding them back is their readability; they tend to use bad variable/method test names and have no documentation and it can get really painful to maintain them.
We are working on developing an approach to address this issue, and we want to know what you think! It is really important for us to get your opinion on this, as we want you to some day use our approach as an IDE Plugin. We understand that automatic test generation tools are far from perfect in other aspects, but we beleive that in the next 5-10 years, they will become good enough so that you don't have to write any obvious unit tests for your projects. When this happens, I beleive our tool could help you be more productive with your work.
We have created two surveys to collect your opinion. Each survey takes < 15 minutes to complete.
I will be available here to answer any questions you have. Thanks!
By cleaning up composition I mean things like writing some comments to explain my code, changing variable names...etc
I'm really torn between going with a less traditionally designed CV and a traditional one. I keep seeing ATS readability mentioned and I'm having trouble finding genuinely free ones. Perhaps there aren't any, but I don't feel as though the 'try once' options aren't very reliable since it's usually their goal to have you choose their CV consultation.
Thanks all!
I'm working for a big company that is evaluating possibilities to get fully in VR. Among different tests, we have been evaluating extreme readability with Varjo headset.
I can tell you that it is dame good and, if you have a good vision (or correction glasses), you would be able to properly read a less than half centimeter height text at more than 3 meter away.
Amazing tech, thumbs up to Varjo's team!
Question:
- What is the current best setting to get maximum text readability in E:D with a Vive? I got mine yesterday and did a bit of flying around and...my word the text is atrociously hard to read in most places.
- Also, is there a way to make it so the side menus don't constantly open and close if I turn my head ever so slightly while looking at them (or maybe I just don't feel like turning my head so far to trigger them?).
- What settings should I look at to make the galaxy map more useful? I don't want to have to rely on switching to keyboard and mouse every time I want to punch in a destination. I know I'll have to use the keyboard to type the system name, but I can't seem to navigate up and down on the systems pane in the galaxy map. Where are the keybinds for that?
Testing offer: I have one of those shiny new GTX 1080s, so I can try all kinds of crazy shit most cards can't handle to see if it helps. The things I don't know are how to provide useful data, IE:
- How do I take a screenshot of what my VR headset sees?
- What settings should I change and how (INI editing, in game, etc?)
- ??? something else I wouldn't know?
I find bugs in software / hardware setups for a living, so the process I'm extremely familiar with. The catch is normally I am looking at white boxes, not black ones. I'm...not as strong when it comes to black boxes I don't know much about.
I experimented with Moving Text every frame just a little in random direction [to mimic eye shake].
The test was two boxes with text on them one box was normal the other I moved the texture every frame so 75 times a second.
The results were not very conclusive but still worth noting.
At 1m distance the text on the two boxes looked the same and both were easily readable.
At 2m distance the text on the two boxes looked the same and both were readable.
At 3m distance the text on the two boxes had differences and both were readable but the moving one was easier to read.
At 4m distance the text on the two boxes had differences and both were unreadable but the moving one seems to have less space between letters.
At 5m distance the text on the two boxes had differences and both were completely unreadable.
I feel that it did have a positive effect when the text was readable but did not seem to increase the distance at which it was readable? Which I do not understand.
I will do further testing with TEXT with more space between letters has this does seem to effect the moving text.
Also has anyone had any success with different FONTS? if so which font gets the greatest Distance?
Not for any actual reason, just wonder if a bot is even smart enough.
http://adf.ly/q5tJb
Must pass Java qualification test (3 out of 4). Took me 5 minutes for the qual test and 5 for the actual one, but I was going slow.
Hey folks, I recently bought my first ever Apple computer (Macbook Pro 2015 model) and have been getting used to it as I've been using mostly Windows all of my life. I decided not to go with a Windows laptop because all of the ones I've used in the past have been really garbage. So far I'm enjoying the Macbook pro, getting used to shortcuts for my work flow, etc etc.
Anyway, my main question: Does anyone know of an app that tests the readability of an audio CD? Just to give you an idea of what I'm looking for, on Windows, I use VSO Inspector. I sell a lot of used audio CDs and rather then listening to each song to verify that it plays correctly, this application will let me know of any playback errors.
Any help is appreciated!
Hello, Technical Writing!
I've just been hired on as a technical writer for a federal contractor, and our current contract has us rewriting a pretty hefty policy document. I've worked as a technical writer before, but never in this kind of official capacity so there are a whole lot more rules, regulations and procedures that I'm getting used to.
My question for you guys is if any of you have any experience using the Flesch-Kincaid readability tests, and if so, how accurate do you find them to be?
I ask because I was recently shown how to use it by one of our client's SMEs, and while I find it very helpful in getting an overall idea on the stats of our document, I'm finding myself a little too focused on the stats and not focused enough on how an actual user may read the document.
To give an example, there are many situations like this;
- You will qualify for such and such if:
- a. You meet this requirement;
- b. You meet this requirement; and
- c. You meet this requirement;
When I run the section I'm working on through the F-K tests, I feel like paragraphs like these really run up the average length of our sentences. I tried to fix this by putting periods at the end of every lettered section, but that creates fragments which I also think negatively effect the scores.
We're basically rewriting an old policy document, and when I ran their old published sections through the F-K tests, their readability grade level was 16.9. After some fancy wordsmithing, I've gotten it down to 13.0, but seeing as how our client would ideally like a 6th grade reading level, that number is not excellent.
Does anyone know how heavily lists like these effect the test scores? Thanks!
