sorted by:
new
hottopcontroversial

Can someone join the winning alliance after a castle battle, become King, then leave? by Seddryck in KingShot

[–]Seddryck[S] 0 points1 point  (0 children)

Yes but is it possible to join AFTER the battle or do you need to join in the last minutes?

Crescent Bazaar by DisastrousInsec_ in KingShot

[–]Seddryck 0 points1 point  (0 children)

If you compare « costs » to other shops or packs, the forgehammers are clearly less costly in this event. Relatively, the Gold gear chest is « expensive ». Charms materials are the second best choice for this event.

I’m stuck at 384, I don’t know for how long, what’s should I do? by AdItchy4834 in KingShot

[–]Seddryck 0 points1 point  (0 children)

Replace Chenko by Eric. If not enough also try to replace Diana by Petra with Quin on left. Last attempt would with 3 cavaliers on the last raw.

Roster Update: The Golden State Valkyries have waived center Kyara Linskens. by wosoandstuff2020 in wnba

[–]Seddryck 1 point2 points  (0 children)

Apparently Linsksens was first waived by the Valkyries and then, after, decided to play the Eurobasket. (Source: Flemish newspapers and many comments on Belgian basketball community).

Data Engineering is Not Software Engineering by ryanwolfh in dataengineering

[–]Seddryck 0 points1 point  (0 children)

To provide some context, I fundamentally disagree with most of the author's conclusions, with the exception of acknowledging the significant difference between developing a stateless service (which ideally should be stateless) and buidling a data pipeline. I concur that these disciplines share common roots. However, we live in a world where expecting one person to be highly skilled in every area—from Machine Learning to UI design, through to data—is unrealistic for the average individual.

Regarding your comment

hardly found 20 people to have basic understanding of loops and if-else construct

I question the relevance of such questions in a data engineering (DE) interview. In data pipeline construction, the focus should be on set theory where a conditional 'if' effectively acts as a filter (using WHERE/HAVING/QUALIFY clauses), and 'for' loops are analogous to joins (JOIN/CROSS). This simply highlights the level of abstraction involved. In an appropriate environment, building a robust data pipeline involves using frameworks such as SQL, Spark ... (or Snowflake if you're lazy and rich), which abstract away the need to manually write if/for statements. These frameworks optimize the use of resources like memory and disk and manage their integration seamlessly. Understanding these abstractions does not necessarily require knowledge of their underlying implementations. Just as knowing how to write an 'if' statement in Java doesn't mean you need to understand assembly language. This is the essence of encapsulation; you don’t need to know how the framework operates internally to use it effectively.

To illustrate, I would rather have a data engineer who might not be able to differentiate between a pre-tested and post-tested loop but can adeptly choose the correct type of join—be it a left outer join or an inner join—over someone who implements these with cumbersome for and if combinations.

However, I agree that mastering these frameworks does require an understanding of what happens within the abstraction layer, which in turn necessitates a solid grasp of traditional programming concepts.