andreineculau

9 ms·

31.
by andreineculau 5y ago
I'm all for not using Kubernetes (or any other tech) just because, but seeing their website giving 500.. I can't help but feel all the k8s' laughter. :( Google Cache doesn't work either https://webcache.google
32.
by andreineculau 5y ago
I haven't read it all but this could be great material as a git-mindset booklet for a team. Great to see someone taking the time to put down common sense notes about working with git, rather than yet another dry "this is how git w
33.
by andreineculau 5y ago
Why? Because it glorifies the pattern of copy/pasting. Your argument goes like: some biking commuters already bike too fast in crowded places, so what harm will it do to incentivise them to put an engine on their bikes so they can go e
34.
by andreineculau 5y ago
hacker news cuts the hash of the url. full url https://github.com/for-GET/jesse/pull/103#issuecomment-83225...
35.
In an alternate universe, GitHub Actions is so much simpler, safer and more fun(github.com)
12 points by andreineculau 5y ago|1 comments
36.
by andreineculau 5y ago
Unfortunately i had this idea just before i changed jobs to a "server-full" position, and now I'm on parental, so i don't have this proxy lambda implemented as a generic solution :( I only had a PoC and then told myself
37.
by andreineculau 5y ago
This 10x!!! Personally i find these setups a complete design failure. Make it work and then figure out how to develop with the constraints you will find later (not the ones you have designed yourself). So - reverse engineer and monitor in-t
38.
by andreineculau 5y ago
Not sure that i follow you, but the setup i described would proxy the env vars as well, among them the aws credentials, so you should be able to run loudly with exactly the same liberties as the original AWS lambda.
39.
by andreineculau 5y ago
Read my comments in https://news.ycombinator.com/item?id=26857198 When you write "your live stack", my brain freezes. Even a simple "webapp" project in my team had 4 common stacks (prod, staging, dev, gi
40.
by andreineculau 5y ago
I don't know them in depth but yes, I'd also go for telepresence (which is smth i discovered after i had my evrika moment and so i started googling for similar ideas or maybe even implementations)
41.
by andreineculau 5y ago
Right! I haven't explored that thought. My team kept everything serverless so we touched zero VPC/etc. From a generic perspective, having a setup to proxy into a LAN is more valuable I think - i can imagine for instance how my tea
42.
by andreineculau 5y ago
Living in my team's bubble i thought everyone runs or tries to run parallel environments: prod, staging, dev, but also an individual (person) or feature env. Why? Because there's no emulator or documentation that will teach you re
43.
by andreineculau 5y ago
Correct. I'm very pedantic and usually I can't help but find flaws in all proposals :)) but I really can't think of anything here. I can see limitations though: if you use lambda layers or native code specifically for the AWS
44.
by andreineculau 5y ago
I've been in the AWS world for 4+ years now and my immediate feedback is don't run any local emulators. None! Write unit tests for the internals and test your system end-to-end. I say that both because AWS services can have unpred
45.
by andreineculau 6y ago
!!! which not only covers the identity scenario but the whole configuration of git, which can be indeed very different from repo to repo, from company to company
46.
by andreineculau 7y ago
I have a script that we call when generating cloudformation templates to generate a dot graph Cfn2dot source https://github.com/tobiipro/support-firecloud/blob/master/bi... Used like this https:/&#
47.
by andreineculau 7y ago
Yup. It is a nice trick that you might find more often in Makefile. I have a make target that does this consistently in all the makefiles I write: https://github.com/andreineculau/core.inc.mk/blob/master/
48.
by andreineculau 7y ago
3 years ago i had some vague hope that things do improve although i am not aware of the bugfixes so i started tracking the bugs as GitHub issues Soon after i gave up. Too many silly bugs, and no fixes. Reference: https://github.c
49.
by andreineculau 7y ago
In a real emergency situation, there are all sorts of solutions to get a fix out and fast. But that almost never happens, thus it's not something to optimize for.
50.
by andreineculau 7y ago
the article talks about pre-commit hook, but nobody stops you from running these checks as pre-push hook. and nobody says you need to run the all the checks that you'd normally run on CI, but just enough checks to get past the silly er
51.
by andreineculau 7y ago
Not big challenges though. A simple tool like https://github.com/andreineculau/npm-publish-git does the job (it's regularly used and tested within my current company TobiiPro https://github.com/tob
52.
by andreineculau 7y ago
100% agree with you. Take the JS world for instance, npm is many good&bad things, but one thing that was squeezed in the package.json spec is the ability to install packages from git repositories. And so, github already had a "pack
53.
GitHub comments today showed as if they are from the future(twitter.com)
2 points by andreineculau 7y ago|1 comments
54.
by andreineculau 8y ago
Since many are asking/complaining that the author didn't provide alternatives, I'd like to point out the obvious starting with what JSON is - "a lightweight data-interchange format". Who is interchanging information
55.
by andreineculau 8y ago
You can already do that today if your editor implements a prettify-symbols-mode https://marketplace.visualstudio.com/items?itemName=siegebel... You can let editorconfig/linters/formatters to take care of code styl
56.
by andreineculau 8y ago
An alternative that is less verbose and uses a derivative of the cURL format is https://github.com/for-GET/katt/blob/master/README.md An example of a KATT spec: https://github.com/for-GET
57.
by andreineculau 8y ago
> Now almost the entirety of its functionality is to help various middle managers track things that are important to them, while continuously making development slower. This!
58.
by andreineculau 8y ago
Stick to github issues or similar. Whatever is closer to the real work and gives you the biggest bang for the buck. Not the most wet dream. You do not need a gazillion of workflows and checks and stories and epics and boards etc. "Keep
59.
by andreineculau 8y ago
Amen to that! Both as a user and a developer in the atlassian ecosystem, the experience is like you're 2 decades behind simple basic features with astronomical implementation effort. "Enterprise" has never gotten a negative c
60.
by andreineculau 8y ago
Alternative: finger and the Norwegian weather service YR - https://github.com/ways/pyyrascii

More ›