text
stringlengths
0
2.35k
[2470.38 --> 2476.40] running to still rising people's mttrs mttds meantime to detection and resolutions actually getting
[2476.40 --> 2481.34] higher as opposed to lower so i think this is the common state that a lot of companies find themselves
[2481.34 --> 2486.46] in and of course with the increased volume of data folks bills increase and the problem actually
[2486.46 --> 2490.70] gets harder so i think that's a common state we find a lot of companies into and this is probably
[2490.70 --> 2494.94] why it's top of mind for a lot of companies out there very cool thank you martin all right the next
[2494.94 --> 2501.06] step is to head to chronosphere.io to explore the platform and get a demo again chronosphere.io
[2501.06 --> 2530.98] okay so we kind of touched on this a little earlier in the episode
[2530.98 --> 2537.48] but i want to dig a little bit deeper in fact i will ask you a question first are you engaged in
[2537.48 --> 2541.54] any kind of open source projects i know you said that you you know contribute to go a little
[2541.54 --> 2550.02] is that a world in which you feel like you have engaged and put prs in so i can cheat my answer
[2550.02 --> 2555.58] right okay yeah as i'm evolving open source because i work at the last the majority of our
[2555.58 --> 2562.46] repels are open source right but as a 100 open source contribution that i'm not working for the
[2562.46 --> 2568.50] company or not no i read you it's something that i always wanted i just said like i managed to get
[2568.50 --> 2577.10] a committed to in go but i haven't fully got to participate in a project i still try oh no today i think i
[2577.10 --> 2582.32] got one on kubernetes too you see like it's one of my goals you know these plans that things you want
[2582.32 --> 2587.00] to do also have to try a bit you know it goes back and forth i may go for a coin again perhaps
[2587.00 --> 2592.56] you know the flame just like lighting up again reignite that passion that's gonna happen but
[2592.56 --> 2597.96] yeah no i'm not really engaged on let's say an external open source project that's not part of
[2597.96 --> 2603.90] my daily job and when you have done it is part of the reason why you think it's difficult to engage
[2603.90 --> 2609.22] fully is anything to do with that to do with like the difficult or the different process to put in a
[2609.22 --> 2615.62] when it is an open source project as opposed to internal like within work pr reviews and submission
[2615.62 --> 2620.30] i think to me what's always difficult like to find something meaningful to work
[2620.30 --> 2627.50] right sometimes you don't know what you can do there is a tag first good issue and so but
[2627.50 --> 2632.16] i think you're a lot i think yeah that's the point we're lost and you don't have someone to go
[2632.16 --> 2639.06] please help me yeah right or i try that or shall i do that right because my project and my team are
[2639.06 --> 2644.36] comfortable to go and do a refactor yeah it's like complete external project that i don't know
[2644.36 --> 2650.88] anyone there or anything i'm gonna be afraid you know and sometimes you're not even able to run
[2650.88 --> 2656.58] the project so that i think that's a lot of the barrier i think if you would have something
[2656.58 --> 2662.66] not necessarily a mentor but you know perhaps like a channel ask questions right like oh i want
[2662.66 --> 2667.62] to get even that like say oh i want to take this issue because sometimes they're good first issues
[2667.62 --> 2672.92] they open like one year ago i was like dude i don't know if it's worth to fix that or not and then
[2672.92 --> 2677.68] you open the pull request you fix everything no one reviews and then you think no one reviews
[2677.68 --> 2683.42] nothing got stale you get demotivated yeah fair enough and do you think there's a higher bar
[2683.42 --> 2688.08] as to what you're willing to put in as a pr for an open source project i speak about this from my
[2688.08 --> 2692.76] own personal like experience when i was trying to get into like okay i want to contribute to open
[2692.76 --> 2697.68] source oh you should just go in and do like a little change but i was like yeah but i feel like
[2697.68 --> 2703.86] i'm contributing to an open source library where everyone can see and they're like oh angelica made
[2703.86 --> 2710.16] like a one line change or like change that one function name i think and if i talk for myself
[2710.16 --> 2715.02] i always had the feeling to contribute to open source pros the bar is super high yeah
[2715.02 --> 2722.24] are you having to be like an expert developer and everything and the reality is no right and
[2722.24 --> 2730.06] the issue is there the problem exists i think this is the best advice i can do to any junior developer
[2730.06 --> 2736.70] just go for it they know you already have right so your change is not there the bug is not fixed
[2736.70 --> 2743.64] the documentation not proved the feature is not there right so this is not gonna change if your
[2743.64 --> 2748.86] change didn't get there you learn something you play with a new technology i was trying to submit
[2748.86 --> 2755.48] pull requests for the kubernetes code just fixing leading issues i understand a bit how the that piece
[2755.48 --> 2760.56] of code worked and i was like oh how they instructed that and like look at the packages because i had to
[2760.56 --> 2766.20] read through the packages to fix leading issues i think one pr got merged the other ones got stale
[2766.20 --> 2773.56] this life it happens and i learned something yeah so try go for it let the other one say no it's not
[2773.56 --> 2781.48] your job to say no for you right it's their job that is a popular opinion i bet applies to many fields
[2781.48 --> 2792.10] in life that's true just do it yes try yeah well done all right the fun part unpopular opinions
[2792.10 --> 2797.28] before we started the recording anderson you mentioned you have several unpopular opinions
[2797.28 --> 2802.20] and you were wondering whether you should go for the most yeah how did you phrase that i forget you
[2802.20 --> 2809.20] used a good word the most controversial yeah exactly or the least controversial yeah now i'm taking
[2809.20 --> 2816.24] i'm picking a controversial one yeah right but i can explain as i said in the pr you can explain
[2816.24 --> 2823.96] you should not write more than 100 columns right you write your code your code should not really
[2823.96 --> 2832.88] pass 100 columns from which yeah first things there's no magic numbers like 100 cut i would say 110
[2832.88 --> 2839.32] it's okay when it's really bad to cut right 120 is almost a hard limit don't really go over that
[2839.32 --> 2848.52] why first things first do you read books on landscape no right come on i think everyone had
[2848.52 --> 2854.12] that right you got like this email right you're like in your four key or ever monitor and that thing
[2854.12 --> 2859.92] goes from side to side and you're reading for the listeners i'm moving my head as you know reading
[2859.92 --> 2863.94] from one side to the other like you're watching tennis you feel like you know a typewriter that goes
[2863.94 --> 2873.90] so it's hard to read right because we don't read in landscape we read in portrait the second
[2873.90 --> 2880.92] thing is not everyone has got ice cream as big as yours there are people coding 14 13 inches right
[2880.92 --> 2887.50] they want to have two tabs open perhaps so if you go much more than 100 it's going to be bad for
[2887.50 --> 2894.00] some people and i believe for everyone too long it's hard to read so that's my unpopular opinion
[2894.00 --> 2900.34] i want to disappoint you that i think i agree with you and i even take this into writing emails that
[2900.34 --> 2906.38] i try to keep that i don't know how many characters that is but i sometimes break lines like one sentence
[2906.38 --> 2912.02] into three four lines just so it stays so you don't have to scroll in case yeah images logos i don't know
[2912.02 --> 2916.14] whatever happens in somebody's signature that it suddenly gets stretched i feel like you're
[2916.14 --> 2922.66] unfortunately preaching to the choir with me and natalie we're both like yes please i don't like
[2922.66 --> 2929.50] my neck will hurt perhaps in go a chrome plugin that just truncates things for you yeah perhaps
[2929.50 --> 2934.62] in go but i think if you go to java you know the things are long there yeah 100 characters is just
[2934.62 --> 2942.34] the function name oh my gosh yes i feel like that one was a good one but like if we have time natalie i want
[2942.34 --> 2948.30] to hear another one yeah i want us to get like an unpopular one from you oh my god what was the
[2948.30 --> 2952.24] other one that you were thinking about saying that you cheekily in your mind were like no i'm not gonna
[2952.24 --> 2957.44] say that no i think this one's like the unpopular kind of popular okay i mean i see a lot happening so
[2957.44 --> 2964.08] perhaps in unpopular return new is wrong period right you have to wrap the errors and add more context
[2964.08 --> 2971.30] always i cannot count how many times i had to go to the code and dig deep and deep and deep to discover
[2971.30 --> 2978.04] where this error came from because i you know it's like when you get like a you try to write to the
[2978.04 --> 2982.76] disk and get an error you get something like i got one too many colors in the address it's like
[2982.76 --> 2988.58] this is finally the address how there is too many columns right and then you have to understand where
[2988.58 --> 2993.56] this address was going to be used which method it was and then oh yeah on this context there are too many
[2993.56 --> 2998.68] columns but they didn't have this information so return new is wrong you have to wrap your errors
[2998.68 --> 3003.54] now you don't have an excuse you have ever wrapping when they send the library so i think wrapping errors
[3003.54 --> 3009.52] will be an unpopular opinion yeah i feel like this this second one is gonna probably be more unpopular
[3009.52 --> 3016.04] yeah because a lot of people just return yeah yeah interesting that's one of the things that i'm looking
[3016.04 --> 3021.70] for requests and was like dude could you wrap that and then it goes back on that if it's my repo
[3021.70 --> 3028.44] my code i might say like no now when i say my please like my teams right i don't have this
[3028.44 --> 3036.06] possessive i think code must be owned by a group and it must be a consensus group but yeah this is the
[3036.06 --> 3041.96] thing that i'm gonna point and usually if it's an external adding code even more important like okay
[3041.96 --> 3049.28] like your wrapper your rules our wrapper our rules right so okay here we wrap do that if i'm owning your
[3049.28 --> 3055.02] wrapper i play by your rules i like that one i'm also having so many more ideas this always happens
[3055.02 --> 3059.82] when me and you have episode nathia i'm like so many more episode ideas write them all down does
[3059.82 --> 3065.68] your code belong to you or to the world i mean on an open source that's definitely a question right
[3065.68 --> 3072.48] yeah also with ai tools that are writing code that's a question yeah oh god that's yeah who is the true
[3072.48 --> 3078.64] either code yeah that's a good one yeah licensing is interesting for sure with a copilot and friends
[3078.64 --> 3085.58] when the ai put the bug in production who do you blame who run the ai who wrote the ai
[3085.58 --> 3092.22] or who reviewed the pr that's a good one right can ai review a pr for sure for sure
[3092.22 --> 3100.00] would you trust that i might have used that in the past yes oh that's nice okay i'm a big fan of ai
[3100.00 --> 3106.08] and coding i think it's a fun combination i'm very happy to automate myself out of job that's good