News for hackers. Stuff that matters.

rjdavis3

Re:Ask HN: Who is hiring? (September 2019) on Thursday September 05, 2019 @09:32AM (#20886463)
ChannelApe | Scranton, PA or REMOTE

We are looking for experienced Java developers with great organization skills. Our company is huge on automated testing so any experience there is a plus. If anyone is interested please apply here: https://www.channelape.com/jobs/application-developer-java/

Ask HN: Any good products to allow users to build dashboards within an app?

My company has an Angular 1.3 front-end app (looking to re-write or upgrade soon) that interacts with our REST API. After logging in users can perform various tasks and see some simple dashboards we created for them around usage. Right now the dashboards are the same for every user but we have had numerous requests for customization. We would love a tool (paid or otherwise) that our users can...

( Read More... | 1 comment | on HN )
Re:How a Blind Developer uses Visual Studio [video] on Tuesday May 16, 2017 @09:14AM (#14349261)
This is great. I always wondered how blind developers managed to navigate IDEs at a decent pace.

I can't help but wonder how Saqib Shaikh navigates through log files for large applications though. Log files usually generate a large amount of noise in the form of time stamps, thread names, log levels, stack traces, etc. that overtime I've learned to "scan" instead of read to find what I am looking for. I would love to see a video of him navigating through a log file to see how he does it. Maybe just lots of string searches?

Re:The tragedy of 100% code coverage (2016) on Tuesday May 09, 2017 @09:54AM (#14299991)
Have you ever tried it with one of the automated tools? I use Pitest extensively to mutate my Java code bases and found it is not too much slower then regular line and branch code coverage tools when you use a history file so only diffs are needed. The trade off of a few more seconds of build time is worth the benefit of the coverage report and being able to fail the build if coverage drops too low for me.

http://pitest.org/quickstart/maven/

Re:The tragedy of 100% code coverage (2016) on Tuesday May 09, 2017 @09:45AM (#14299903)
I use pitest to run mutation coverage on most of my Java code bases. pitest implements a timeout to check for infinite loops introduced by changing the code.

http://pitest.org/faq/

Re:DynamoDB cannot store empty strings on Wednesday December 14, 2016 @07:23AM (#13175446)
I would love for them to fix storage of empty string but I don't think that is going to happen given all the documentation they have around not allowing it. Must have been easier for them to just document the limitation.

I do agree that they could do a better job in their documentation explaining the difference between JSON spec and their JSON equivalent that they store. It is not clear that the JSON you post is not stored in the same exact way. They could be more clear about the types they append to your data (L, S, SS, N) and then reference the link I put above about the restrictions for each type.

Re:DynamoDB cannot store empty strings on Wednesday December 14, 2016 @07:15AM (#13175412)
Sorry I saw the link was referencing the Java SDK so I thought you were using the same. The DynamoDBMapper Java SDK has been an easy to use and readable ORM for me. Adding annotations to define keys and attributes has been great. That said I'm not sure if JavaScript has an equivalent to the AttributeTransformer I mentioned.
Re:DynamoDB cannot store empty strings on Tuesday December 13, 2016 @04:31PM (#13171258)
I agree they should fix it but I think they have been transparent about the restriction. It is already listed within most of their documentation.

http://docs.aws.amazon.com/amazondynamodb/latest/APIReferenc...

It is also listed as a Gotcha on the AWS Open Guide which trended on HN a few weeks ago.

https://github.com/open-guides/og-aws#dynamodb

Re:DynamoDB cannot store empty strings on Tuesday December 13, 2016 @04:22PM (#13171165)
While not ideal, you can create a new AttributeTransform that sets a place holder when storing into DynamoDB and removes it when pulling out of DynamoDB as part of your DynamoDBMapper instantiation.

I did this to convert some String Sets (SS) in my database to String Lists (L). I almost did this same thing to fix the empty String issue but didn't have the time to implement it yet.

http://docs.aws.amazon.com/AWSJavaSDK/latest/javadoc/com/ama...

Re:DynamoDB cannot store empty strings on Tuesday December 13, 2016 @04:03PM (#13170993)
What is the point of this trending? To try and get AWS to fix it? I must admit this was a gotcha for me at first but it is documented right on their standard Limits page. I'm guessing the fix is non-trivial or they probably would have just done it.

http://docs.aws.amazon.com/amazondynamodb/latest/developergu...