HN user

zeeshanejaz

1 karma
Posts5
Comments7
View on HN

Github does a poor job of presenting your work to viewers, so why do developers insist on including it in their resumes. I believe its because developers take pride in their craft and to be introduced by their work.

Yet developers' best work is hidden inside private repos: the side project that might have commercial potential, that company work that can't be open source, clients and consultancy work that's covered under NDA. If you are hiring developers based on their github profile, you are optimizing for the wrong profile.

That's why I made https://gitfolio.dev - mostly to scratch my own itch: present my best work better than github does, provide evidence for what I am good at, and keep updating it on an autopilot.

If you are a developer, you can give it a try for your own portfolio at https://gitfolio.dev - you can use it even without giving it access to your code.

This logic didn't make much sense to me. If banana-mobile company treated me badly and didn't replace my water-damaged mobile, I wouldn't throw away its shares because I am disgruntled. How a company treats me as a customer, or an employee, has nothing to do with how I see it as an investment.

Dear all, I am a part of a research group at the University Of Auckland. Our bigger vision is to create a set of tools for safety critical application of DNNs. This includes a formal approach for composition of multiple NNs, static timing analysis, and correct by construction approaches for SW/HW co-design.

Our first project is now live at https://www.aitransformer.com/ which is basically an enhanced Keras2C utility. Unlike the alternatives, the generated code doesn't depend on anything like TensorFlow C Library. This makes the code amenable to static timing analysis and perhaps more light-weight. If you use C code for AI application, or use AI in embedded systems and edge compute, we would love to hear from you. Leave comments. Thanks!

We migrated from TeamCity and OctopusDeploy a couple of months ago and we are already regretting it. The reliability of this system is just horrendous. The documentation is pretty much outdated, and quite a few plugins do not work. I have to write a bunch of powershell script to get it to work the way I want. And today, all hell broke loose.

Since this morning, we are stuck with an error message "TF400893: Unable to contact the server. This is most likely caused by a network error. Please check your connection and try again.". This has cause a couple of release pipelines to be get stuck, with cancel option not working either. The paid "parallel jobs" are being consume in this stuck pipeline and no other project from my organisation can be built or deployed because of it.

Pretty much regretting having spent so much time configuring the pipelines. We might switch it doesn't get resolved soon or if it happens even one more time.

SDKS.IO crawls the web, not for existing SDKs, but for API descriptions, and generates SDKs automatically. So if an API does not have any SDKs, but has its description in Swagger/API Blueprint/RAML etc posted on Github, the SDKs will be automatically generated for it. If you google for these SDKs, you won't find them :)