je42

31 ms·

241.
by je42 7y ago
Generating UX/UI in the backend doesn't imply to use old tooling. React server side rendering, Vue's Nuxt, etc are all modern ways to render UX/UI in the backend for example. And there are more. The discussion of renderi
242.
by je42 7y ago
That's why you still want explicit automatic audits.
243.
by je42 7y ago
However, Frontends are also expensive when you look on other metrics. They consume battery for example on a mobile device. > GQL allows for the client UI/UX to describe what it needs, and the backend delivers that, within the contex
244.
by je42 7y ago
To GraphQL there is also the opposite: Just move as much stuff as possible to the backend - make the frontend thin. With that approach you also don't end up writing a lot of specialized REST endpoints for the frontend. You can just us
245.
by je42 7y ago
Yep. As a bigger org you want automatic compliance checks that verify that all buckets are not publically accessible.
246.
by je42 7y ago
Cool ! Thanks for pointing out those differences ! It helps when deciding on which library is best for the use-case at hand.
247.
by je42 7y ago
nice README. I am a bit surprised that there is no reference to Ramda ( https://ramdajs.com/ )?
248.
by je42 7y ago
i guess you can blame on the interview process... i usually ask deep questions on the first random items the interviewee puts in bold on his/her C.V. so lying shouldn't help. i.e. say when you don't know. if you say you know
249.
by je42 7y ago
the whole point is "you cannot fork a fixed dependency". if they put this libc into an environment where other applications need to work, then application developers will need to deal with the fact that there a multiple libc aroun
250.
by je42 7y ago
I am curious: Why is your other half of your services in Go ? If you are happy with .Net ?
251.
by je42 7y ago
in a unit-test scenario, you are writing tests based on the language and its properties. he is applying risk based assessment which tests are required to provide a high quality implementation. If a system misbehaves you will catch in higher
252.
by je42 7y ago
Unittests !
253.
by je42 7y ago
One thing about agile is that usually companies not only set fixed deadlines but also fixed feature set; which usually means lower quality. That in turn means technical debt; which puts future deadlines and feature sets at risk. Since in SC
254.
Wait, why the hell is the ‘race to 5G’ even a race?(theverge.com)
3 points by je42 7y ago|1 comments
255.
by je42 7y ago
you need a team for larger applications, however the members of the team should have overlapping skills. so you don't always need to do everything all the time. it is fine to be a specialist in some areas. actually, a team needs specia
256.
by je42 7y ago
Using Kappa architecture it becomes a system-wide pattern; and it should be applied in a large context; because thats the point of the architecture ;)
257.
by je42 7y ago
> Do not apply this pattern with a loose hand. Why especially this pattern ? I would say you shouldn't apply any pattern with a loose hand...
258.
by je42 7y ago
> if you say you’re a master of network protocols, guess what, I’ve maintained a TCP/IP stack, and unless you’re really a master I’m going to bury you. yep. :) all lot of applicants should take a note at this.
259.
by je42 7y ago
usually for a coding challenge i include in the instructions to add unittests. ;) since I consider the ability to write well designed unittests as crucial.
260.
by je42 7y ago
Why not use dead projects ? I like TurboBadger for example. It is pretty feature complete and the code base is well developed. so changes and/or fixes can be done quite easily.
261.
by je42 7y ago
jep. it can cause hard to trace errors and makes reproducible build more difficult.
262.
by je42 7y ago
this was an important result in the linear algebra class for first year math/cs/eng students at my university.
263.
by je42 7y ago
i guess the main question is why humans can do it without lidar ? or the other way put: why would a lidar bridge the gap between a current vision-based system and human level performance ?
264.
by je42 8y ago
looks quite ugly. repeating keys... yaml looks better (while it has other problems)
265.
by je42 8y ago
mmh. cflags and cxxflags are command line options ? i would expect them to be defined as part of build file.
266.
by je42 8y ago
we have await this() and await that() also in python aiohttp and we will have in C++ co_wait this() and co_wait that() and we have in C# await this() and await that() this is not something specific to JS / Typescript...
267.
by je42 8y ago
it is not only operating cost but also costs for licensing.
268.
by je42 8y ago
please keep in mind server-side doesn't mean necessarily "basic" you can have a server-side app and still have the same user experience as a full-blown SPA app, as long as you know what you must do in the client for a great u
269.
by je42 8y ago
agreed: everything that you must do client-side because of latency, offline and/or device capabilities: do it client side. everything else should go to the server.
270.
by je42 8y ago
so this means you have implemented scrum not efficiently. if you work in an inverted pyramid where the team has autonomy (within boundaries) - scrum doesn't become a reporting tool it is for the team. since there is nothing else "

More ›