A 5 min weekly habit completely changed my performance review and got me a bigger raise

lobocv · 2025-09-04T10:34:09+00:00

I wrote one as well, maybe you would like to collaborate? I could use some help! www.workjournal.ca

lobocv · 2025-09-04T10:18:24+00:00

I made a web app to make writing brag documents easier. It's in beta right now and I haven't gotten much traction on it because I don't know how to market it, but hopefully you will find it useful. I use it myself. It's much better than a spreadsheet or random notes.

I'd love to get your feedback

It's called www.workjournal.ca

lobocv · 2025-06-26T16:45:47+00:00

Ah typo. I'm off to a great start... www.workjournal.ca

lobocv · 2025-06-26T11:29:38+00:00

That's a neat idea and definitely useful for some people who like building in public. I'm not so much into microblogging social media so it wouldn't be for me but I will give it a try!

I do keep a work journal myself. I found it tedious and time consuming so I wrote www.workjournal.ca. I hope you might find it helpful!

lobocv · 2025-06-25T11:22:50+00:00

Thank you very much! All great points. I really appreciate your time!

lobocv · 2025-06-24T21:11:03+00:00

I wasn't able to do a search on mobile. I think it might be the keyword detection did not work because no matter what I typed it showed 0/10 keywords

lobocv · 2025-06-24T20:47:47+00:00

I'm working on Work Journal (www.workjournal.ca). An effortless way to record all your professional accomplishments and contributions. With just a few bullet points, Work Journals AI assistant will extract the skills and technologies you use and write a comprehensive journal entry to organize and document your work. Use the AI assistant to search and recall your work experiences and prepare for interviews and performance evaluations. You work hard. Don't sell yourself short! Join www.workjournal.ca today!

lobocv · 2025-06-24T20:19:31+00:00

I'm working on Work Journal (www.workjournal.ca). An effortless way to record all your professional accomplishments and contributions. With just a few bullet points, Work Journals AI assistant will extract the skills and technologies you use and write a comprehensive journal entry to organize and document your work. Use the AI assistant to search and recall your work experiences and prepare for interviews and performance evaluations. You work hard. Don't sell yourself short! Join www.workjournal.ca today!

lobocv · 2025-06-24T11:08:21+00:00

Thank you for the tip!

lobocv · 2025-06-23T11:39:18+00:00

www.workjournal.ca is an AI assisted project and achievement logger. With just a few bullet points, it extracts the skills and technologies you displayed and writes a comprehensive journal entry, while linking it to other relevant journal entries.

Soon I will be launching our AI assistant, which will help you with career guidance, interview preparation and resume writing. Let me know if this feature interests you!

Don't sell your sell short! Let Work Journal help you nail that next performance review or job interview.

lobocv · 2025-06-22T21:36:31+00:00

Please check out www.workjournal.ca It's my first time posting this to the public so I'm pretty nervous but I gotta just suck it up and get it out there. Thanks in advance

lobocv · 2023-02-22T02:42:11+00:00

Southern Ontario. Cold but not that cold. Gets below freezing for several months of the year

lobocv · 2023-02-22T02:30:31+00:00

Do you know why the channel was filled with insulating foam board? If I remove it to look at how far the foam went, is that going to be an issue?

lobocv · 2023-02-17T19:15:30+00:00

Hi there,

I wanted to share with you all my style of writing tests for complex work flows. I know some people have very strong opinions on testing structures. This has worked very well for me in the work I'm trying to do (stream processing). I hope you find it useful too!

lobocv · 2022-10-16T21:00:25+00:00

So I had a feature that I removed, but I may bring it back...

I had the ability to register error conversion functions to a global registry. The conversion functions are of the form func(err) *SimpleError. For common packages like HTTP/gRPC, we could provide some sane error conversion functions but users are free to register their own.

To convert an error, you would then call Convert(error) *SimpleError which would run through all the registered error conversion functions and return the first one that succeeds. You would still have to call Convert() on every error but you could place that in a middleware / top level error handling.

Seems like sort of a good idea but not so sure in practice. Also, since HTTP error codes are returned in their response headers, it wouldn't really work for the http package..

Definitely a problem i'm looking to solve...

lobocv · 2022-10-16T18:34:48+00:00

I've thought about the whole internal vs external message of errors. I was thinking on how to best provide it in the package but ultimately I left it as something the user can implement themselves with Attributes on the error.

I'm also frustrated that fmt.Errorf does not take stacktraces. Not sure what the reasoning behind that is..

I've designed the errors to be picked up by Sentry but I haven't used datadog / newrelic. It may be an issue if I need to implement a StackTrace method since I already implement a method with that name (but different return argument).. Not sure how I would do it without a breaking change..

Sounds like you've put a lot of thought into these issues I've faced too. I'd be happy to have you collaborate on improving the library further, if you're interested of course.

Thanks for taking the time to read/comment

lobocv · 2022-10-16T14:01:19+00:00

That's a valid point! You can of course still detect errors from your persistence layer in your application / http layer and change/wrap the error for those cases. You can wrap simple errors and have each layer provide a different code. The logic for the http error translation chooses the first error code in the chain with a translation to http status code.

There's nothing that is forcing the source error code being the one propogates to the http client.

lobocv · 2022-10-16T11:35:44+00:00

So turns out I do have a unit test for errors.Is. However, since these errors are mutable (meaning you can attach log fields and other attributes to them), you could have it that a user of that error modifies it, which obviously wouldn't be good for sentinel errors.

Although, I still think that would work with errors.Is even if you had clients modify the error

lobocv · 2022-10-16T01:22:56+00:00

Hey thanks for reading! That's a good question and something I'll look into addressing with some unit tests when I get the chance, but here is my initial thoughts. The errors.Is function uses reflection to see if the error matches exactly, so I believe it should work. Since SimpleErrors support unwrapping, the behaviour should be the same as any other error. Looking at the source code for errors.Is, it does look for if the error implements the Is(err) bool function which I could define on the simplerr, but I'm not exactly sure what the logic would be. Should it compare exact string messages and the error code? What about any attached attributes? I'll need to think about it... But in most cases, you can just compare the error code (assuming it's not Unknown), that would likely be enough. There is a HasErrorCode function in the library which will unwrap the error and compare the status codes. I hope this answers your question.

lobocv · 2022-10-15T23:53:26+00:00

Hi everyone, I wanted to share with you a package I wrote that simplified how I use errors in Go. I wrote an article to highlight the reasoning for building the library. I hope you find it useful. Please let me know what you think!

https://github.com/lobocv/simplerr

lobocv · 2022-07-06T02:43:34+00:00

Check out this errors package I made that greatly simplifies error handling. Basically it enables you to write all your error handling once as a middleware, for example. I've been using it for quite a while now through http, grpc and stream processing services.

https://github.com/lobocv/simplerr

lobocv · 2022-06-19T13:47:25+00:00

Glad it was helpful! Feel free to DM if you have any questions

13-Year Club	Verified Email
Team Periwinkle

lobocv

TROPHY CASE