Youtube comments of Charles M. (@charlesm.2604).

  1. 285
  2. 237
  3. 234
  4. 201
  5. 193
  6. 179
  7. 151
  8. 150
  9. 131
  10. 127
  11. 124
  12. 118
  13. 113
  14. 107
  15. 103
  16. 94
  17. 92
  18. 84
  19. 83
  20. 80
  21. 77
  22. 76
  23. 75
  24. 72
  25. 71
  26. 70
  27. 65
  28. 64
  29. 63
  30. 63
  31. 60
  32. 58
  33. 55
  34. 53
  35. 52
  36. 52
  37. 51
  38. 49
  39. 47
  40. 46
  41. 46
  42. 45
  43. 44
  44. 43
  45. 40
  46. 39
  47. 39
  48. 37
  49. 37
  50. 36
  51. 36
  52. 36
  53. 36
  54. 35
  55. 35
  56. 35
  57. 35
  58. 33
  59. 32
  60. 32
  61. 32
  62. 31
  63. 30
  64. 30
  65. 29
  66. 29
  67. 29
  68. 28
  69. 28
  70. 28
  71. 28
  72. 27
  73. 27
  74. 26
  75. 26
  76. 26
  77. 25
  78. 25
  79. 25
  80. 24
  81. 24
  82. 24
  83. 23
  84. 23
  85. 23
  86. 22
  87. 22
  88. 22
  89. 22
  90. 22
  91. 21
  92. 21
  93. 21
  94. 21
  95. 21
  96. 20
  97. 20
  98. 20
  99. 20
  100. 20
  101. 20
  102. 19
  103. 19
  104. 19
  105. 19
  106. 19
  107. 19
  108. 19
  109. 18
  110. 18
  111. 18
  112. 18
  113. 18
  114. 18
  115. 18
  116. 18
  117. 17
  118. 17
  119. 17
  120. 17
  121. 16
  122. 16
  123. 16
  124. 15
  125. 15
  126. 15
  127. 14
  128. 14
  129. 14
  130. 14
  131. 14
  132. 14
  133. 14
  134. 14
  135. 14
  136. 14
  137. 13
  138. 13
  139. 13
  140. 13
  141. 13
  142. 13
  143. 13
  144. 13
  145. 13
  146. 13
  147. 13
  148. 12
  149. 12
  150. 12
  151. 12
  152. 12
  153. 12
  154. 11
  155. 11
  156. 11
  157. 11
  158. 11
  159. 11
  160. 11
  161. 11
  162. 11
  163. 11
  164. 11
  165. 11
  166. 11
  167. 11
  168. 11
  169. 11
  170. 11
  171. 11
  172. 11
  173. 11
  174. 11
  175. 11
  176. 10
  177. 10
  178. 10
  179. 10
  180. 10
  181. 10
  182. 10
  183. 10
  184. 10
  185. 10
  186. 10
  187. 10
  188. 10
  189. 10
  190. 10
  191. 10
  192. 9
  193. 9
  194. 9
  195. 9
  196. 9
  197. 9
  198. 9
  199. 9
  200. 9
  201. 9
  202. 9
  203. 9
  204. 9
  205. 9
  206. 8
  207. 8
  208. 8
  209. 8
  210. 8
  211. 8
  212. 8
  213. 8
  214. 8
  215. 8
  216. 8
  217. 8
  218. 8
  219. 8
  220. 8
  221. 8
  222. 8
  223. 8
  224. 8
  225. 8
  226. 8
  227. 8
  228. 8
  229. 8
  230. 8
  231. 8
  232. 8
  233. 7
  234. 7
  235. 7
  236. 7
  237. 7
  238. 7
  239. 7
  240. 7
  241. 7
  242. 7
  243. 7
  244. 7
  245. 7
  246. 7
  247. 7
  248. 7
  249. 7
  250. 6
  251. 6
  252. 6
  253. 6
  254. 6
  255. 6
  256. 6
  257. 6
  258. 6
  259. 6
  260. 6
  261. 6
  262. 6
  263. 6
  264. 6
  265. 6
  266. 6
  267. 6
  268. 6
  269. 6
  270. 6
  271. 6
  272. 6
  273. 6
  274. 6
  275. 6
  276. 6
  277. 6
  278. 6
  279. 6
  280. 6
  281. 6
  282. 6
  283. 6
  284. 6
  285. 6
  286. 6
  287. 6
  288. 6
  289. 6
  290. 6
  291. 6
  292. 6
  293. 5
  294. 5
  295. 5
  296. 5
  297. 5
  298. 5
  299. 5
  300. 5
  301. 5
  302. 5
  303. 5
  304. 5
  305. 5
  306. 5
  307. 5
  308. 5
  309. 5
  310. 5
  311. 5
  312. 5
  313. 5
  314. 5
  315. 5
  316. 5
  317. 5
  318. 5
  319. 5
  320. 5
  321. 5
  322. 5
  323. 5
  324. 5
  325. 5
  326. 5
  327. Hi folks, software engineer here, if I can add my 2 cents in there for that dude looking for advice: Although I never worked on videogames, I know a bunch of people who did. And AAA studios will kill you. There is a thing in that specific field called "the crunch" which describe the time period during the annoucement of the game and its release. We call it "the crunch" because that's the noises your body makes when you're done with it. To make a long story short, publishers dedicate their resources depending on predictions. The first few months/year after a release, a game will cost more money than it'll bring. In order not to screw their budgets, publishers are only showing a maquette of the final product when they announce it then gather as much feedback as possible to see if the development is worth it before actually entering the development process. That's when the crunch starts. Studios will restrict you out of your social life, will not let you have phone calls during work, will not value your health (and that's one of the most fucked up part about it), will force you to work additionnal UNPAID hours, etc... They do so by threatning you. They know that you've sacrificed a whole lot to have this position and use it against you. They manipulate you out of your entourage as well. They also let you know that if you can't resist the crunch, other studios won't work with you as you are not fit for the job (it is an industry standard after all). There is ton of info online if you want to learn more but the videogame industry is one of the closest to ressemble modern day slavery. Now it's not to say it's all bad, in fact it's gotten better since 3-5 years because of unification and social medias. Indie studios or those who are not published by/related to AAA publishers are not really impacted by the crunch on such levels too. EDIT for some resources: - "Inside Rockstar Games' Culture Of Crunch" by Jason Schreier (Kataku - 2018) - "How is crunch legal in the videogame industry" by Michael Thomsen (The Washington Post - 2021) - TakeThis non profits, charity about mental health awareness invested in the problem.
    5
  328. 5
  329. 5
  330. 5
  331. 5
  332. Vue SFC approach is really neat. I hate JSX, and I hate that I have to use it. Why would you mix JavaScript and markup ? It makes for disgusting return statements. React's "just a library" lie approach* is also a waste of time, because you're gonna end up using React specific libraries without the advantage of boilerplate. On the same note, React doesn't have a powerful CLI for code generation and scaffolding like Vue and Angular. React has pseudo-functional mindset when it's not only not needed but also completely counter intuitive. Older React class based components were neat because you could take advantage of TypeScript interface implementation. Now you need to use hooks with poorly designed APIs for things that used to be super straight forward. Then you have styling. If you're going to embed HTML into JavaScript, why on earth aren't you embedding CSS in it as well ? For the love of god, make a DSL for CSS instead of forcing your users to use poor CSS-in-JS "libraries" with `template literals`, no syntax highlighting/formatting/suggestions, etc... And make it sit in your file with no purpose. Let not get me started on state management, it took I don't know how many year for the team to implement an atomic state management solution, and we still don't have proper a store API, we need to build on top of the poorly designed Context. Vue is good because it has a proper boilerplate and powerful CLI like Angular without enforcing a strict design so it's still accessible and manageable for junior devs. In addition to official libraries for routing, state management, testing, etc... And Vue has a great SFC design to keep views, styling and business logic separated but still closely connected. Model, expression, binding directives, etc... are so much better than throwing some JavaScript code in a JSX statement, I mean have you seen loops and conditional rendering in React? 🤮
    5
  333. 5
  334. 5
  335. 5
  336. 5
  337. 5
  338. 5
  339. 5
  340. 5
  341. 4
  342. 4
  343. 4
  344. 4
  345. 4
  346. 4
  347. 4
  348. 4
  349. 4
  350. 4
  351. 4
  352. 4
  353. 4
  354. 4
  355. 4
  356. 4
  357. 4
  358. 4
  359. 4
  360. 4
  361. 4
  362. 4
  363. 4
  364. 4
  365. 4
  366. 4
  367. 4
  368. 4
  369. 4
  370. 4
  371. 4
  372. 4
  373. 4
  374. 4
  375. 4
  376. 4
  377. 4
  378. 4
  379. 4
  380. 4
  381. 4
  382. 4
  383. 4
  384. 4
  385. 4
  386. 4
  387. 4
  388. 4
  389. 4
  390. 4
  391. 4
  392. 4
  393. 4
  394. 4
  395. 4
  396. 4
  397. 4
  398. 4
  399. 4
  400. 4
  401. 4
  402. 4
  403. 4
  404. 4
  405. 4
  406. 4
  407. 4
  408. 4
  409. 4
  410. 3
  411. 3
  412. 3
  413. 3
  414. 3
  415. 3
  416. 3
  417. 3
  418. 3
  419. 3
  420. 3
  421. 3
  422. 3
  423. 3
  424. 3
  425. 3
  426. 3
  427. 3
  428. 3
  429. 3
  430. 3
  431. 3
  432. 3
  433. 3
  434. 3
  435. 3
  436.  @biskitpagla  Linting isn't helping to write clean code though, it helps to share a set of conventions on a project. Consistency of conventions is just one of the many elements that form a clean codebase, outside the scope of linting I can think of: -naming of variables, functions and functions parameters -functions only solving one issue, being concise and short -comments (JDocs format) -avoiding "magic" code as much as possible (ternary, lambdas, etc...) -using most familiar design patterns in the team -white spacing classes properly -avoiding referencing functional code from different files, reserving unique file exports to objects (classes, enums, interfaces, etc...). For example linting wouldn't mind those 2 approaches yet the second is clearly cleaner than the first: 1) public run(str: string, o = this.default): string [] 2) broken down: public getDirectoryContent(path: string, options?: DirectoryParserOptions = this.defaultOptions): string[] private isDirectoryAccessible(path: string): boolean private optionsToArgs(options: DirectoryParserOptions): string private runCLICommand(command: string): string[] And that's not true at all, a lot of modern languages make for disgusting dirty codebases with confusing code, spaghetti code and bad conventions from the language designers themselves. Off the dome I'm thinking Dart & Flutter or the stairway to hell as I like to call it. On the other hand you have C# for example which, despite being an "old" language, is clearly more readable. Because the people who designed it aren't dogshit.
    3
  437. 3
  438. 3
  439. 3
  440. 3
  441. 3
  442. 3
  443. 3
  444. 3
  445. 3
  446. 3
  447. 3
  448. 3
  449. 3
  450. 3
  451. 3
  452. 3
  453. 3
  454. 3
  455. 3
  456. 3
  457. 3
  458. 3
  459. 3
  460. 3
  461. 3
  462. 3
  463. 3
  464. 3
  465. 3
  466. 3
  467. 3
  468. 3
  469. 3
  470. 3
  471. 3
  472. 3
  473. 3
  474. 3
  475. 3
  476. 3
  477. 3
  478. 3
  479. 3
  480. 3
  481. 3
  482. 3
  483. 3
  484. 3
  485. 3
  486. 3
  487. 3
  488. 2
  489. 2
  490. 2
  491. 2
  492. 2
  493. 2
  494. 2
  495. 2
  496. 2
  497. 2
  498. 2
  499. 2
  500. 2
  501. 2
  502. 2
  503. 2
  504. 2
  505. 2
  506. 2
  507. 2
  508. 2
  509. 2
  510. 2
  511. 2
  512. 2
  513. 2
  514. 2
  515. 2
  516. 2
  517. 2
  518. 2
  519. 2
  520. 2
  521. 2
  522. 2
  523. 2
  524. 2
  525. 2
  526. 2
  527. 2
  528. 2
  529. 2
  530. 2
  531. 2
  532. 2
  533. 2
  534. 2
  535. 2
  536. 2
  537. 2
  538. 2
  539. 2
  540. 2
  541. 2
  542. 2
  543. 2
  544. 2
  545. 2
  546. 2
  547. 2
  548. 2
  549. 2
  550. 2
  551. 2
  552. 2
  553. 2
  554. 2
  555. 2
  556. 2
  557. 2
  558. 2
  559. 2
  560. 2
  561. 2
  562. 2
  563. 2
  564. 2
  565. 2
  566. 2
  567. 2
  568. 2
  569. 2
  570. 2
  571. 2
  572. 2
  573. 2
  574. 2
  575. 2
  576. 2
  577. 2
  578. 2
  579. 2
  580. 2
  581. 2
  582. 2
  583. 2
  584. 2
  585. 2
  586. 2
  587. 2
  588. 2
  589. 2
  590. 2
  591. 2
  592. 2
  593. 2
  594. 2
  595. 2
  596. 2
  597. 2
  598. 2
  599. 2
  600. 2
  601. 2
  602. 2
  603. 2
  604. 2
  605. 2
  606. 2
  607. 2
  608. 2
  609. 2
  610. 2
  611. 2
  612. 2
  613. 2
  614. 2
  615. 2
  616. 2
  617. 2
  618. 2
  619. 1
  620. 1
  621. 1
  622. 1
  623. 1
  624. 1
  625. 1
  626. 1
  627. 1
  628. 1
  629. 1
  630. 1
  631. 1
  632. 1
  633. 1
  634. 1
  635. 1
  636. 1
  637. 1
  638. 1
  639. 1
  640. 1
  641. 1
  642. 1
  643. 1
  644. 1
  645. 1
  646. 1
  647. 1
  648. 1
  649. 1
  650. 1
  651. 1
  652. 1
  653. 1
  654. 1
  655. 1
  656. 1
  657. 1
  658. 1
  659. 1
  660. 1
  661. 1
  662. 1
  663. 1
  664. 1
  665. 1
  666. 1
  667. 1
  668. 1
  669. 1
  670. 1
  671. 1
  672. 1
  673. 1
  674. 1
  675. 1
  676. 1
  677. 1
  678. 1
  679. 1
  680. 1
  681. 1
  682. 1
  683. 1
  684. 1
  685. 1
  686. 1
  687. 1
  688. 1
  689. 1
  690. 1
  691. 1
  692. 1
  693. 1
  694. 1
  695. 1
  696. 1
  697. 1
  698. 1
  699. 1
  700. 1
  701. 1
  702. 1
  703. 1
  704. 1
  705. 1
  706. 1
  707. 1
  708. 1
  709. 1
  710. 1
  711. 1
  712. 1
  713. 1
  714. 1
  715. 1
  716. 1
  717. 1
  718. 1
  719. 1
  720. 1
  721. 1
  722. 1
  723. 1
  724. 1
  725. 1
  726. 1
  727. 1
  728. 1
  729. 1
  730. 1
  731. 1
  732. 1
  733. 1
  734. 1
  735. 1
  736. 1
  737. 1
  738. 1
  739. 1
  740. 1
  741. 1
  742. 1
  743. 1
  744. 1
  745. 1
  746. 1
  747. 1
  748. 1
  749. 1
  750. 1
  751. 1
  752. 1
  753. 1
  754. 1
  755. 1
  756. 1
  757. 1
  758. 1
  759. 1
  760. 1
  761. 1
  762. 1
  763. 1
  764. 1
  765. 1
  766. 1
  767. 1
  768. 1
  769. 1
  770. 1
  771. 1
  772. 1
  773. 1
  774. 1
  775. 1
  776. 1
  777. 1
  778. 1
  779. 1
  780. 1
  781. 1
  782. 1
  783. ​@ I am not saying they aren't productive. LLMs are literally glorified guesstimate algorithms. It's how they work. I wasn't downplaying how good their results are, just that there is nothing to be done to make them better. Sanitizing datasets, sure. Feeding them more data, increasing its parameters (until it LITERALLY can't fit on the planet), sure. Using more efficient transformers, sure. That's the extent of the progress of LLMs, it LITERALLY can't be better than it is. I can't wait for the LLM hype to be over and for the research to be done on actual AI. We have made so much advancement in computer vision, but we somehow abandoned it. In a year we'll have companies training their LLMs distills using their own data for their own specific targeted needs (without the insane general purpose weights of the massive models like OAI, Claude, LLama, etc.) and we will move back to fund AI development in directions that'll actually matter. I encourage you to read more on the topic of what LLMs are, and how they work. In the meantime, here's the takeaway from Google's own "Introduction to Large Language Models" papers: "Language models predict and generate text by estimating the probability of a token or sequence of tokens occurring within a longer sequence, useful for tasks like text generation and translation. Large language models (LLMs) are advanced language models with vast parameters and datasets, enabling them to process longer text sequences and perform complex tasks like summarization and question answering." This reply is probably going to get deleted but I hope you can read it before it happens.
    1
  784. 1
  785. 1
  786. 1
  787. 1
  788. 1
  789. 1
  790. 1
  791. 1
  792. 1
  793. 1
  794. 1
  795. 1
  796. 1
  797. 1
  798. 1
  799. 1
  800. 1
  801. 1
  802. 1
  803. 1
  804. 1
  805. 1
  806. 1
  807. 1
  808. 1
  809. 1
  810. 1
  811. 1
  812. 1
  813. 1
  814. 1
  815. 1
  816. 1
  817. 1
  818. 1
  819. 1
  820. 1
  821. 1
  822. 1
  823. 1
  824. 1
  825. 1
  826. 1
  827. 1
  828. 1
  829. 1
  830. 1
  831. 1
  832. 1
  833. 1
  834. 1
  835. 1
  836. 1
  837. 1
  838. 1
  839. 1
  840. 1
  841. 1
  842. 1
  843. 1
  844. 1
  845. 1
  846. 1
  847. 1
  848. 1
  849. 1
  850. 1
  851. 1
  852. 1
  853. 1
  854. 1
  855. 1
  856. 1
  857. 1
  858. 1
  859. 1
  860. 1
  861. 1
  862. 1
  863. 1
  864. 1
  865. 1
  866. 1
  867. 1
  868. 1
  869. 1
  870. 1
  871. 1
  872. 1
  873. 1
  874. 1
  875. 1
  876. 1
  877. 1
  878. 1
  879. 1
  880. 1
  881. 1
  882. 1
  883. 1
  884. 1
  885. 1
  886. 1
  887. 1
  888. 1
  889. 1
  890. 1
  891. 1
  892. 1
  893. 1
  894. 1
  895. 1
  896. 1
  897. 1
  898. 1
  899. 1
  900. 1
  901. 1
  902. 1
  903. 1
  904. 1
  905. 1
  906. 1
  907. 1
  908. 1
  909. 1
  910. 1
  911. 1
  912. 1
  913. 1
  914. 1
  915. 1
  916. 1
  917. 1
  918. 1
  919. 1
  920. 1
  921. 1
  922. 1
  923. 1
  924. 1
  925. 1
  926. 1
  927. 1
  928. 1
  929. 1
  930. 1
  931. 1
  932. 1
  933. 1
  934. 1
  935. 1
  936. 1
  937. 1
  938. 1
  939. 1
  940. 1
  941. 1
  942. 1
  943. 1
  944. 1
  945. 1
  946. 1
  947. 1
  948. 1
  949. 1
  950. 1
  951. 1
  952. 1
  953. 1
  954. 1
  955. 1
  956. 1
  957. 1
  958. 1
  959. 1
  960. 1
  961. 1
  962. 1
  963. 1
  964. 1
  965. 1
  966. 1
  967. 1
  968. 1
  969. 1
  970. 1
  971. 1
  972. 1
  973. 1
  974. 1
  975. 1
  976. 1
  977. 1
  978. 1
  979. 1
  980. 1
  981. 1
  982. 1
  983. 1
  984. 1
  985. 1
  986. 1
  987. 1
  988. 1
  989. 1
  990. 1
  991. 1
  992. 1
  993. 1
  994. 1
  995. 1
  996. 1
  997. 1
  998. 1
  999. 1
  1000. 1
  1001. 1
  1002. 1
  1003. 1
  1004. 1
  1005. 1
  1006. 1
  1007. 1
  1008. 1
  1009. 1
  1010. 1
  1011. 1
  1012. 1
  1013. 1
  1014. 1
  1015. 1
  1016. 1
  1017. 1
  1018. 1
  1019. 1
  1020. 1
  1021. 1
  1022. 1
  1023. 1
  1024. 1
  1025. 1
  1026. 1
  1027. 1
  1028. 1
  1029. 1
  1030. 1
  1031. 1
  1032. 1
  1033. 1
  1034. 1
  1035. 1
  1036. 1
  1037. 1
  1038. 1
  1039. 1
  1040. 1
  1041. 1
  1042. 1
  1043. 1
  1044. 1
  1045. 1
  1046. 1
  1047. 1
  1048. 1
  1049. 1
  1050. 1
  1051. 1
  1052. 1
  1053. 1
  1054. 1
  1055. 1
  1056. 1
  1057. 1
  1058. 1
  1059. 1
  1060. 1
  1061. 1
  1062. 1
  1063. 1
  1064. 1
  1065. 1
  1066. 1
  1067. 1
  1068. 1
  1069. 1
  1070. 1
  1071. 1
  1072. 1
  1073. 1
  1074. 1
  1075.  @RajinderYadav  Because without plugins vscode is nothing more than a text editor with a pretty embedded Terminal while we need IDEs. Since then I switched to the JetBrains ecosystem (I get the licenses through my employer) and it's crazy how much I've missed out on. The biggest pro of JetBrains IDEs is the code refactoring. It understands what you try to code and make your life so much easier. It informs you of changes you should make to your code in realtime, following official and/or popular conventional guidelines, it generates code for you and it also rewrites entire/parts of files for more readable, less bug-inducing (nullity/ exception handling, constructor initializations, dependency injection, etc...) and more extendable codebases. Ultimately it's the best tool to make your projects more maintainables and for devs to enjoy writing code again. But it's not all JetBrains offers; Test-driven-development isn't a pain anymore with the built-in Explorer, Automation is goated with Background Tasks, Scheduler and Debug/Run profiles, powerful analytics during Debugging, the Version Control integration is actually good (timestamps and diffs in the editor, commit and push through the UI), it also has proper built-in database tooling and specific tools (built-in REST client, HTTP server, WebView tabs, etc...). You also have plugins for non built-in languages support and for 3rd party services. Those plugins aren't bloating the execution Heap, making the program smooth to run on any configuration. And you get all of that at very lightweight performances. The IDE indexes your project as you work on it so it launches very fast and don't consume crazy amounts of RAM.
    1
  1076. 1
  1077. 1
  1078. 1
  1079. 1
  1080. 1
  1081. 1
  1082. 1
  1083. 1
  1084. 1
  1085. 1
  1086. 1
  1087. 1
  1088. 1
  1089. 1
  1090. 1
  1091. 1
  1092. 1
  1093. 1
  1094. 1
  1095. 1
  1096. 1
  1097. 1
  1098. 1
  1099. 1