HN user
I created PoC for merging similar system requirements and performing gap analysis between vendor documentation and internal company SOPs and policies.
Everything in Python flask + Azure OpenAI. I am working on moving AI part to Claude Sonet. Seems that results are bit different since GPT model has more rough approach to merging requirements and also less sensitive to finding gaps.
thanks indeed. Didn't know about algolia. I usualy googled topics with site:news.ycombinator.com
Definitely will check it.
- no open space,
- no domestic country manager,
- no BS meetings,
- no BS about overtimes,
- contract + good pay,
- home-office,
Do you know TICK stack - Inflix DB?
Splunk
From my experience, these resources are worth read:
[1] Pattern Recognition and Machine Learning (Information Science and Statistics) by Christopher M. Bishop
Andreas Brandmaier's permutation distribution clustering is a method rooted in the dissimilarities between time series, formalized as the divergence between their permutation distributions. Personally, I think this is your "best" option http://cran.r-project.org/web/packages/pdc/index.html
Eamonn Keogh's SAX (Symbolic Aggregate Approximation) and iSAX routines develop "shape clustering" for time series
http://www.cs.ucr.edu/~eamonn/SAX.htm
There are approaches based on text compression algorithms that remove the redundancy in a sequence of characters (or numbers), creating a kind of distance or density metric that can be used as inputs to clustering, see, e.g.:
http://link.springer.com/chapter/10.1007/978-0-387-84816-7_4
This paper by Rob Hyndman Dimension Reduction for Clustering Time Series Using Global Characteristics, discusses compressing a time series down to a small set of global moments or metrics and clustering on those:
http://www.robjhyndman.com/papers/wang2.pdf
Chapter 15 in Aggarwal and Reddy's excellent book, Data Clustering, is devoted to a wide range (a laundry list, really) of time-series clustering methods (pps 357-380). The discussion provides excellent background to many of the issues specific to clustering a time series"
http://users.eecs.northwestern.edu/~goce/SomePubs/Similarity...
...and a lot more.
-- URL --
[1] https://www.amazon.com/Pattern-Recognition-Learning-Informat...
I have membership in IEEE and Computer Society just for SkillPort access (e-learning+books). Otherwise don't get any other benefits from it.
seconded....spreadsheets are almost everywhere. Even small tweaks can be scripted.
As was already mentioned. Trustness is the key. You need to be a trusted partner for such sensitive type of work.
Wrong people with root access to core infrastructure can make much more damage and cost more than problem which isn't solved at all.
There is also no space for learning on-the-fly. You have to know what you are doing, and how to perform certain steps correctly (t-shoot, recovery, migration).
From my experience, almost all my contracts (> 90%) came from word-of-mouth. Almost all online and printed advertisements, online profiles were waste of my time and resources.
Also, if friend of mine recommend me to someone else, I can believe that I will get paid (or there is only low risk). In case of blind-contract via internet, there is still a bigger risk that you will not get paid. I am not sure if I can (and want) trust published ratings on such web-pages.
"find a way to use it to distribute porn."
this made my day :)
i think if content can be verified via blockchain that doesn't contains any malware it would be much more preferred.
Location: Slovakia
Remote: YES
Willing to relocate: no, but travelling possible
Technologies: powershell, python, php, html5, bit of java, network (routing, switching, ccnp, ccda), security (fw, proxy, AAA, ccna-sec), IoT, Arduino, Technical writing, PMI, DMAIC
Résumé/CV: ON-demand
Email: in my HN profile
I have 10 years of experience from various ICT areas like network (5 years) and security (6 years), various project size, quality assurance, sw development, currently cooperate with local startups and their new IoT products. Looking for: technical problems to solve, product development, prototype development, optimization,innovation,software automation, proof-of-concept.
I am open for more detailed discussion about my past projects.
Seconded. We have used Kong API and it works flawlessly for our basic needs. Time from research till first prototype was in hours.
"Banks seems to have many layers of checking for potentially suspicious activity,..."
I don’t think so. I had this kind of incident and nobody from bank noticed it (60 euro paid over night 3:35 AM from central europe to fake company somwhere in tax paradise, summer 2014). If i asked why and how it was possible, they replied with formal letter how much sorry they are. Nothing more.
I was in touch with ViSA guys and they confirmed payment as fraud and returned my money back to me.
Around 10 years ago i was in national bank. We had small project for entrance gateway automation. Control unit was strange DIY solution.
Banks aren’t so secure as we think. At least in my country.
I worked for big oil company and even their infrastructure and solutions are far from ideal. So i don’t have false expectations about security.
Currently, i am in preparing process for my 4th book and i am thinking how to get more money in advance.
Has anyone experience with corporate sponsorship?
Yes, great for brainstroming and issue discussion but not for deep individual thinking.
As Oren Klaff said...you can't steal it, you can't find it, you can't buy it...you have to earn it.[0]
Courses and books give you tool. For sharpening, you have to use it daily.
Good resources about "tools":
I'd Rather Die! Public Speaking Survival Skills by Robert Scanlon.[1]
MIT OWC - Rethoric [2]
Oren Klaff - How To Pitch Anything (LondonReal) [0]
(not exactly about speaking but suitable for speak preparation) Technical communication by Mike Markel [3]
[0] https://www.youtube.com/watch?v=WxwTn_f5yaI
Edit: Formatting
Recently, i saw interesting speech about eating habits, by Michael Pollan: https://www.youtube.com/watch?v=c31cAdYUvT8
I observed that after 2 glasses of wine I'm more resistant to all kind of distractions. I don't have tendency to open dozens of tabs in browser, switch among unsolved things, check mails, smartphone etc.
Disadvantages are that I'm tired sooner and it's not sustainable drink alcohol if I need to do something.
All-in-all, no practical solution....just interesting self-observation :)
Very interesting reading about this topic is in book Pragmatis by William James.
Its philosphy so its not easy reading for relax.
From critical thinking point of view, try to read something about rhetoric. If you know some approaches, try to get in practice and challenge some speakers.
Start with your friends and familly. But I have to warn you...you will not be favorite partner for discussions anymore :-) so don't overdo.
Why you need a list? What if you don't need majority of tools?
Install just tools you need for work. No more, no less. If you don't know about related tools, you probably don't need them at all.
Government information about legislation in preparation process
All proprietary know how, guidelines howto, real world experiences with solutions, approaches, process...what doesnt work at all and what is working fine and why.
Seconded. In my last job i automated all tedious tasks via powershell. Need to verify connectivity and documentation accuracy (credentials, snmp strings, vendors, versions...)? Powershell is solution for me.
Even tcl scripts was parsed, compared and exported to xls with Powershell. Verify and implement configuratiom template was another case where powershell was solution.
For me this is my strongest weapon on windows automation and system management.
And i like it beacuse you can edit in notepad++, sublime, atom, whatever...save... a run ps1 file. No insane and complex IDE needed, no compilers. If you need you can do exe files. It's dirty solution, but it works.
My last project (app for coffe shopps and restaurants) is written in powershell.
"The biggest issue" for me is support of my scripts on windows with lower version of powershell or .NET
In regards to original question. "Powershell in action" is my favorite resource about powershell.
From my experience .... for example daily writing improved my thinking and articulating ideas and thoughts.
Also design and making hardware staff with wood and steel improved my imagination and thinking about how things works.
You don't see overnight success...but if you compare your outcome from three of eight years ago you will see amazing difference in quality.
How long it take? It depends on area. Something can be mastered within hours, something within years. Do you know 10,000 hour rule? It is exactly what you are looking for.
So, answer is yes...practice makes perfect.
I prefer videos with transcript. Not all videos or parts are interesting or valuable for me.
As was already mentioned, shorter videos are better. It can keep up your engagement. One bad example is Microsoft virtual academy. I wasn't able watch neither one full video. Udacity of tedx or coursera are good examples.
Also if its very interesting topic i am taking some notes. Pencil and paper should improve memorize process (don't have citation right now, writing from mobile) but my font is terrible and slow (if it has to be readable) Electronic notes are much better for me, i can search, format, paste screens and diagrams, even from screenshots video.
If i am watching tutorials, am doing all steps in parallel. Very often with google at next screen due to different version , syntax, whatever.
After all i am taking notes with step-by-step procedure what and how i did it. Sometimes also with description why.I prefer videos with transcript. Not all videos or parts are interesting or valuable for me.
As was already mentioned, shorter videos are better. It can keep up your engagement. Ona bad example is Microsoft virtual academy. I wasn't able watch neither one full video.
But everyone have to find own way what is best way for him.
Would be interesting to see how many people/other services are now lost without Google.
Bratislava and Kosice from Slovakia are not working also.
My desk looks very similar ...osciloscope, power supply and bills :) ... i also have dozens sticky notes lying around.
I already consider these solutions but they are good for devs. I am looking for something for non-devs. But thanks for tip.
From my experience, requirements don't come from bottom but it should. Initiator is almost always manager who might have some idea or vision but it's not right originator. And this is the main issue. He is trying to remove outward manifestation not root cause. Employees are always struggling with deeper issues than manager is trying to solve.
Practical example: I am working with huge amount of data about customer's network infrastructure. Every item (device/contract/ticket) has own web page. There is huge items with wrong or dummy data. If I need report, verify and amend certain data i can't do it via bulk requests or automatically. Our application doesn't have such interface, we don't have API, we don't have CLI. I did talk to architect and he said me...no, we don't have it, and you are the first one who asked for it. Nobody need it. So sorry but no.
Another example: internal tool, have some features but are wrongly implemented. I reported that it doesn't work as expected. I received reply that nobody use it, so there is no chance to get resource for fix and improvement.
And another one...manager bring idea with time saving and required new internal tool which will do automatically sign-in to all day-to-day tools. It saved almost 5 minutes. But after password change it very often locked users account. In total it wasted few hours of raising incident with internal IT.
And I have lot of similar experiences. So from my point of view here are key features for corporate internal tools:
1) If tool or function doesn't work - hide it or remove it
2) If documentation is available - do it properly. Have some documents with terminology explanation. Explain purpose and dependency between fields. Also explain what is mandatory and why. This is whole story how can proper documentation save your time and money. Everybody need to understand what they use and why they have to fill field A, B, C and optionally D. You can save a lot of time, money and issues, especially with newcomers. This documentation can be studied at any time during future work. You can avoid misinterpretation from older colleague etc.
3) If tools are developed always talk to end user not only with manager. Ask 5 times why should we solve this? Isn't the real issue somewhere else?
4) Internal tools always needs to be supported from management. Otherwise is very small chance that your effort will be appreciated.
5) If you create tool have CLI version. GIU is some kind of protection against stupidity but it also restrict improvement and speedup of whole process.
6) If you work with data, use standardized format like csv, xml or json. Same format needs to be used for import and export. If other internal tools use csv don't use xml or json and vice-versa.
7) Other internal tools have to be able work with same format. Export from tool A have to be applicable (or with small amendment, no more than several clicks/removal and copy-paste actions) into tool B. So your format what is standardized for other tools.
8) Don't use insane level of nested features and choices. Something like Audit-> Results -> Failed/Succeeded -> Details/Settings/Re-run -> (Details) Result/Rule/Config/History -> (Result part) Output: " Filed X, Y, Z wasn't find in config" ... and you are thinking wtf? Why? And you have to open different window and verify it manually. I need to know what was found and why it didn't match. Very often is due to wrong regexp pattern, but it take almost 30 minutes to verify all possible paths and find root cause.
9) Use universally applicable language/environment. From my experience you create something which works at computer/server A but it will fail on computer/server B.
And there are tons of other issues I dont remember. Some of them are technical (software/system/hardware) some of them are social - people/management. I would say social issues is much harder to overcome than technical. Social issues are also more important, because if it fail to solve, entire project/tool can be damaged. Technical issues can be solved almost every time. If solution A doesn't work we can create B, but we always solve it.